System and method for wirelessly activating an electromechanically controlled fuel dispenser

A system and method are provided for remotely activating electromechanically controlled fuel dispensers. Each fuel dispenser is associated in a database with a unique identification code, and a first code is associated with an electronic payment system pre-identified by a fuel purchasing customer for automatic payment processing during fuel purchase transactions. In response to a wirelessly received identification code, the fuel dispenser associated in the database with the identification code that matches the wirelessly received identification code is identified, the identified fuel dispenser is activated to an active state in which the identified fuel dispenser is enabled to dispense fuel if the first code in the database matches a wirelessly received second code, and payment for the purchase of fuel dispensed from the identified fuel dispenser is automatically processed following activation thereof using the pre-identified electronic payment system associated with the first code in the database.

FIELD OF THE INVENTION

The present invention relates generally to apparatuses and techniques for dispensing fuel into motor vehicles and/or fuel storage containers, and more specifically to systems and methods for wirelessly activating electromechanically controlled fuel dispensers for subsequent dispensation of fuel into motor vehicles and/or fuel storage containers.

BACKGROUND

Fuel dispensers implemented at so-called “fueling stations” or “filling stations” provide for the purchase and dispensation of fuel into motor vehicles and/or fuel storage containers from one of typically multiple sources of fuel stored on-site. Conventional electromechanical fuel dispensers typically include a control section, which can be manipulated to control the fuel dispenser from an inactive state in which the fuel dispenser is inhibited from dispensing fuel to an active state in which the fuel dispenser is enabled for subsequent dispensation of fuel, and a dispensing section which, after the fuel dispenser is activated, can be manipulated to dispense the fuel from one of the sources of fuel.

Manipulations of the control and dispensing sections of known electromechanical fuel dispensers are generally manual operations. For example, a conventional technique for manipulating the control section may typically involve manually presenting a method of payment, e.g., credit/debit card or cash, at the fuel dispenser or to an attendant at the fueling station and, following approval of the method of payment, manually selecting a fuel type and/or grade. The action of manually selecting the fuel type and/or grade typically controls the fuel dispenser from the inactive state to the active state to enable the dispensing section of the fuel dispenser to be manually manipulated to dispense the selected fuel type and/or grade. Manipulation of the dispensing section then typically involves manually disengaging a fuel nozzle from the fuel dispenser, manually inserting the fuel nozzle into a fuel inlet orifice of a fuel tank of a motor vehicle or other fuel storage container, and then manually actuating a control lever carried by the nozzle to cause a fuel pump to dispense fuel from the selected source of fuel through a fuel hose and into the fuel inlet orifice via the nozzle.

SUMMARY

The present invention may comprise one or more of the features recited in the attached claims, and/or one or more of the following features and combinations thereof. In a first aspect, a method of remotely activating any of a plurality of electromechanically controlled fuel dispensers may comprise associating, with a first processor in a first database, each of the plurality of fuel dispensers with a different identification code, associating, with the first processor in the first or a second database, a first code and an electronic payment system pre-identified by a fuel purchasing customer for automatic payment processing during subsequent transactions for the purchase of fuel by the customer with any of the plurality of fuel dispensers, wirelessly receiving an identification code, in response to the wirelessly received identification code, identifying with the first processor the one of the plurality of fuel dispensers associated in the first database with the identification code that matches the wirelessly received identification code, wirelessly receiving a second code, in response to the wirelessly received second code, automatically activating with the first processor the identified one of the plurality of fuel dispensers from an inactive state in which the identified one of the plurality of fuel dispensers is disabled from dispensing fuel to an active state in which the identified one of the plurality of fuel dispensers is enabled to dispense fuel if the first code in the first or the second database matches the wirelessly received second code, and automatically processing with the first processor payment for the purchase of fuel dispensed from the identified one of the plurality of fuel dispensers following activation thereof using the pre-identified electronic payment system associated with the first code in the first or the second database.

In the first aspect, each of the plurality of electromechanically controlled fuel dispensers may be part of a retail enterprise, and the first code may comprise one of a plurality of enterprise membership service identification codes stored in the first or the second database that uniquely identifies a customer as one of a plurality of customer members of an enterprise membership service program associated with the retail enterprise. Automatically activating the identified one of the plurality of fuel dispensers may illustratively comprise comparing with the first processor the wirelessly received second code with the plurality of membership service identification codes, if the wirelessly received second code matches the one of the plurality of membership identification codes, accessing with the first processor the pre-identified electronic payment system associated in the first or the second database with the one of the plurality of membership identification codes, processing the accessed pre-identified electronic payment system for payment authorization, and automatically activating with the first processor the identified one of the plurality of fuel dispensers upon authorization of the accessed pre-identified payment system for payment for the purchase of fuel to be subsequently dispensed from the identified one of the plurality of fuel dispensers. Alternatively or additionally, the first or the second database may have stored therein a purchase history containing a record of purchases previously made from the retail enterprise by the identified one of the plurality of customer members of the enterprise membership service program, and the method may further comprise associating, with the first processor in the first or the second database, the first code with a mobile communication device carried by the identified one of the plurality of customer members of the enterprise membership service program, one of generating and retrieving from the first or the second database by the first processor at least one discount coupon for a product or service from the retail enterprise based on the purchase history of the identified one of the plurality of customer members of the enterprise membership service program, and wirelessly transmitting with the first processor to the mobile communication device associated with the first code in the first or the second database the at least one discount coupon or notification of the at least one discount coupon.

In the first aspect, the first code in the first or the second database may further comprises a security code, the method may further comprise wirelessly receiving a third code, and wherein automatically activating with the first processor the identified one of the plurality of fuel dispensers from the inactive state to the active state thereof may be further conditioned upon the security code in the first or the second database matching the wirelessly received third code.

In the first aspect, the identified one of the plurality of fuel dispensers may be configured to selectively dispense any of a plurality of different grades or types of fuel, and the method may further comprise associating with the first processor in the first or the second database the first code and a default grade or type of fuel pre-identified by the fuel purchasing customer for dispensation by any of the plurality of fuel dispensers during subsequent transactions for the purchase of fuel by the customer, and automatically enabling with the first processor the automatically activated one of the plurality of fuel dispensers to dispense the default grade or type of fuel associated in the first or the second database with the first code.

In the first aspect, the identified one of the plurality of fuel dispensers may be configured to selectively dispense any of a plurality of different grades or types of fuel, and the method may further comprise wirelessly receiving a third code, and automatically enabling with the first processor the automatically activated one of the plurality of fuel dispensers to dispense the one of the plurality of different grades or types of fuel identified by the wirelessly received third code.

In the first aspect, the method may further comprise wirelessly transmitting the first and second codes with a mobile electronic device under control of a second processor separate and remote from the first processor and from each of the plurality of fuel dispensers. The method may further still comprise wirelessly transmitting, under control of the second processor, the first code in response to detection at or proximate to the identified one of the plurality of fuel dispensers of a broadcast identification signal, and the broadcast identification signal may carry the corresponding identification code that matches the identification code associated in the first database with the identified one of the plurality of fuel dispensers. The method may further still comprise decoding with the second processor the corresponding identification code from the broadcast identification signal, and wirelessly transmitting, under control of the second processor, the first code as the decoded corresponding identification code. The method may further still comprise wirelessly transmitting, under control of the second processor, the first code as raw signal content of the broadcast identification signal, and decoding with the first processor the corresponding identification code from the raw signal content of the broadcast identification signal wirelessly transmitted as the first code. Any of the methods described in this paragraph may further still comprise wirelessly broadcasting a different broadcast identification signal with each of a plurality of wireless signal broadcasting devices located at or proximate to a different one of the plurality of fuel dispensers, and detecting, with wireless communication circuitry carried by the mobile communication device, the broadcast identification signal broadcast by the wireless signal broadcasting device located at or proximate to the identified one of the plurality of fuel dispensers, and/or further comprise wirelessly transmitting, under control of the second processor, the second code in response to one of detection at or proximate to the identified one of the plurality of fuel dispensers of a broadcast identification signal and a wirelessly received request to transmit the second wirelessly transmitted signal, wherein the broadcast identification signal carries the corresponding identification code that matches the identification code associated in the first database with the identified one of the plurality of fuel dispensers, and/or further comprise wirelessly transmitting, under control of the second processor, the first code and the identification code that matches the identification code associated in the first database with the identified one of the plurality of fuel dispensers in response to manual input into the mobile electronic device of the identification code, and/or further comprise determining geographic coordinates corresponding to a geographic location of the mobile electronic device, and wirelessly transmitting, under control of the second processor, the determined geographic coordinates as the wirelessly transmitted first code, wherein the identification code that matches the wirelessly received identification code corresponds to a geographic location of the identified one of the fuel dispensers.

In a second aspect, a system for remotely enabling fuel dispensation, the system may comprise a plurality of fuel dispensers, a plurality of wireless signal broadcasting devices each located at or near a different one of the plurality of fuel dispensers, at least one database having stored therein a plurality of identification codes each associated with a different one of the plurality of wireless signal broadcasting devices and also with a corresponding one of the plurality of fuel dispensers at or near which each different wireless signal broadcasting device is located, and a plurality of customer codes each associated with a different one of a plurality of customer members of a membership service program and each also associated with a different electronic payment system pre-identified by a corresponding one of the plurality of customer members for automatic payment processing during transactions for the purchase of fuel carried out by the customer member at any of the plurality of fuel dispensers, a processor, and a memory having instructions stored therein which, when executed by the processor, cause the processor to identify, in response to a wirelessly received identification code, the one of the plurality of fuel dispensers associated in the at least one database with the identification code that matches the wirelessly received identification code, to automatically activate, in response to a wirelessly received customer code, the identified one of the plurality of fuel dispensers from an inactive state in which the identified one of the plurality of fuel dispensers is disabled from dispensing fuel to an active state in which the identified one of the plurality of fuel dispensers is enabled to dispense fuel if one of the plurality of customer codes in the at least one database matches the wirelessly received customer code, and to automatically process payment for the purchase of fuel dispensed from the identified one of the plurality of fuel dispensers following activation thereof using the one of the plurality of pre-identified electronic payment systems associated in the at least one database with the matching one of the plurality of customer codes.

In the second aspect, the memory may further have instructions stored therein which, when executed by the processor, cause the processor to automatically activate the identified one of the plurality of fuel dispensers by accessing the one of the plurality of pre-identified electronic payment systems associated in the at least one database with the matching one of the plurality of customer codes, processing the accessed one of the plurality of pre-identified electronic payment systems for payment authorization, and automatically activating the identified one of the plurality of fuel dispensers upon authorization of the accessed one of the plurality of pre-identified electronic payment systems for payment for the purchase of fuel to be subsequently dispensed from the identified one of the plurality of fuel dispensers.

In the second aspect, each of the plurality of customer codes stored in the at least one database may further include a security code, and the memory may further have instructions stored therein which, when executed by the processor, cause the processor to automatically activate the identified one of the plurality of fuel dispensers from the inactive state to the active state thereof further in response to a wirelessly received security code if the security code included in the matching one of the plurality of customer codes matches the wirelessly received security code.

In the second aspect, each of the plurality of fuel dispensers may be configured to selectively dispense any of a plurality of different grades or types of fuel, and each of the plurality of customer codes may be further associated in the at least one database with a default grade or type of fuel corresponding to one of the plurality of different grades or types of fuel pre-selected for dispensation by any of the plurality of fuel dispensers during transactions for the purchase of fuel by the associated one of the plurality of customer members, and the instructions stored in the memory may further include instructions which, when executed by the processor, cause the processor to automatically activate the identified one of the plurality of fuel dispensers from the inactive state thereof to an active state in which the identified one of the plurality of fuel dispensers is enabled to dispense the default grade or type of fuel associated in the at least one database with the one of the plurality of customer codes in the at least one database that matches the wirelessly received customer code.

In the second aspect, each of the plurality of fuel dispensers may be configured to selectively dispense any of a plurality of different grades or types of fuel, and the instructions stored in the memory may further include instructions which, when executed by the processor, cause the processor to automatically enable, in response to a wirelessly received fuel code, the automatically activated one of the plurality of fuel dispensers to dispense one of the plurality of different grades or types of fuel identified by the wirelessly received fuel code.

In the second aspect, each of the plurality of fuel dispensers may be part of a retail enterprise, and the at least one database may have stored therein a plurality of purchase histories each containing a record of purchases previously made from the retail enterprise by a different one of the plurality of customers members of the membership service program, and a plurality of mobile communication device codes each identifying a different mobile communication device carried by different one of the plurality of customer members, and each of the plurality of customer codes may be associated in the at least one database with a different corresponding one of the plurality of purchase histories and also with a different corresponding one of the mobile communication device codes, and the instructions stored in the memory may further include instructions which, when executed by the processor, cause the processor to one of generate and retrieve from the at least one database at least one discount coupon for a product or service from the retail enterprise based on the one of the plurality of purchase histories associated in the at least one database with the one of the plurality of customer codes that matches the wirelessly received customer code, and to wirelessly transmit the at least one discount coupon or notification of the at least one discount coupon to the mobile communication device identified by the one of the plurality of mobile communication device codes associated in the at least one database with the one of the plurality of customer codes that matches the wirelessly received customer code.

In a third aspect, a non-transitory machine-readable medium may comprise a plurality of instructions which, when executed by at least one processor, result in the at least one processor associating in a first database each of the plurality of fuel dispensers with a different identification code, associating in the first or a second database, a first code and an electronic payment system pre-identified by a fuel purchasing customer for automatic payment processing during subsequent transactions for the purchase of fuel by the customer with any of the plurality of fuel dispensers, in response to a wirelessly received identification code, identifying the one of the plurality of fuel dispensers associated in the first database with the identification code that matches the wirelessly received identification code, in response to a wirelessly received second code, automatically activating the identified one of the plurality of fuel dispensers from an inactive state in which the identified one of the plurality of fuel dispensers is disabled from dispensing fuel to an active state in which the identified one of the plurality of fuel dispensers is enabled to dispense fuel if the first code in the first or the second database matches the wirelessly received second code, and automatically processing payment for the purchase of fuel dispensed from the identified one of the plurality of fuel dispensers following activation thereof using the pre-identified electronic payment system associated with the first code in the first or the second database.

In the third aspect, each of the plurality of electromechanically controlled fuel dispensers may be part of a retail enterprise, and the first code may comprise one of a plurality of enterprise membership service identification codes stored in the first or the second database that uniquely identifies a customer as one of a plurality of customer members of an enterprise membership service program associated with the retail enterprise. The plurality of instructions, may further include instructions which, when executed by the at least one processor, result in the at least one processor automatically activating the identified one of the plurality of fuel dispensers by comparing with the wirelessly received second code with the plurality of membership service identification codes, if the wirelessly received second code matches the one of the plurality of membership identification codes, accessing the pre-identified electronic payment system associated in the first or the second database with the one of the plurality of membership identification codes, processing the accessed pre-identified electronic payment system for payment authorization, and automatically activating the identified one of the plurality of fuel dispensers upon authorization of the accessed pre-identified payment system for payment for the purchase of fuel to be subsequently dispensed from the identified one of the plurality of fuel dispensers. Alternatively or additionally, the first or the second database may have stored therein a purchase history containing a record of purchases previously made from the retail enterprise by the identified one of the plurality of customer members of the enterprise membership service program, and the plurality of instructions may further include instructions which, when executed by the at the least one processor, result in the at least one processor associating in the first or the second database the first code with a mobile communication device carried by the identified one of the plurality of customer members of the enterprise membership service program, one of generating and retrieving from the first or the second database at least one discount coupon for a product or service from the retail enterprise based on the purchase history of the identified one of the plurality of customer members of the enterprise membership service program, and wirelessly transmitting to the mobile communication device associated with the first code in the first or the second database the at least one discount coupon or notification of the at least one discount coupon

In the third aspect, the first code in the first or the second database may further comprise a security code, and the plurality of instructions may further include instructions which, when executed by the at least one processor, result in the at least one processor automatically activating the identified one of the plurality of fuel dispensers from the inactive state to the active state thereof is further conditioned upon the security code in the first or the second database matching a wirelessly received third code.

In the third aspect, the identified one of the plurality of fuel dispensers may be configured to selectively dispense any of a plurality of different grades or types of fuel, and the plurality of instructions may further include instructions which, when executed by the at the least one processor, result in the at least one processor associating in the first or the second database the first code and a default grade or type of fuel pre-identified by the fuel purchasing customer for dispensation by any of the plurality of fuel dispensers during subsequent transactions for the purchase of fuel by the customer, and automatically enabling the automatically activated one of the plurality of fuel dispensers to dispense the default grade or type of fuel associated in the first or the second database with the first code.

In the third aspect, the identified one of the plurality of fuel dispensers may be configured to selectively dispense any of a plurality of different grades or types of fuel, and the plurality of instructions may further include instructions which, when executed by the at least one processor, result in the at least one processor automatically enabling the automatically activated one of the plurality of fuel dispensers to dispense one of the plurality of different grades or types of fuel identified by a wirelessly received third code.

In a fourth aspect, a method of remotely activating any of a plurality of electromechanically controlled fuel dispensers each configured to dispense any of a plurality of different grades of fuel may comprise associating, with a first processor in a first database, each of the plurality of fuel dispensers with a different identification code, associating, with the first processor in the first or a second database, a first code with an electronic payment system and also with a default grade of fuel, the electronic payment system pre-identified by a fuel purchasing customer for automatic payment processing during subsequent transactions for the purchase of fuel by the customer at any of the plurality of fuel dispensers, and the default grade of fuel also pre-identified by the fuel purchasing customer as one of the plurality of grades of fuel to be dispensed by any of the plurality of fuel dispensers during subsequent transactions for the purchase of fuel by the customer, in response to a wirelessly received identification code, identifying with the first processor the one of the plurality of fuel dispensers associated in the first database with the identification code that matches the wirelessly received identification code, in response to a wirelessly received second code, automatically activating with the first processor the identified one of the plurality of fuel dispensers from an inactive state in which the identified one of the plurality of fuel dispensers is disabled from dispensing fuel to an active state in which the identified one of the plurality of fuel dispensers is enabled to dispense the default grade of fuel associated in the first database with the first code if the first code in the first or second database matches the wirelessly received second code, and automatically processing with the first processor payment for the purchase of the default grade of fuel dispensed from the identified one of the plurality of fuel dispensers following activation thereof using the pre-identified electronic payment system associated with the first code in the first or the second database.

In a fifth aspect, a method of remotely activating any of a plurality of electromechanically controlled fuel dispensers each configured to dispense any of a plurality of different types of fuel may comprise associating, with a first processor in a first database, each of the plurality of fuel dispensers with a different identification code, associating, with the first processor in the first or a second database, a first code with an electronic payment system and also with a default type of fuel, the electronic payment system pre-identified by a fuel purchasing customer for automatic payment processing during subsequent transactions for the purchase of fuel by the customer at any of the plurality of fuel dispensers, and the default type of fuel also pre-identified by the fuel purchasing customer as one of the plurality of type of fuel to be dispensed by any of the plurality of fuel dispensers during subsequent transactions for the purchase of fuel by the customer, in response to a wirelessly received identification code, identifying with the first processor the one of the plurality of fuel dispensers associated in the first database with the identification code that matches the wirelessly received identification code, in response to a wirelessly received second code, automatically activating with the first processor the identified one of the plurality of fuel dispensers from an inactive state in which the identified one of the plurality of fuel dispensers is disabled from dispensing fuel to an active state in which the identified one of the plurality of fuel dispensers is enabled to dispense the default type of fuel associated in the first database with the first code if the first code in the first or second database matches the wirelessly received second code, and automatically processing with the first processor payment for the purchase of the default type of fuel dispensed from the identified one of the plurality of fuel dispensers following activation thereof using the pre-identified electronic payment system associated with the first code in the first or the second database.

In a sixth aspect, a system for remotely enabling fuel dispensation may comprise a plurality of fuel dispensers, a plurality of wireless signal broadcasting devices each located at or near a different one of the plurality of fuel dispensers, at least one database having stored therein a plurality of identification codes each associated with a different one of the plurality of wireless signal broadcasting devices and also with a corresponding one of the plurality of fuel dispensers at or near which each different wireless signal broadcasting device is located, and a plurality of customer codes each associated with a different one of a plurality of customer members of a membership service program and each also associated with a different electronic payment system preauthorized by a corresponding one of the plurality of customer members for automatic payment processing during transactions for the purchase of fuel carried out by the customer member at any of the plurality of fuel dispensers, and a server coupled to each of the plurality of fuel dispensers, the server including at least one module to identify, in response to a wirelessly received identification code, the one of the plurality of fuel dispensers associated in the at least one database with the identification code that matches the wirelessly received identification code, to automatically activate, in response to a wirelessly received customer code, the identified one of the plurality of fuel dispensers from an inactive state in which the identified one of the plurality of fuel dispensers is disabled from dispensing fuel to an active state in which the identified one of the plurality of fuel dispensers is enabled to dispense fuel if the customer code in the at least one database matches the wirelessly received customer code, and to automatically process payment for the purchase of fuel dispensed from the identified one of the plurality of fuel dispensers following activation thereof using the pre-identified electronic payment system associated with the customer code in the at least one database.

In a seventh aspect, a mobile electronic device may comprise a wireless communication circuit, a display monitor, a processor coupled to the wireless communication circuit and to the display monitor, and a memory. The memory may have instructions stored therein which, when executed by the processor, cause the processor to automatically or in response to user input, control the wireless communication circuit to establish a wireless communication link with one of an electromechanically controlled fuel dispenser and a server coupled thereto that is within a wireless communication range of the mobile electronic device, control the display monitor to display a plurality or a subset of the plurality of different fuels that are dispensable from the fuel dispenser, and in response to user selection of one of the plurality or the subset of the plurality of different fuels displayed on the display monitor, transmit instructions via the wireless communication link to control the fuel dispenser from an inactive state in which the fuel dispenser is inhibited from dispensing fuel to an active state in which the fuel dispenser is enabled to dispense the selected one of the plurality or the subset of the plurality of different fuels.

In an eighth aspect, a mobile electronic device may comprise a wireless communication circuit, a memory, a database, at least one of the memory and the database having stored therein payment information identifying at least one system of payment specific to a user of the mobile electronic device via which payment can be processed for the purchase of fuel, a display monitor, and a processor coupled to the wireless communication circuit and to the display monitor. The memory may have instructions stored therein which, when executed by the processor, cause the processor to automatically or in response to user input, control the wireless communication circuit to establish a wireless communication link with one of an electromechanically controlled fuel dispenser and a server coupled thereto that is within a wireless communication range of the mobile electronic device, control the display monitor to display the payment information, transmit the payment information to the one of the fuel dispenser and the server coupled thereto via the wireless communication link, and in response to receipt by the mobile electronic device from the one of the fuel dispenser and the server coupled thereto, via the wireless communication link, of information indicating that the at least one system of payment identified by the payment information is accepted for processing of payment for the purchase of fuel to be dispensed from the fuel dispenser, control the display monitor to display at least one of (a) a message indicating acceptance of the at least one system of payment identified by the payment information for processing of payment for the purchase of fuel to be dispensed from the fuel dispenser, and (b) a plurality or a subset of the plurality of different fuels that are dispensable from the fuel dispenser.

In a ninth aspect, a method is provided for remotely activating an electromechanically controlled fuel dispenser using a mobile electronic device having a processor coupled to a display monitor and to a wireless communication circuit. The method may comprise automatically or in response to user input to the mobile electronic device, controlling with the processor the wireless communication circuit to establish a wireless communication link with one of the electromechanically controlled fuel dispenser and a server coupled thereto that is within a wireless communication range of the mobile electronic device, controlling the display monitor to display a plurality or a subset of the plurality of different fuels that are dispensable from the fuel dispenser, and in response to user selection of one of the plurality or the subset of the plurality of different fuels displayed on the display monitor, transmitting instructions via the wireless communication link to control the fuel dispenser from an inactive state in which the fuel dispenser is inhibited from dispensing fuel to an active state in which the fuel dispenser is enabled to dispense the selected one of the plurality or the subset of the plurality of different fuels.

In a tenth aspect, a method is provided for remotely activating an electromechanically controlled fuel dispenser using a mobile electronic device having a processor coupled to a display monitor and to a wireless communication circuit, the mobile electronic device having stored therein payment information identifying at least one system of payment specific to a user of the mobile electronic device via which payment can be processed for the purchase of fuel. The method may comprise automatically or in response to user input to the mobile electronic device, controlling with the processor the wireless communication circuit to establish a wireless communication link with one of the electromechanically controlled fuel dispenser and a server coupled thereto that is within a wireless communication range of the mobile electronic device, controlling the display monitor to display the payment information, transmitting the payment information to the one of the fuel dispenser and the server coupled thereto via the wireless communication link, and in response to receipt by the mobile electronic device from the one of the fuel dispenser and the server coupled thereto, via the wireless communication link, of information indicating whether the at least one system of payment identified by the payment information is accepted for processing of payment for the purchase of fuel to be dispensed from the fuel dispenser, controlling the display monitor to display at least one of (a) a message indicating acceptance of the at least one system of payment identified by the payment information for processing of payment for the purchase of fuel to be dispensed from the fuel dispenser, and (b) a plurality or a subset of the plurality of different fuels that are dispensable from the fuel dispenser.

In an eleventh aspect, an electromechanically controlled fuel dispenser may comprise a dispensing section having a nozzle that is manually actuatable to dispense fuel from any of a plurality of different sources of fuel, the dispensing section having an inactive state in which the dispensing section is inhibited from dispensing fuel and an activate state in which the dispensing section is enabled to dispense fuel, and a control section including a wireless communication circuit, a processor coupled to the wireless communication circuit, and a memory. The memory may have instructions stored therein which, when executed by the processor, cause the processor to automatically control the wireless communication circuit to establish a wireless communication link with a mobile electronic device that is within a wireless communication range of the fuel dispenser, and in response to receipt via the wireless communication link of a fuel selection request from the mobile electronic device, control the dispensing section from the inactive state to the active state to enable the fuel dispenser to dispense fuel from the one of the plurality of different sources of fuel identified by the fuel selection request.

In a twelfth aspect, an electromechanically controlled fuel dispenser may comprise a dispensing section having a nozzle that is manually actuatable to dispense fuel from any of a plurality of different sources of fuel, the dispensing section having an inactive state in which the dispensing section is inhibited from dispensing fuel and an activate state in which the dispensing section is enabled to dispense fuel, and a control section including a wireless communication circuit, a processor coupled to the wireless communication circuit, and a memory. The memory may have instructions stored therein which, when executed by the processor, cause the processor to automatically control the wireless communication circuit to establish a wireless communication link with a mobile electronic device that is within a wireless communication range of the fuel dispenser, receive from the mobile electronic device, via the wireless communication link, payment information identifying a system of payment specific to a user of the mobile electronic device via which payment can be processed for the purchase of fuel, transmit the received payment information to a server, separate from the mobile electronic device, for processing thereof, receive from the server a message indicating whether the system of payment identified by the payment information is accepted for processing of payment for the purchase of fuel to be dispensed from the fuel dispenser, and if the message received from the server indicates that the system of payment identified by the payment information is accepted for processing of payment for the purchase of fuel to be dispensed from the fuel dispenser, transmit to the mobile electronic device, via the wireless communication link, at least one of (a) information indicating acceptance of the at least one system of payment identified by the payment information for processing of payment for the purchase of fuel to be dispensed from the fuel dispenser, and (b) information identifying each of the plurality or each of a subset of the plurality of fuel sources dispensable via the fuel dispenser.

In a thirteenth aspect, a method is provided for remotely activating an electromechanically controlled fuel dispenser having a processor coupled to a wireless communication circuit. The method may comprise automatically controlling, with the processor, the wireless communication circuit to establish a wireless communication link with a mobile electronic device that is within a wireless communication range of the fuel dispenser, and in response to receipt via the wireless communication link of a fuel selection request from the mobile electronic device, controlling the fuel dispenser from an inactive state in which the fuel dispenser is inhibited from dispensing fuel to an activate state in which the fuel dispenser is enabled to dispense fuel from one of a plurality of different sources of fuel identified by the fuel selection request.

In a fourteenth aspect, a method may be provided for remotely activating an electromechanically controlled fuel dispenser having a processor coupled to a wireless communication circuit. The method may comprise automatically controlling, with the processor, the wireless communication circuit to establish a wireless communication link with a mobile electronic device that is within a wireless communication range of the fuel dispenser, receiving from the mobile electronic device, via the wireless communication link, payment information identifying a system of payment specific to a user of the mobile electronic device via which payment can be processed for the purchase of fuel, transmitting the received payment information to a server, separate from the mobile electronic device, for processing thereof, receiving from the server a message indicating whether the system of payment identified by the payment information is accepted for processing of payment for the purchase of fuel to be dispensed from the fuel dispenser, and if the message received from the server indicates that the system of payment identified by the payment information is accepted for processing of payment for the purchase of fuel to be dispensed from the fuel dispenser, transmitting to the mobile electronic device, via the wireless communication link, at least one of (a) information indicating acceptance of the at least one system of payment identified by the payment information for processing of payment for the purchase of fuel to be dispensed from the fuel dispenser, and (b) information identifying each of the plurality or each of a subset of the plurality of fuel sources dispensable via the fuel dispenser.

In a fifteenth aspect, a server may be communicatively coupled to an electromechanically controlled fuel dispenser having a dispensing section configured to dispense fuel from any of a plurality of different sources of fuel and a control section including a wireless communication circuit, and the server may comprise a processor, and a memory. The memory may have instructions stored therein which, when executed by the processor, cause the processor to automatically control the wireless communication circuit of the fuel dispenser to establish a wireless communication link with a mobile electronic device that is within a wireless communication range of the fuel dispenser, and in response to receipt by the fuel dispenser, via the wireless communication link, of a fuel selection request from the mobile electronic device, control the dispensing section of the fuel dispenser from an inactive state in which the dispensing section is inhibited from dispensing fuel to an activate state in which the dispensing section is enabled to dispense fuel from one of the plurality of different sources of fuel identified by the fuel selection request.

In a sixteenth aspect, a server may be communicatively coupled to an electromechanically controlled fuel dispenser having a dispensing section configured to dispense fuel from any of a plurality of different sources of fuel and a control section including a wireless communication circuit, and the server may comprise a processor, and a memory. The memory may have instructions stored therein which, when executed by the processor, cause the processor to automatically control the wireless communication circuit of the fuel dispenser to establish a wireless communication link with a mobile electronic device that is within a wireless communication range of the fuel dispenser, receive from the mobile electronic device, via the wireless communication link and the fuel dispenser, payment information identifying a system of payment specific to a user of the mobile electronic device via which payment can be processed for the purchase of fuel to be dispensed from the fuel dispenser, determine whether the system of payment identified by the payment information is acceptable for processing of payment for the purchase of fuel to be dispensed from the fuel dispenser, and if the system of payment identified by the payment information is determined acceptable for processing of payment for the purchase of fuel to be dispensed from the fuel dispenser, instruct the fuel dispenser to transmit to the mobile electronic device, via the wireless communication link, at least one of (a) information indicating acceptance of the at least one system of payment identified by the payment information for processing of payment for the purchase of fuel to be dispensed from the fuel dispenser, and (b) information identifying each of the plurality or each of a subset of the plurality of fuel sources dispensable via the fuel dispenser.

In a seventeenth aspect, a system may comprise a plurality of electromechanically controlled fuel dispensers each having a first wireless communication circuit, a first memory and a first processor coupled to the first wireless communication circuit and to the first memory, each of the plurality of fuel dispensers having an inactive state in which the fuel dispenser is inhibited from dispensing fuel and an active state in which the fuel dispenser is enabled to dispense fuel from any of a plurality of different sources of fuel, and a mobile electronic device having a second wireless communication circuit, a second memory and a second processor coupled to the second wireless communication circuit and the second memory. Each of the first and second memories may have instructions stored therein which, when executed by the first and second respective processors, cause the first and second processors to control the first and second wireless communication circuits respectively to (a) automatically establish a wireless communication link between the second wireless communication circuit and the first wireless communication circuit of a proximate one of the plurality of fuel dispensers that is nearest in proximity to the mobile electronic device, or (b) establish a wireless communication link between the second wireless communication circuit and the first wireless communication circuit of a selected one of the plurality of fuel dispensers, identified by the mobile electronic device in response to a first user input to the mobile electronic device, that is within a wireless communication range of the mobile electronic device, and the second memory may further have instructions stored therein which, when executed by the second processor, cause the second processor to control the proximate or selected fuel dispenser, via the wireless communication link, from the inactive state to the active state to enable the proximate or selected fuel dispenser to dispense fuel from one of the plurality of different sources of fuel identified by the mobile electronic device in response to a second user input to the mobile electronic device.

In an eighteenth aspect, a system may comprise a plurality of electromechanically controlled fuel dispensers each having a first wireless communication circuit, a first memory and a first processor coupled to the first wireless communication circuit and to the first memory, and a mobile electronic device having a second wireless communication circuit, a second memory and a second processor coupled to the second wireless communication circuit and the second memory, the mobile electronic device having stored therein payment information identifying at least one system of payment specific to a user of the mobile electronic device via which payment can be processed for the purchase of fuel. Each of the first and second memories may have instructions stored therein which, when executed by the first and second respective processors, cause the first and second processors to control the first and second wireless communication circuits respectively to (a) automatically establish a wireless communication link between the second wireless communication circuit and the first wireless communication circuit of a proximate one of the plurality of fuel dispensers that is nearest in proximity to the mobile electronic device, or (b) establish a wireless communication link between the second wireless communication circuit and the first wireless communication circuit of a selected one of the plurality of fuel dispensers, identified by the mobile electronic device in response to a first user input to the mobile electronic device, that is within a wireless communication range of the mobile electronic device, and the second memory may further have instructions stored therein which, when executed by the second processor, cause the second processor to control the display monitor to display the payment information, transmit the payment information to the proximate or selected fuel dispenser via the wireless communication link, and in response to receipt by the mobile electronic device from the proximate or selected fuel dispenser, via the wireless communication link, of information indicating that the at least one system of payment identified by the payment information is accepted for processing of payment for the purchase of fuel to be dispensed from the fuel dispenser, control the display monitor to display at least one of (a) a message indicating acceptance of the at least one system of payment identified by the payment information for processing of payment for the purchase of fuel to be dispensed from the fuel dispenser, and (b) a plurality or a subset of the plurality of different fuels that are dispensable from the fuel dispenser.

In a nineteenth aspect, a method may be provided for remotely activating one of a plurality of electromechanically controlled fuel dispensers, each having a first processor and each coupled to a plurality of different sources of fuel, using a mobile electronic device having a second processor. The method may comprise controlling the first and second wireless communication circuits to (a) automatically establish a wireless communication link between the second wireless communication circuit and the first wireless communication circuit of a proximate one of the plurality of fuel dispensers that is nearest in proximity to the mobile electronic device, or (b) establish a wireless communication link between the second wireless communication circuit and the first wireless communication circuit of a selected one of the plurality of fuel dispensers, identified by the mobile electronic device in response to a first user input to the mobile electronic device, that is within a wireless communication range of the mobile electronic device, executing a fuel selection application stored on the mobile electronic device using the second processor, and controlling, via the fuel selection application executing on the mobile electronic device and over the wireless communication link, the proximate or selected fuel dispenser from an inactive state in which the proximate or selected fuel dispenser is inhibited from dispensing fuel to an activate state in which the fuel dispenser is enabled to dispense fuel from one of the plurality of different sources of fuel.

In a twentieth aspect, a method may be provided for remotely activating one of a plurality of electromechanically controlled fuel dispensers, each having a first processor and each coupled to a plurality of different sources of fuel, using a mobile electronic device having a second processor coupled to a display monitor, the mobile electronic device having stored therein payment information identifying at least one system of payment specific to a user of the mobile electronic device via which payment can be processed for the purchase of fuel. The method may comprise controlling the first and second wireless communication circuits to (a) automatically establish a wireless communication link between the second wireless communication circuit and the first wireless communication circuit of a proximate one of the plurality of fuel dispensers that is nearest in proximity to the mobile electronic device, or (b) establish a wireless communication link between the second wireless communication circuit and the first wireless communication circuit of a selected one of the plurality of fuel dispensers, identified by the mobile electronic device in response to a first user input to the mobile electronic device, that is within a wireless communication range of the mobile electronic device, executing a fuel selection application stored on the mobile electronic device using the second processor, selecting, via the fuel selection application executing on the mobile electronic device and over the wireless communication link, the payment information identifying the at least one system of payment, transmitting to the proximate or selected fuel dispenser, via the wireless communication link, the selected payment information, and if the at least one system of payment identified by the selected payment information is accepted for processing of payment for the purchase of fuel to be dispensed from the fuel dispenser, controlling the display monitor to display at least one of (a) a message indicating acceptance of the at least one system of payment identified by the payment information for processing of payment for the purchase of fuel to be dispensed from the fuel dispenser, and (b) a plurality or a subset of the plurality of different fuels that are dispensable from the fuel dispenser.

DESCRIPTION OF THE ILLUSTRATIVE EMBODIMENTS

For the purposes of promoting an understanding of the principles of the invention, reference will now be made to a number of illustrative embodiments shown in the attached drawings and specific language will be used to describe the same.

In the following description, numerous specific details such as logic implementations, resource partitioning/sharing/duplication implementations, types and interrelationships of system components, and logic partitioning/integration choices are set forth in order to provide a more thorough understanding of the present disclosure. Control structures, gate level circuits, driver circuits and full software instruction sequences have not been shown in detail in order not to obscure the disclosure. It will be appreciated, however, by one skilled in the art that embodiments of the disclosure may be practiced without such specific details. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.

References in the specification to “one embodiment”, “an embodiment”, “an example embodiment”, “one illustrative embodiment” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases may or may not necessarily refer to the same embodiment. Further, when a particular feature, structure, process, process step or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, process, process step or characteristic in connection with other embodiments whether or not explicitly described. Further still, it is contemplated that any single feature, structure, process, process step or characteristic disclosed herein may be combined with any one or more other disclosed feature, structure, process, process step or characteristic, whether or not explicitly described, and that no limitations on the types and/or number of such combinations should therefore be inferred.

Embodiments of this disclosure may be implemented in hardware, firmware, software, or any combination thereof. Embodiments implemented in a computer system may include one or more bus-based interconnects between components and/or one or more point-to-point interconnects between components. Embodiments of this disclosure may also be implemented as instructions stored on one or more machine-readable media, which may be read and executed by one or more processors. As used herein, the term “machine-readable medium,” and variants thereof, refers generally to non-transient data storage media and excludes any transitory signals. A machine-readable medium may be embodied as any device or physical structure for storing or transmitting information in a form readable by a machine (e.g., a computing device). For example, a machine-readable medium may be embodied as any one or combination of read only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory device, and/or other conventional machine-readable storage medium.

The terms “customer,” “fuel purchaser,” “purchaser” and “user,” and variants thereof, are used interchangeably in the following description. Such terms should be understood to define and refer to any purchaser of fuel from a retail fueling station including, but not limited to, an operator and/or any passenger of a motor vehicle to be or being refueled, an operator and/or any passenger of a motorized or non-motorized vehicle carrying, towing or otherwise transporting a motor vehicle to be or being refueled, an operator and/or any passenger of a motorized or non-motorized vehicle carrying, towing or otherwise transporting a fuel container to be or being filled with fuel, or the like. The terms “inactive,” “inactive state,” “inactivated state,” “inactive operational state,” “deactivate,” “deactivation,” and variants thereof, used herein with reference to an electromechanically controlled fuel dispenser, are defined for purposes of this disclosure as an operational state (or in the case of “deactivate” or “deactivation” to control to an operational state) of the fuel dispenser in which the fuel dispenser generally, and the dispensing section of the fuel dispenser in particular, is inhibited or prevented from dispensing fuel of any type or grade. The terms “active,” “activate state,” “activated state,” “activate,” “activation,” and variants thereof, used herein with reference to an electromechanically controlled fuel dispenser, are defined for purposes of this disclosure as an operational state (or in the case of “activate” or “activation” to control to an operational state) of the fuel dispenser in which the fuel dispenser generally, and the dispensing section of the fuel dispenser in particular, is enabled to dispense a selected fuel type and/or grade from a source of fuel of the selected type and/or grade.

Referring now toFIG. 1, a system10is shown for wirelessly activating an electromechanical fuel dispenser for subsequent dispensation of fuel, for carrying out the subsequent fuel dispensation process through completion and for providing wirelessly connected purchasers of fuel with purchaser-specific discount rewards/offers for one or more goods and/or services offered for sale by an enterprise via which the fuel is purchased. In the illustrated embodiment, the system10includes a main server12coupled via a private network14to one or more local hub servers161-16K, with each local hub server161-16Kcoupled to one or more electromechanical fuel dispensers181-18N,181-18M; e.g., K, N and M may each be any positive integer. Each fuel dispenser181-18N,181-18Mis configured to be enabled and ready to be manually manipulated to dispense a selected fuel type and/or grade after being controlled from an inactive state to an active state. As described in more detail below, a wireless communication link may be selectively established between a fuel dispenser181-18N,181-18M(and/or a corresponding one of the local servers161-16K) and a mobile communication device80(and/or a vehicle communication device90), and the fuel dispenser may then be wirelessly and remotely activated via the wireless communication link using the mobile communication device80(and/or the vehicle communication device90). In one embodiment, the fuel dispenser181-18N,181-18Mmay, once activated, be manually controlled in a conventional manner to dispense a type and/or grade of fuel selected as part of the remote activation process. In alternate embodiments, the fuel dispenser activation process may be partially carried out wirelessly and remotely using the mobile communication device80(and/or the vehicle communication device90), and then completed by manually selecting the fuel type and/or grade. In any case, the ability to wirelessly and remotely activate, or partially activate, an electromechanically controlled fuel dispenser for subsequent dispensation of fuel effectively reduces the amount of time required to be spent manually manipulating the fuel dispenser during fuel purchase transactions, thus providing for a number of attendant benefits.

In some embodiments, the enterprise served by the main (or “enterprise”) server is12a retail enterprise that offers for sale goods and/or services in addition to fuel. As will be further described below, the main server12in some such embodiments illustratively hosts an enterprise member services (EMS) program which includes or otherwise has access to a database containing a plurality of virtual customer rewards repositories each configured to store and manage virtual rewards/offers for a different one of a corresponding plurality of customer-members of the EMS program. The EMS program further illustratively includes a customer purchase history database containing purchase histories of one or more customers of the retail enterprise. In addition to virtual discount coupons offered to all customers of the EMS program, the EMS program also illustratively includes, in some embodiments, a customized reward/offer feature in which the purchase history of each customer-member is collected over time and stored, and customer-specific rewards or offers for goods and/or services offered for sale by the enterprise are then generated from a database of rewards/offers based on the customer's purchase history. Such customer-specific rewards or offers are then typically stored in the customer's rewards repository in the form of virtual rewards or offers; i.e., virtual discount coupons, that may be subsequently redeemed by the customer toward the purchase of corresponding products and/or services offered for sale by the enterprise. As used herein, the term “enterprise member services program,” “enterprise membership services program” or EMS and “shopper membership service” are interchangeable and refer to a shopper or customer service which may offer to customer members one or more services such as making available to customers one or more virtual discount coupons that may be redeemable by the retail enterprise against the purchase of from the retail enterprise of various goods, which may include fuel, and/or services and/or tracking and maintaining customer purchase histories in the customer purchase history database accessible by the main server12. In this regard, the terms “shopper membership account” and “EMS account” are likewise interchangeable and refer to a mechanism by which the retail enterprise may make available to customers one or more virtual discount coupons and/or by which a customer's purchase history and information about the customer can be maintained by the main server12in a database separately from purchase histories of and information about other customers. Further in this regard, the term “EMS identification code” or EMSID illustratively refers to at least one collection of letters, symbols and/or numbers that is different for, and therefore unique to, each customer member of the enterprise membership services program, and which is used to uniquely identify a customer's EMS account within the enterprise membership services program. In one embodiment, for example, the EMSID for each customer may include a unique, several-digit access code and a separate and unique, several-digit password, although in other embodiments the EMSID may include more, fewer and/or different codes and/or passwords.

As will be discussed in further detail below, the main server12illustratively includes an EMS module that manages and controls a customer-member interface, e.g., a web-based interface, to the EMS program via which customers can access and manage their individual EMS accounts. Illustratively, each customer may access their individual (and private from other customer-members) EMS account, i.e., their individual EMS page(s) within the web-based EMS interface, which may be referred to hereinafter as an “EMS website,” by entering that customer's EMSID into a graphic user interface element of the web-based EMS interface. Therein, the customer may access, establish, modify and otherwise manage the customer's EMS account information including, for example, but not limited to, name, address, email address, mobile telephone number and, as will be described in greater detail below in relation to various embodiments illustrated inFIGS. 14A-22, at least one of a preferred or preselected fuel grade and/or type and electronic payment information (EPI) associated with one or more forms of electronic payment.

The main server12may serve an enterprise of any conceivable size and/or diversity that offers a range of consumer products and/or services via one or more retail outlets, e.g., brick-and-mortar outlets, and/or via one or more on-line shopping services, e.g., one or more publicly-accessible or privately-accessible web sites hosted by an enterprise and accessible via a system of interconnected computer networks, e.g., the Internet, using a web browser. The latter may be referred to herein as a “virtual” or “on-line” shopping outlet or service, and the combination of one or more retail outlets and one or more on-line shopping outlets may be referred to herein as a so-called “bricks-and-clicks” enterprise. In any case, the customer purchase histories may be as equally as diverse as the enterprise, and may therefore include a narrow or a wide range of product and/or service purchases, or any range in between. Customer-specific rewards or offers may be provided in the form of discount rewards or offers, e.g., virtual discount coupons, for the purchase of any one or combination of products and/or services offered for sale by the enterprise.

As briefly described above, each customer-member of the EMS program is illustratively assigned, or selects, a unique EMS identification code (EMSID). In one embodiment, the mobile communication device80or a vehicle communication device90illustratively provides the customer's EMSID to the fuel dispenser181-18N,181-18M(or to a corresponding one of the local servers161-16K, or to the main server12) when a wireless communication link82is established therebetween. In such embodiments the fuel dispenser181-18N,181-18M(or a corresponding one of the local servers161-16K) to which the mobile communication device80or vehicle communication device90is wirelessly linked passes the EMSID to the main or enterprise server12, or the mobile communication device80or vehicle communication device90passes the EMSID directly to the main or enterprise server12The main or enterprise server12is thus notified whenever an EMS customer-member is in wireless communication, i.e., linked by a wireless communication connection, with an enterprise fuel dispenser181-18N,181-18M(or a corresponding one of the local servers161-16Kor with the main server12) for the purpose of purchasing fuel. In such embodiments, the main server12illustratively includes a rewards/offer module via which the main server12can determine and push one or more customer-specific rewards/offers to any EMS customer-member by transmitting the customer-specific rewards/offers to the enterprise fuel dispenser181-18N,181-18M(or a corresponding one of the local servers161-16K) to which the EMS customer-member is wirelessly linked, along with instructions to cause the enterprise fuel dispenser181-18N,181-18M(or a corresponding one of the local servers161-16K) to wirelessly transmit the one or more customer-specific rewards/offers to the wirelessly linked mobile communication device80or vehicle communication device90, or via which the main server12can determine and push one or more such rewards/offers directly to any such EMS customer-member by wirelessly transmitting such customer-specific rewards/offers directly to the customer-member's mobile communication device80or vehicle communication device90. Because such wirelessly connected EMS customer-members are presently in the process of purchasing fuel at an enterprise fueling station, the customer-specific rewards/offers, e.g., virtual discount coupons, may be specifically tailored to fuel-related discounts or rewards, e.g., a fuel unit price discounts, upgrades to higher grade fuel, etc., to discounts or rewards at the co-located enterprise fueling station, e.g., free soft drink, 2-for-1 hot dogs, discounted or free car wash, etc., and/or to discounts or rewards at one or more enterprise fueling stations located elsewhere. Alternatively or additionally, the customer-specific rewards/offers may be specifically tailored to discounts or rewards at one or more non-fuel-related retail outlets owned and/or operated by the enterprise.

In the embodiment illustrated inFIG. 1, the main server12is illustratively connected to one or more local servers161-16Kvia a private network14, and each local server161-16Kis illustratively implemented at a fueling (or filling) station, i.e., a fuel sales facility or “fuel center”,521-52Krespectively. Some retail enterprises may include a single brick and mortar fuel sales facility52, and other larger enterprises may include two or more physically remote brick and mortar fuel sales facilities521-52K. In the latter case, the retail enterprise may include, for example, at least one main business facility with two or more remote brick and mortar fuel sales facilities, and for purposes of this document the two or more remote brick and mortar fuel sales facilities521-52Kin such an arrangement are referred to as fuel sales “hubs.” In this disclosure, the system10will be illustrated and described in the context of such a larger retail enterprise having at least one main business facility located remotely from two or more fuel sales hubs. In this regard, the main server12in the system10shown inFIG. 1will typically be located at a main business location of the retail enterprise, and will be coupled via the network14to two or more local servers161-16K, each of which will typically be located at a different one of the two or more hub locations521-52K.

Each of the hub locations521-52Kmay include any number of electromechanically controlled fuel dispensers communicatively coupled to a corresponding local server, and in the embodiment illustrated inFIG. 1, for example, the local server161is communicatively coupled to “N” such electromechanically controlled fuel dispensers181-18N, where N may be any positive integer, and the local server16Kis communicatively coupled to “M” such electromechanically controlled fuel dispensers181-18M, where M may be any positive integer (and where M may or may not be equal to N). Communicative coupling between the local server161and the one or more electromechanically controlled fuel dispensers181-18N, and between the local hub server16Kand the one or more electromechanically controlled fuel dispensers181-18M, may be accomplished using any known communication coupling, and communications over any such hardwire and/or wireless coupling may be accomplished using any known communication protocol.

In some alternative embodiments of such a large retail enterprise, one or more of the local servers161-16Kmay be omitted, and the main server12may be coupled directly, via the network14, to the one or more electromechanically controlled fuel dispensers181-18N,181-18M, or the main server12may be omitted and at least one of the local servers161-16Kmay be configured to act as a so-called master server with the remaining local servers161-16Kconfigured to act as so-called slave servers. In other alternative embodiments in which the retail enterprise includes only a single brick and mortar fuel sales facility, the local servers161-16Kmay be omitted and the main server12may be coupled directly, e.g., via a wired or wireless interface, to one or more electromechanically controlled fuel dispensers, e.g.,181-18Nor181-18M, or the main server12and all but one local server, e.g.,161, may be omitted and the sole local server, e.g.,161, may be coupled directly, e.g., via a wired or wireless interface, to one or more electromechanically controlled fuel dispensers, e.g.,181-18N.

For purposes of the following description, any process disclosed as being controlled by the main server12may, in some embodiments, instead be controlled, in whole or in part, by one or more local servers161-16K, and/or may be controlled, in whole or in part, by one of the electromechanically controlled fuel dispensers181-18N,181-18M. Likewise, any process disclosed as being controlled by any of the local servers161-16Kmay, in some embodiments, instead be controlled, in whole or in part, by the main server12, and/or may be controlled, in whole or in part, by one of the electromechanically controlled fuel dispensers181-18N,181-18M. Further still, any process disclosed as being controlled by any of the electromechanically controlled fuel dispensers181-18N,181-18Mmay, in some embodiments, instead be controlled, in whole or in part, by one or more of the local servers161-16K, and/or may be controlled, in whole or in part, by the main server12.

The main server12may be embodied as any type of server (e.g., a web server) or similar computing device capable of performing the functions described herein. In the illustrative embodiment ofFIG. 1, the main server12includes a processor20, an I/O subsystem22, a memory24, a data storage26, a communication circuitry28, and one or more peripheral devices30. It should be appreciated that the main server221may include other components, sub-components, and devices commonly found in a sever and/or computing device, which are not illustrated inFIG. 1for clarity of the description.

The processor20of the main server12may be embodied as any type of processor capable of executing software/firmware, such as a microprocessor, digital signal processor, microcontroller, or the like. The processor20may be a single processor or include multiple processors. The I/O subsystem22of the main server12may be embodied as circuitry and/or components to facilitate input/output operations with the processor20and/or other components of the main server12. The processor20is communicatively coupled to the I/O subsystem22.

The memory24of the main server12may be embodied as or otherwise include one or more conventional volatile and/or non-volatile memory devices. The memory24is communicatively coupled to the I/O subsystem22via a number of signal paths. Although only a single memory device24is illustrated inFIG. 1, the main server12may include additional memory devices in other embodiments. Various data and software may be stored in the memory24. The data storage26is also communicatively coupled to the I/O subsystem22via a number of signal paths, and may be embodied as any type of device or devices configured for the short-term or long-term storage of data such as, for example, memory devices and circuits, memory cards, hard disk drives, solid-state drives, or other data storage devices.

The communication circuitry28of the main server12may include any number of devices and circuitry for enabling and controlling communications between the main sever12and the one or more local servers161-16K, and/or for enabling and controlling communications between the main server12and any one or more of the fuel dispensers181-18N,181-18M, any of one or more mobile communication devices80and/or any of one or more vehicle communication devices90. In the illustrated embodiment, for example, communication between the main server12and the one or more local servers161-16Ktakes place wirelessly via the network14, wherein the network14may represent, for example, a private local area network (LAN), a personal area network (PAN), a storage area network (SAN), a backbone network, a global area network (GAN), a wide area network (WAN), or collection of one or more of any such computer networks such as an intranet, extranet or the Internet (i.e., a global system of interconnected networks upon which various applications and/or services run including, for example, the World Wide Web (WWW)). In alternative embodiments, the communication path between the main server12and the one or more local servers161-16Kmay be a non-private network and/or may be, in whole or in part, a wired connection.

Generally, the communication circuitry28may be configured to use any one or more, or combination, of conventional secure and/or unsecure communication protocols to conduct communications between the main server12and the one or more local servers161-16K. As such, the network14may include any number of additional devices, such as additional computers, routers, and switches, to facilitate communications between the main server12and the one or more local servers161-16K. Communication between the one or more local servers161-16Kand the one or more electromechanically controlled fuel dispensers181-18N,181-18Mmay take place via one or more conventional wired or wireless communication interfaces.

In some embodiments, the main server12may also include one or more peripheral devices30. Such peripheral devices30may include any number of additional input/output devices, interface devices, and/or other peripheral devices. For example, the peripheral devices30may include one or more conventional displays, keyboards, point-and-select devices, audio processing circuits, and/or other input/output devices.

An embodiment of one of the local servers, e.g.,161, is also illustrated inFIG. 1, and generally includes the same components as the main server12. For example, a processor40is coupled to an I/O subsystem42, and the I/O subsystem42is coupled to a memory44, a data storage unit46, communication circuitry48and one or more peripheral devices50. In some embodiments, each of the foregoing components may be identical to corresponding components of the main server12described above, and a detailed explanation of such components will not be repeated here for brevity. In other embodiments, the local server161may be configured differently than the main server12described above. In any case, the communication circuitry48of the local server161facilitates communication with the communication circuitry28of the main server12and vice versa so that information can be shared between the main server12and the local server161via the network14. Although only one such main server12is shown inFIG. 1, it should be appreciated that, in other embodiments, the system10may include any number of main servers.

The local server16K, as well as any additional local server(s), may be substantially similar to the local server161and include similar components. As such, the description provided above of the components of the local server161may be equally applicable to such similar components of the local server16Kand are not repeated here so as not to obscure the present disclosure. Further details of one illustrative embodiment of an example one of the local servers161-16Kwill be provided below with respect toFIG. 7. Of course, it should be appreciated that in some embodiments one or more of the local servers161-16Kmay be dissimilar to others of the local servers161-16K.

Referring still toFIG. 1, an embodiment of one, e.g.,181, of the plurality of electromechanically controlled fuel dispensers181-18N,181-18Mare shown. In the illustrated embodiment, the electromechanically controlled fuel dispenser181generally includes the same components as the main server12and each of the local servers161-16K. For example, a processor60is coupled to an I/O subsystem62, and the I/O subsystem62is coupled to a memory64, a data storage unit66, communication circuitry68and one or more peripheral devices70. In some embodiments, each of the foregoing components may be identical to corresponding components of the main server12described above, and a detailed explanation of such components will not be repeated here for brevity. In other embodiments, the fuel dispenser181may be configured differently than the main server12described above. In embodiments that include one or more local servers161-16K, the communication circuitry68of the fuel dispenser181facilitates communication with the communication circuitry48of a corresponding one of the local servers161-16Kand vice versa so that information can be shared between the fuel dispenser181and the corresponding one of the local servers161-16Kvia a wired or wireless communication interface. In alternate embodiments that do not include any local servers161-16Kand in which the main server12is coupled directly to the one or more fuel dispensers181-18N(and/or181-18M), the communication circuitry68of the fuel dispenser181facilitates communication with the communication circuitry28of main server12and vice versa so that information can be shared between the fuel dispenser181and the main server12via the network14.

The electromechanically controlled fuel dispenser18N, as well as any additional fuel dispensers, may be substantially similar to the fuel dispenser181and include similar components. As such, the description provided above of the components of the fuel dispenser18Nmay be equally applicable to such similar components of the fuel dispenser181and are not repeated here so as not to obscure the present disclosure. Of course, it should be appreciated that in some embodiments one or more of the electromechanically controlled fuel dispensers181-18N,181-18Mmay be dissimilar to others of the fuel dispensers181-18N,181-18M. As further illustrated inFIG. 1, the fuel dispenser181is shown coupled via a fuel hose72to a fuel inlet orifice of a conventional motor vehicle78. Each of the fuel dispensers181-18N,181-18Mare so equipped, with one end of the fuel hose72coupled to a conventional nozzle74sized to be received within the fuel inlet orifice of the motor vehicle. Further details of one illustrative embodiment of an example one of the electromechanically controlled fuel dispensers181-18N,181-18Mwill be provided below with respect toFIG. 2.

In some embodiments, a mobile communication device80may be carried by an operator84(or a passenger) of the motor vehicle78, and in such embodiments the mobile communication device80may be configured to communicate wirelessly with the fuel dispenser181via a wireless communication link established between the communication circuitry68of the fuel dispenser181and communication circuitry carried by the mobile communication device80. Alternatively or additionally, a vehicle communication device90may be embedded or carried by the motor vehicle78, and in embodiments the vehicle communication device90may be configured to communicate wirelessly with the fuel dispenser181via a wireless communication link established between the communication circuitry68of the fuel dispenser181and communication circuitry carried by the vehicle communication device90. Alternatively or additionally still, the mobile communication device80and/or the vehicle communication device90may be configured to communicate wirelessly with a corresponding one of the local servers161-16K(or the main server12) via a wireless communication link established between the communication circuitry48of the corresponding one of the local servers161-16K(or the communication circuitry28of the main server12) and communication circuitry carried by the mobile communication device80and/or the vehicle communication device90.

The mobile communication device80may illustratively be any mobile, e.g., hand-held, electronically controlled device capable of establishing a wireless communication link with at least one of the electromechanically controlled fuel dispensers181-18N,181-18M, at least one of the local servers161-16Kand/or the main server12, and of executing instructions for remotely activating one of the electromechanically controlled fuel dispensers181-18N,181-18Mvia such a wireless communication link. For example, the mobile communication device80may be embodied as, without limitation, a portable computer such as a tablet computer, a laptop computer, a notebook computer, or other mobile computing device, a smart phone, a cellular telephone, or the like. It will be understood that a customer may use multiple different mobile communication devices80to remotely activate one of the fuel dispensers181-18N,181-18M, and/or that multiple customers may use a single mobile communication device80to remotely activate one of the fuel dispensers181-18N,181-18M. Further details of one illustrative embodiment of the mobile communication device80will be provided below with respect toFIGS. 3 and 5.

The vehicle communication device90may illustratively be any electronically controlled device mounted in, embedded in or carried by the motor vehicle76that is capable of establishing a wireless communication link with at least one of the electromechanically controlled fuel dispensers181-18N,181-18M, at least one of the local servers161-16Kand/or the main server12, and of executing instructions for remotely activating one of the electromechanically controlled fuel dispensers181-18N,181-18Mvia such a wireless communication link. For example, the vehicle communication device90may be embodied as or form part of, without limitation, a vehicle navigation system, a vehicle entertainment system, an in-vehicle information system, or the like. Further details of one illustrative embodiment of the vehicle communication device90will be provided below with respect toFIGS. 4 and 6.

In some embodiments, the mobile communication device80is configured, as will be described in detail below, to wirelessly and remotely activate one of the fuel dispensers181-18N,181-18M, via a wireless communication link82established between the mobile communication device80and the fuel dispenser or via a wireless communication link established between the mobile communication device80and a corresponding one of the local servers161-16K(or the main server12), for subsequent dispensation of fuel. In some alternate embodiments, the vehicle communication device90may instead be so configured to wirelessly and remotely activate one of the fuel dispensers181-18N,181-18M, via a wireless communication link established between the vehicle communication device90and the fuel dispenser or via a wireless communication link established between the vehicle communication device90and a corresponding one of the local servers161-16K(or the main server12), for subsequent dispensation of fuel. In still other alternate embodiments, the mobile communication device80and the vehicle communication device90may each be configured to separately or together wirelessly and remotely activate one of the fuel dispensers181-18N,181-18M. In this regard, the term “mobile electronic device,” as used herein, may refer to and mean the mobile communication device80or the vehicle communication device90, or alternatively to the combination of the mobile communication device80and the vehicle communication device90operating together.

Referring now toFIG. 2, a simplified block diagram is shown of an embodiment of some of the features of an example one,18, of the one or more electromechanically controlled fuel dispensers181-18N,181-18Millustrated inFIG. 1. In the illustrated embodiment, for example, the fuel dispenser18includes an identification number or code (ID)200mounted to or integral with the fuel dispenser18. In one embodiment, the ID200is illustratively sized to be large enough to be visible by occupants of the motor vehicle76and, in some embodiments, by an attendant of the corresponding hub location521-52K. The ID200may illustratively be any one or combination of letters, numbers, symbols or the like. In some alternative embodiments, the ID200may be or include a conventional barcode or a 2-dimensional machine-readable code, e.g., a matrix barcode or quick response (QR) code, that may be scanned or otherwise captured, e.g., via a camera, of a mobile communication device80for the purpose of identifying the particular fuel dispenser18. In any case, the fuel dispenser18further includes hardware infrastructure202in the form of, for example, one or more frames, brackets, shelves and the like to house and support the various electromechanical components and to mount the fuel dispenser at a suitable location relative to the corresponding hub location521-52K.

The fuel dispenser18further includes a fuel dispensing section204which includes a number of conventional actuators and sensors206coupled to one or more conventional fuel pumps208, to one or more conventional fuel hose/nozzle combinations72/74and electrically connected to one or more conventional controllers210that form(s) part of the peripheral devices70of the fuel dispenser18. The one or more fuel pumps208is/are fluidly coupled to a plurality of different sources, e.g., storage containers, of fuel212via suitable fluid flow conduits. Prior to operating the fuel dispensing section204, the nozzles74of the one or more hose/nozzle combinations72/74are typically removably mounted within and supported by a storage receptacle defined by the fuel dispenser18.

The fuel dispensing section204is manually operable or actuatable in a conventional manner to dispense fuel from one of the sources of fuel212via one of the hose/nozzle combinations72/74when the fuel dispensing section204of the fuel dispenser18is activated, e.g., by effecting payment and/or selecting an appropriate fuel type and/or grade. For example, a selected one of the nozzles74is manually withdrawn from its storage receptacle on the fuel dispenser18and inserted into a fuel inlet orifice of the motor vehicle76or suitable fuel storage container. When the fuel dispenser18is activated, a lever carried by the selected nozzle74(and forming one of the actuators206) is manually actuated to start and stop the flow of fuel from a selected one of the fuel sources212through the selected nozzle74. Fuel flow control is accomplished by the processor60, which executes conventional instructions stored in the memory64of the fuel dispenser18to control the one or more controllers210to cause one or more of the actuators206to engage and control at least one of the fuel pumps208to pump fuel from a selected one of the fuel sources212through one of the hose/nozzle combinations72/74. In one embodiment, the plurality of different sources of fuel212dispensable from the fuel dispenser18includes sources of at least two or more different grades, i.e., octane ratings, of gasoline. In another embodiment, the plurality of different sources of fuel212dispensable from the fuel dispenser18includes at least one grade, i.e., octane rating, of gasoline and at least one type of diesel fuel. It will be understood, however, that this disclosure does not place any limitations on the number, type and/or grade of different fuels that may be dispensed from the fuel dispenser18. In this regard, the plurality of different sources of fuel212may include any number, types and/or grades of known fuel, liquid or otherwise, examples of which may include, but are not limited to, any grade, i.e., octane rating, of gasoline (e.g., petrol), any grade or type (e.g., petroleum-derived or otherwise) of diesel fuel, compressed natural gas (CNG), compressed hydrogen (CH), a mixture of compressed natural gas and hydrogen (HCNG), liquefied petroleum gas (LPG), Ethanol, biofuel, biodiesel, Kerosene, and the like.

The fuel dispenser18illustrated inFIG. 2further includes a number of additional peripheral devices70including, for example, one or more conventional display monitors214, one or more conventional keypads216and one or more conventional payment interfaces218. The one or more conventional payment interfaces218may include at least one conventional payment interface configured to read and identify, e.g., via magnetic stripe, radio-frequency identification tag (RFID), or the like, a pre-paid debit medium, e.g., pre-paid debit card, and/or a charge/credit medium, e.g., credit or debit card. In some embodiments, the one or more payment interfaces218may further include at least one conventional payment interface configured to accept and process cash. In any case, the one or more payment interfaces218are manually operated in a conventional manner to process payment for the purchase of fuel dispensed by, or to be dispensed by, the fuel dispenser18.

In some embodiments, the peripheral devices70further include a number of conventional fuel grade selectors220each identifying a different source212of, e.g., a particular grade, i.e., octane rating, of gasoline. Alternatively or additionally, the peripheral devices70may also include at least one conventional alternate fuel selector222identifying at least one alternate source212of fuel, e.g., diesel fuel. In any case, each of the fuel grade selectors220and the at least one alternate fuel grade selector222are manually-actuated switches or buttons requiring manual selection thereof. Selection of one of the plurality of different fuel sources212from which to dispense fuel via the fuel dispenser18is conventionally accomplished by manual selection of one of the number of fuel grade selectors220or the at least one alternative fuel selector222.

In some embodiments, the peripheral devices70may further include one or more conventional electronic beacons224, e.g., conventional radio beacons, for the purpose of transmitting radio signals carrying information corresponding to the location and/or identity of the fuel dispenser18. At least one such beacon224may be mounted to or near the fuel dispenser18, and is illustratively configured to periodically broadcast one or more unique wireless identification signals, i.e., one or more identification signals that distinguish the particular beacon224from other beacons224, e.g., other beacons224associated with other fuel dispensers18. In some alternate embodiments, the at least one beacon224may be configured to broadcast one or more unique wireless signals non-periodically. In some embodiments, each fuel dispenser18has a single beacon224associated therewith, i.e., located at or near the fuel dispenser18. In other embodiments, each fuel dispenser18may have two or more beacons224, e.g., a “set” of beacons224, associated therewith. In such embodiments, each set of beacons224may illustratively be configured to periodically broadcast a wireless identification signal that is identical to those in the set of beacons but different and distinguishable from the wireless identification signals broadcast by all other beacons224, e.g., those associated with other fuel dispensers18. Alternatively, each set of beacons224may be configured to periodically broadcast a wireless identification signal that is different and distinguishable from the wireless identification signals broadcast by those beacons224within the set of point-of-sale beacons224and that is also different and distinguishable from the wireless identification signals broadcast by all other beacons within the retail enterprise.

In some embodiments, the one or more beacons224are each configured to periodically broadcast wireless identification signals in the radio frequency (RF) range, although any of the one or more beacons224may be configured to alternatively broadcast wireless identification signals in one or more other frequency ranges. In any case, the one or more beacons224are further each configured to broadcast wireless identification signals with a predefined broadcast range and/or orientation (i.e., direction). Illustratively, the broadcast range of each beacon224is sufficiently large, wide and/or oriented to be detected by mobile communication devices80and/or vehicle communication devices90carried by customers during a normal fuel stop, e.g., during refueling of a vehicle or other container from a fuel dispenser18, while is at the same time sufficiently small, narrow and/or oriented so as not to be detected by mobile communication devices80and/or vehicle communication devices90of customers being processed by one or more adjacent fuel dispensers18.

Illustratively, the unique wireless identification signals broadcast by each beacon224carry decodable information in the form of a unique identification code (UID). Generally, the UID of each beacon224, or in some embodiments each set of beacons224, uniquely identifies that beacon224and distinguishes that beacon224from all other beacons within the retail enterprise or at least those associated with one or more other fuel dispensers18located at a common fuel center52. In some embodiments, the UID may further include, and/or the unique wireless identification signals broadcast by the one or more beacons224may additionally carry, beacon type information in the form of a beacon type code (BT). Generally, the beacon type code, BT, identifies the general location or use of the beacon224within the retail enterprise. Example beacon types may include, but should not be limited to, fuel dispenser beacons, fuel center beacons, point-of-sale beacons, brick-and-mortar and/or fuel center location entrance beacons, beacons associated with specific departments or product category locations within the retail enterprise, general store location beacons, or the like. The beacon type code, BT, of each beacon224, in embodiments in which include the beacon type code, BT, is thus a fuel dispenser beacon or “FD beacon.” Those skilled in the art will recognize additional and/or alternative information that may be included within or appended to the UID, and/or carried by the unique wireless identification signals broadcast by the one or more beacons224, and it will be understood that any such additional and/or alternative information is contemplated by this disclosure.

The beacon224illustrated inFIG. 2and just described above represent only one example of a wireless signal broadcasting device that may be included in the peripheral devices212of the various fuel dispensers181-18N,181-18M, and that may be located at or near one or more of the fuel dispensers181-18N,181-18Mfor the purpose of broadcasting one or more unique wireless identification signals. Those skilled in the art will recognize other wireless signal broadcasting devices that may be substituted for one or more of the beacons224, and it will be understood that any such other wireless signal broadcasting devices are contemplated by this disclosure. Any one or more such alternate wireless signal broadcasting device may be operable to broadcast one or more unique wireless identification signals periodically or non-periodically in any frequency range with any orientation or direction and/or having any broadcast range, and decodable information carried by such one or more unique wireless identification signals may illustratively include, in addition to a unique identification code, UID, a beacon type code (BT) and/or other additional and/or alternative information that may be included within or appended to the UID.

In addition to circuitry for facilitating communication with the local server161, the communication circuitry68of the fuel dispenser18further includes a conventional wireless communication circuit230via which the fuel dispenser18can communication wirelessly with wirelessly-enabled external devices or systems. The wireless communication circuit230may be configured to communicate wirelessly using any known electromagnetic technology, examples of which include, but are not limited to, radio frequency (RF), infrared (IR), microwave (MW), magnetic, optical and the like. In embodiments using radio frequency communication technology, wireless communications may be conducted using any known RF communication protocol, examples of which include, but are not limited to, Bluetooth® short-wave radio communications, wifi wireless local area network (WLAN), wireless Universal Serial Bus (USB), and the like. In the specific example illustrated inFIG. 2, the wireless communication circuit230includes a conventional Bluetooth® module232configured to conduct wireless communications in accordance with an established Bluetooth® communications protocol. Alternatively or additionally, the communication circuitry68may include a conventional near-field communication (NFC) device234which may be included in embodiments in which the mobile electronic device (80/90) also has such a near-field communication device such that information, e.g., in the form of instructions and/or customer identification information such as EMSIDs, user names, passwords, or the like, and/or customer payment information, e.g., credit/debit card information or the like, can be transferred from the mobile electronic device (80/90) to the fuel dispenser18by tapping the two near-field communication devices together or by passing the near-field communication device of a so-equipped mobile electronic device (80/90) sufficiently close to the near-field communication device234to effectuate such communication.

The various components of the fuel dispenser18illustrated inFIGS. 1 and 2are illustratively carried in a single housing240which may be formed using one or more panels of one or more suitable materials such as glass, plastic, metal or the like. The housing240may have any shape, and in one embodiment is generally rectangular in shape. In some embodiments, the housing240may carry a single fuel dispenser, and in other embodiments the housing240may carry multiple fuel dispensers, e.g., two fuel dispensers, each facing in opposite directions.

The memory64of the fuel dispenser18includes a number of software modules stored therein, each containing one or more sets of instructions that are executable by the processor60of the fuel dispenser18to accomplish a specific function. For example, the memory64illustratively includes a conventional dispenser activation module250having stored therein instructions which, when executed by the processor60of the fuel dispenser18, cause the processor60to be responsive to the above-described manual operations of processing payment and selecting a fuel grade and/or type to control the dispensing section from an inactive state in which the dispensing section204is inhibited from dispensing fuel to an active state in which the dispensing section204is enabled to be manually manipulated, as described above, to dispense fuel from one of the plurality of different sources of fuel212. In some embodiments, the inactive state is the normal or default state of the dispensing section204, and control of the dispensing section204from the inactive state to the active state typically requires the sequential, manual operations of processing payment by the one or more payment interfaces218followed by manual selection via the selectors220/222of a desired fuel type and/or grade. In other embodiments, control of the dispensing section204may be at least partially overridden, e.g., to process payment, by an attendant at a corresponding hub location, e.g.,521. In such embodiments, the payment and fuel selection functions remain manual operations, but the payment operation may be carried out remotely from the fuel dispenser18under the control of a local server, e.g.,161.

In one embodiment, the memory64further includes a remote activation module252having stored therein instructions which, when executed by the processor60of the fuel dispenser18, cause the processor60to control the wireless communication circuit230to establish a wireless communication link with a mobile electronic device, i.e., a mobile communication device80and/or a vehicle communication device90, and to then be responsive to instructions transmitted by the remote electronic device to the fuel dispenser18, via the wireless communication link, to control the dispensing section204from the inactive state to the active state. Further details relating to the operation of the fuel dispenser18in accordance with such instructions stored in the remote activation module252will be described below with respect toFIGS. 9A-9B and 11.

In some embodiments, the memory64of the fuel dispenser18further includes a conventional local positioning system (LPS) and/or location-based service (LBS) module254. In one embodiment, the module254is an LPS module and has stored therein instructions which, when executed by the processor60, cause the processor60to control the one or more beacons224to transmit signals, e.g., radio frequency signals such as Bluetooth® Low Energy signals, wifi, ultra wide band (UWB), etc., containing information that can be used by a compatible LPS module running on the mobile electronic device (80/90) to determine the position of the beacon224(and hence, the position of the fuel dispenser18and/or the mobile electronic device (80/90). In another embodiment, the module254is an LBS module and has stored therein instructions which, when executed by the processor60, cause the processor60to utilize global positioning system (GPS) information transmitted by a so-equipped mobile electronic device to determine its position relative to a known position of the fuel dispenser18.

The memory64of the fuel dispenser18may further include a conventional geofence module256. In one embodiment, the module256has stored therein a set of geographic coordinates which together define a virtual boundary at least partially about the fuel dispenser18. The module256further has instructions stored therein which, when executed by the processor60, cause the processor60to utilize global positioning system (GPS) information transmitted by a so-equipped mobile electronic device to determine the position of the mobile electronic device relative to the virtual boundary defined at least partially about the fuel dispenser18. The processor60can thus determine when and whether a GPS-equipped mobile electronic device has entered and exited the area defined within the virtual boundary.

The memory64of the fuel dispenser18may further include an ID Code module258having stored therein instructions which, when executed by the processor60, cause the processor60to generate a random or pseudo-random number (IDCODE), and to control one of the display monitors214to display the generated number. Illustratively, the generated number may include any number of digits, and may include or incorporate one or more non-random numbers, such as an identification number of the fuel dispenser, an identification number of the hub location521, or the like. As one specific example, a random two-digit number, e.g.,23, may be generated by the processor60and combined with the identification number, e.g., 1, of the fuel dispenser18to produce the IDCODE231which the processor60then causes to be displayed on one of the display monitors. In embodiments that include the IDCODE module, the remote activation module252may, as described below, include instructions to establish a wireless communication link with a mobile electronic device that is within wireless communication range of the fuel dispenser18and that transmits the displayed IDCODE in response to user input to the mobile electronic device. Illustratively, the instructions stored in the IDCODE module256may cause the processor60to periodically regenerate and display the IDCODE with any specified frequency, and/or to require detection of the transmission by a mobile electronic device of any number of sequentially generated IDCODES before establishing a wireless communication link with the mobile electronic device.

Referring now toFIG. 3, a simplified block diagram of an embodiment of the mobile communication device (MCD)80is shown. In the illustrated embodiment, the mobile communication device80generally includes the same components as the main server12. For example, a processor300is coupled to an I/O subsystem302, and the I/O subsystem302is coupled to a memory304, a data storage unit306, communication circuitry310and one or more peripheral devices318. In some embodiments, some or all of the foregoing components may be identical to corresponding components of the main server12and/or of the fuel dispenser18described above, and a detailed explanation of such components will not be repeated here for brevity. In other embodiments, the mobile communication device80may be configured differently than the main server12and/or the fuel dispenser18described above. In the illustrated embodiment, for example, the data storage306includes a user data area308within which data specific to the user may be stored. Examples of such user data may include, but should not be limited to, payment information identifying one or more systems of payment, e.g., credit/debit card information, prepaid debit card information, fuel-specific charge card, etc., specific to the user via which payment can be processed for the purchase of fuel, motor vehicle information identifying one or more motor vehicles for which the user may purchase fuel, fuel type and/or grade preferences of the user, photographic data, e.g., of odometer readings, etc., and the like.

The communication circuitry310is illustratively identical to the communication circuitry68of the fuel dispenser18, particularly in embodiments in which a wireless communication link will be established between the fuel dispenser18and the mobile communication device80and/or between the mobile communication device80and another electronic system, e.g., one of the plurality of local servers161-16Kand/or the main server12. In the illustrated embodiment, the communication circuitry310illustratively includes a wireless communication circuit310, and in some embodiments the wireless communication circuit310further illustratively includes a Bluetooth® module314configured to conduct radio frequency communication in accordance with one or more known Bluetooth® communications protocols (including, for example, Bluetooth® Low Energy). If and when wirelessly communicating with the main server12, a local server16or a fuel dispenser18, the mobile communication device16may use any suitable communication protocol. As with the communication circuitry68of the fuel dispenser18, some embodiments of the communication circuitry310of the mobile electronic device80may alternatively or additionally include a near-field communication (NFC) device316such that information, e.g., in the form of instructions, can be transferred from NFC device316of the mobile electronic device (80/90) to the NFC device254of the fuel dispenser18(and/or vice versa) by tapping the two near-field communication devices together or by passing/holding the mobile communication device80sufficiently close to the fuel dispenser18so as to effectuate such communication.

The peripheral devices318of the mobile electronic device80illustratively include at least one display screen320, at least one keypad32, a GPS receiver324, and a camera326. In some embodiments, the display screen320may be a conventional display-only screen, in which case a keypad32is provided separately from the screen320. In other embodiments, the display screen320may be a conventional touch-screen display, and in such embodiments they keypad32may be omitted if included as part of the touch-screen display. The GPS receiver324is illustratively a conventional global positioning system (GPS) receiver configured to continually determine the geographical coordinates of the mobile communication device80(and optionally the time of day) via radio signals continually broadcast by a plurality of earth-orbiting GPS satellites, and to provide such geographical coordinates (and optionally the time of day) to the processor300. The camera326is likewise conventional, and conventional instructions are stored in the memory304via which the processor300can control operations of the camera326and to capture, time, date and coordinate stamp, and store in the data storage308photos taken by the camera326.

The various components of the mobile communication device80illustrated inFIG. 3are illustratively carried in a single housing330or case which may be formed using one or more panels of one or more suitable materials such as glass, plastic, metal or the like. The housing330or case may have any shape, and in one embodiment is generally rectangular in shape.

Referring now toFIG. 4, a simplified block diagram of an embodiment of the vehicle communication device (VCD)90ofFIG. 1is shown. In the illustrated embodiment, the vehicle communication device90generally includes the same components as the main server12. For example, a processor400is coupled to an I/O subsystem402, and the I/O subsystem402is coupled to a memory404, a data storage unit406, communication circuitry410and one or more peripheral devices420. In some embodiments, some or all of the foregoing components may be identical to corresponding components of the main server12and/or of the fuel dispenser18and/or of the mobile communication device80described above, and a detailed explanation of such components will not be repeated here for brevity. In other embodiments, the vehicle communication device90may be configured differently than the main server12and/or the fuel dispenser18and/or the mobile communication device80described above.

In the illustrated embodiment, the data storage406includes a user data area408within which data specific to the user may be stored as described above with respect to the user data area308of the data storage306of the mobile electronic device80. The communication circuitry410is illustratively identical to the communication circuitry310of the mobile communication device80, particularly in embodiments in which a wireless communication link will be established between the vehicle communication device90and a fuel dispenser18, a local server16and/or the main server12. In the illustrated embodiment, the communication circuitry410thus illustratively includes a wireless communication circuit410that further illustratively includes a Bluetooth® module414configured to conduct radio frequency communication in accordance with one or more known Bluetooth® communications protocols (including, for example, Bluetooth® Low Energy), and a near-field communication (NFC) device418such that information, e.g., in the form of instructions and/or data, can be transferred from NFC device418of the vehicle electronic device90to the NFC device254of the fuel dispenser18and/or vice versa, and/or such that information can be transferred by the NFC device418of the vehicle communication device90to the NFC device316of the mobile communication device80and/or vice versa. The communication circuitry410may further illustratively include a network communication device416that allows the vehicle communication device90to wirelessly access the Internet or other communication network.

The peripheral devices420of the vehicle electronic device90illustratively include at least one display screen422, at least one keypad424and a GPS receiver426, all as described above with respect to the peripheral devices318of the mobile electronic device80. The peripheral devices420further illustratively include a number of vehicles sensors and/or actuators, or a data interface accessing such sensors and/or actuators, via which the processor400can receive vehicle and/or engine operating information. As one particular example of such vehicle operating information, which should not be considered limiting in any way, the processor400illustratively has access to odometer mileage such that the processor400may, at any time, determine the current mileage traveled by the vehicle76.

The various components of the vehicle communication device90illustrated inFIG. 4are illustratively carried in a single housing430or case which may be formed using one or more panels of one or more suitable materials such as glass, plastic, metal or the like. The housing430or case may have any desired shape, and may be partially or fully embedded within a structure, e.g., an instrument panel, of the motor vehicle76.

Referring now toFIG. 5, a simplified block diagram of an embodiment of the memory304of the mobile communication device80ofFIG. 3is shown illustrating a number of software algorithm modules stored therein. In the illustrated embodiment, for example, the memory304includes a fuel dispenser activation module502having stored therein instructions executable by the processor300of the mobile electronic device80. In one embodiment, the fuel dispenser activation module502has instructions stored therein which, when executed by the processor300, cause the processor300to control the wireless communication circuit310to establish a wireless communication link with the wireless control circuit230one of the fuel dispensers181-18N,181-18M, (or with the wireless control circuit of one of the local servers161-16Kor the main server12), and to then transmit instructions to the fuel dispenser (or a corresponding one of the local servers or the main server), via the wireless communication link, to control the dispensing section204of the fuel dispenser from the inactive state to the active state. Further details relating to one embodiment of the operation of the mobile communication device80in accordance with instructions stored in the fuel dispenser activation module502will be described below with respect toFIGS. 9A-9B and 10. Other embodiments of the operation of the mobile communication device80in accordance with instructions stored in the fuel dispenser activation module52will be described with respect toFIGS. 14-22.

The memory304of the mobile communication device80further includes a global positioning system (GPS) module504having instructions stored therein which, when executed by the processor300of the mobile electronic device80, cause the processor300to continually receive geographical coordinates (and time of day information) from the GPS receiver324. In some embodiments, the processor300is further operable, in accordance with the instructions stored in the GPS module504to transmit one or more times or periodically, e.g., at the request of the LBS module254and/or geofence module256of the fuel dispenser18, the geographical coordinates of the GPS receiver324via the wireless communication circuit312.

The memory304of the mobile communication device80further includes an enterprise member services (EMS) module506having instructions stored therein which are executable by the processor300of the mobile electronic device80. In one embodiment, the instructions stored in the EMS module506illustratively cause the processor300to have access to the customer's enterprise member services account and to the customer's rewards repository, both maintained by the main server12. In other embodiments, the EMS module308may include instructions executable by the processor300to communicate customer-member information to and from the main server12or other system, to control one or more local peripheral devices to facilitate communications between customer-members of the enterprise membership service (EMS) program and the main server12or other system and to facilitate customer input of customer-identifying information, e.g., an EMS identifying number and/or code (EMSID).

The memory304of the mobile communication device80may further include a location position system (LPS) and/or location-based services (LBS) module508which may illustratively be identical or communicatively complementary to the LPS/LBS module256described above with respect to the fuel dispenser18. In embodiments that include the LPS/LBS module508, the module508illustratively has instructions stored therein which, when executed by the processor300of the mobile electronic device80, cause the processor300to control the wireless communication circuit312to transmit signals one or more times or periodically, e.g., in response to a request signal transmitted by an LPS/LBS device or system of a fuel dispenser18, local server16or main server12, or vice versa, in order to facilitate a determination of the position of the mobile electronic device80relative to one or more fuel dispensers181-18N,181-18M(or relative to one of the local servers161-16Kor the main server12) or vice versa.

The memory304of the mobile communication device80may further include an identification code (IDCODE) module510that is communicatively complementary to the IDCODE module258described above with respect to the fuel dispenser18. In embodiments that include the IDCODE module510, for example, the module510illustratively has instructions stored therein which, when executed by the processor300of the mobile electronic device80, cause the processor300to be responsive to user input of the random or pseudo-random IDCODE produced by the processor60of one of the fuel dispensers181-18N,181-18Mand displayed on one of the display monitors214to control the wireless communication circuit312to transmit signals one or more times or periodically, for the purpose of establishing a wireless communication link with the corresponding one of the fuel dispensers181-18N,181-18M(or local server16or main server12coupled thereto).

Referring now toFIG. 6, a simplified block diagram of an embodiment of the memory404of the vehicle communication device90ofFIG. 4is shown illustrating a number of software algorithm modules stored therein. In the illustrated embodiment, for example, the memory404includes a fuel dispenser activation module602having stored therein instructions which are executable by the processor400of the vehicle electronic device90. In one embodiment, the fuel dispenser activation module602has instructions stored therein which, when executed by the processor400, cause the processor400to control the wireless communication circuit412to establish a wireless communication link with the wireless control circuit230one of the fuel dispensers181-18N,181-18M, (or with the wireless control circuit of one of the local servers161-16Kor the main server12), and to then transmit instructions to the fuel dispenser (or a corresponding one of the local servers or the main server), via the wireless communication link, to control the dispensing section204of the fuel dispenser from the inactive state to the active state. Further details relating to such operation of the vehicle communication device90in accordance with one embodiment of the instructions stored in the fuel dispenser activation module602will be described below with respect toFIGS. 9A-9B and 10. Other embodiments of the operation of the vehicle communication device90in accordance with instructions stored in the fuel dispenser activation module52will be described with respect toFIGS. 14-22.

The memory404further includes a GPS module604, and an EMS module606identical in structure and operation to the GPS module504and EMS module506of the memory304of the mobile communication device80. The memory404may further include an LPS/LBS module608and an IDCODE module610that are each likewise identical in structure and operation to the LPS/LBS module508and IDCODE module510of the memory304of the mobile communication device80. The memory404may further include an odometer module612having instructions stored therein which, when executed by the processor400of the vehicle communication device90, cause the processor400to monitor and maintain a current value of the vehicle odometer, i.e., a current value of the mileage traveled by the motor vehicle76.

Referring now toFIG. 7, a simplified diagram of an embodiment of some of the features of an example one,16, of the local servers161-16Killustrated inFIG. 1is shown. In the illustrated embodiment, the peripheral devices50of the local server16illustratively include one or more payment interfaces702, one or more keypads704and one or more display monitors706, all of which may be similar or identical in structure and/or function to like components of the fuel dispenser18illustrated inFIG. 2. The peripheral devices50further illustratively include a conventional fuel dispenser control interface708having a number of manually operated switches via which operation of one or more of the number of on-site fuel dispensers181-18N,181-18Mmay be controlled and/or overridden. For example, the manual payment operation described above with respect toFIG. 2may, in some embodiments, be alternatively effectuated via the one or more payment interfaces702of the local server16, and in such cases the attendant may then manually control the fuel dispenser control interface708to override this operation on the corresponding fuel dispenser18such that, after effectuating payment via the one or more payment interfaces702, the customer need only remotely control the fuel dispenser18to select a desired type and/or grade of fuel.

The peripheral devices50of the local server16may, in some embodiments, further include one or more beacons710identical in structure and function to the one or more beacons224described with respect toFIG. 2, except that in embodiments in which the UID includes beacon type information such beacon type information illustratively identifies the one or more beacons710as one or more fuel center beacons710. Likewise, the local server16may include a unique identification number or code700, and the memory720may include a conventional dispenser activation module720, a remote activation module722and one or more additional modules724, such as an LPS/LBS module726, a geofence module728and/or an IDCODE module730, all identical in structure and operation to like-named components and modules illustrated and described above with respect toFIG. 2. The communication circuitry48may further include wireless communication circuitry740in addition to wired communication circuitry742used to normally communicate with the one or more fuel dispensers181-18N,181-18M.

In one embodiment, a wireless communication link is established between the mobile electronic device (i.e., the mobile communication device80and/or the vehicle communication device90) and one of the electromechanically controlled fuel dispensers181-18N,181-18M. The mobile electronic device may then be operated to remotely and wirelessly control the fuel dispenser, e.g.,181, via the wireless communication link, to an activated state in which the dispensing section204of the fuel dispenser, e.g.,181, is enabled to be mechanically manipulated to dispense fuel. In such embodiments, the mobile electronic device may directly control the fuel dispenser181, and in such cases the control section of the fuel dispenser181which controls activation of the dispensing section204includes the processor60, the remote activation module252and the one or more controllers210. Alternatively, the fuel dispenser181may operate as a pass-through device by passing all commands/requests from the mobile electronic device to the corresponding local server, e.g.,161, or the main server12, and acting only upon commands/requests transmitted back to the fuel dispenser181from the local server161or the main server12. In such cases, the processor40of the local server161(or the processor20of the main server12) primarily controls the dispensing section204of the fuel dispenser181, and the “control section” of the fuel dispenser181which controls activation of the dispensing section204thus includes not only the processor60and the one or more controllers210acting upon the dispensing section204of the fuel dispenser181but also the processor40and remote activation module722of the local server161(or the processor20and similar remote activation module stored within the memory24of the main server12). Alternatively still, control of the dispensing section204may be carried out in-part by the processor60, under the direction of instructions stored in the remote activation module252of the fuel dispenser181, and in-part by the processor40under the direction of instructions stored in the remote activation module722of the local server161(or the processor20and similar remote activation module stored within the memory24of the main server12). In such cases, the “control section” of the fuel dispenser181which controls activation of the dispensing section204thus includes not only the processor60, the remote activation module252and the one or more controllers210acting upon the dispensing section204of the fuel dispenser181but also the processor40and remote activation module722of the local server161(or the processor20and similar remote activation module stored within the memory24of the main server12).

In other embodiments, the wireless communication link may be established between the mobile electronic device (i.e., the mobile communication device80and/or the vehicle communication device90) and a local server, e.g.,161, serving a plurality of electromechanically controlled fuel dispensers, e.g.,181-18N. In such cases, the “control section” of the selected fuel dispenser, e.g.,181, which controls activation of the dispensing section204may include primarily the processor40, acting under the direction of the remote activation module722of the local server161(or the processor20and similar remote activation module stored within the memory24of the main server12), and also the processor60controlling the one or more controllers210in accordance with instructions received from the processor40of the local server161. Alternatively, the local server161in this embodiment may operate as a pass-through device by passing all commands/requests from the mobile electronic device to the selected fuel dispenser, e.g.,181, and by passing all fuel dispenser operating information provided by the fuel dispenser181back to the mobile electronic device via the wireless link. In such cases, the processor60of the fuel dispenser181primarily controls the dispensing section204of the fuel dispenser181under the direction of the remote activation module252, and the “control section” of the fuel dispenser181which controls activation of the dispensing section204thus includes not only the processor40of the local server161but also the processor60, the remote activation module252of the fuel dispenser181and the one or more controllers210. Alternatively still, control of the dispensing section204in this embodiment may be carried out in-part by the processor60, under the direction of instructions stored in the remote activation module252of the fuel dispenser181, and in-part by the processor40under the direction of instructions stored in the remote activation module722of the local server161(or the processor20and similar remote activation module stored within the memory24of the main server12). In such cases, the “control section” of the fuel dispenser181which controls activation of the dispensing section204thus includes not only the processor60, the remote activation module252and the one or more controllers210acting upon the dispensing section204of the fuel dispenser181but also the processor40and remote activation module722of the local server161(or the processor20and similar remote activation module stored within the memory24of the main server12).

In still other embodiments, the wireless communication link may be established between the mobile electronic device (i.e., the mobile communication device80and/or the vehicle communication device90) and the main server12. In such cases, the “control section” of the selected fuel dispenser, e.g.,181, which controls activation of the dispensing section204may include primarily the processor20, acting under the direction of a remote controlled fueling module842of the main server12, and also the processor60controlling the one or more controllers210in accordance with instructions received from the processor20of the main server12. Alternatively, the main server12in this embodiment may operate as a pass-through device by passing all commands/requests from the mobile electronic device to the selected fuel dispenser, e.g.,181, and by passing all fuel dispenser operating information provided by the fuel dispenser181back to the mobile electronic device via the wireless link. In such cases, the processor60of the fuel dispenser181primarily controls the dispensing section204of the fuel dispenser181under the direction of the remote activation module252, and the “control section” of the fuel dispenser181which controls activation of the dispensing section204thus includes not only the processor20of the main server12but also the processor60, the remote activation module252of the fuel dispenser181and the one or more controllers210. Alternatively still, control of the dispensing section204in this embodiment may be carried out in-part by the processor60, under the direction of instructions stored in the remote activation module252of the fuel dispenser181, and in-part by the processor20under the direction of instructions stored in the remote controlled fueling module842of the main server12. In such cases, the “control section” of the fuel dispenser181which controls activation of the dispensing section204thus includes not only the processor60, the remote activation module252and the one or more controllers210acting upon the dispensing section204of the fuel dispenser181but also the processor10and remote controlled fueling module842of the main server12.

Thus, depending upon the nature of the devices between which the wireless communication link is established, the “control section” which controls activation of the dispensing section204of the selected fuel dispenser18may be solely contained within the fuel dispenser18or contained, in-part, within the fuel dispenser18and in-part within a local server161or main server12to which the fuel dispenser18is communicatively coupled.

Referring now toFIG. 8, a simplified block diagram of an embodiment of a software environment800of the main server illustrated inFIG. 1is shown. In the illustrated embodiment, the environment800includes a server database802which includes customer account data804, a fuel receipt database806, a customer purchase history database808, a rewards/offers database810, product/service and pricing data412and a rewards repository814. The main server12further includes a payment interface module820, a transaction module822, an enterprise member services (EMS) module824and a communication module826, as well as a fuel dispenser management module830.

The main server12manages payment transactions, oversees the operations of the local servers161-16Kand provides, stores and manages rewards/offers, i.e., virtual discount coupons, for customer members of the enterprise member services (EMS) program offered and managed by the enterprise via the EMS module824. Customers may elect to participate in the EMS program offered, managed and maintained by the retail enterprise by establishing a user account (which may be referred to herein as an “EMS account” or “customer account”) within the server12, which user account may in some cases be an individual account accessible only by an individual person, e.g., an individual customer, and in other cases may be a group or “household” account accessible by each of a plurality of members of a predefined group of persons, e.g., members of a family or household, one or more employees of a business enterprise, etc. The terms “shopper,” “customer,” “member,” “customer member” and “household,” and variants thereof, are used interchangeably in this disclosure, and such terms should be understood to refer interchangeably to an individual customer or a predefined group of individual customers (referred to herein as a “household”) who purchase products and/or services from the enterprise, including fuel from any of its hub locations161-16K, and who are members of an enterprise member services (EMS) program of the type described herein and provided and managed by the retail enterprise.

Illustratively, a software application program is available for download from the main server12via a public network1202(see, e.g.,FIG. 12) for customers electing to access the EMS program via one or more of their mobile electronic devices, e.g., one or more mobile communication devices80and/or one or more vehicle communication devices90. Once downloaded and activated, customers can access and manage their EMS program account and program features via the software application module executed by their mobile electronic device, e.g., the EMS module508in the case of the mobile communication device80and the EMS module606in the case of the vehicle communication device90. Illustratively, the main server12additionally hosts and controls an EMS website accessible via the public network1202, and in such embodiments customers can access and manage their EMS accounts and program features by accessing their EMS page(s) of the EMS website hosted by the main server12via a web-enabled computing device, e.g., either the mobile communication device80, the vehicle communication device90or another web-enabled computing device such as a personal, laptop, notebook or tablet computer. In embodiments in which customers access and manage their EMS accounts and program features via the EMS website, any such mobile communication device80, vehicle communication device90and/or other web-enabled computing device will illustratively be equipped with one or more conventional web browsers.

In the illustrated embodiment, the customer account data804of the server database802has stored therein information relating to user accounts and profile data for each of the customer members of the EMS program. As customers join the EMS program, the server12establishes an EMS account within the customer account data804that is unique to the customer, and assigns to customer, or the customer selects, a corresponding EMS member identification (EMSID) as briefly described above. The EMSID associated with each customer is entered into the main server12and stored along with the customer's profile data in the customer account data804of the main server12. Illustratively, the EMSID may thereafter be used to access the customer's EMS account.

In some embodiments, the EMSID may illustratively include or identify a purchase tracking identifier code. Such a purchase tracking identifier code may be or include, for example, one or more of a customer ID card, an ID associated with an RFID tag, which RFID tag may be part of the NFC communication circuitry of the mobile electronic device, a shopper's incentive card, or the like. At least one of the above-described purchase tracking identifier code items may be provided to the main server12automatically by the fuel dispenser activation module502,602of the mobile electronic device upon establishment of the wireless communication link between the mobile electronic device and a selected one of the fuel dispensers181-18N,181-18M(or a corresponding one of the local servers161-16Kor the main server12). It is through such a purchase tracking identifier code that the main server12monitors and may track, via the EMS module824, purchases made by customer members from the retail enterprise during purchase transactions, including fuel purchases made by customer members. All such purchase transaction data relating to items purchased by customer members during purchase transactions carried out via one or more payment interfaces is stored in the customer purchase history database808. Illustratively, the purchase transaction data includes, but is not limited to, product/service identification information, product/service pricing, and the like.

In other embodiments, the EMSID may not be provided in or as part of any tangible form, and may instead be or include one or more easily remembered sequences of numbers, letters, symbols or other characters. In any case, EMSIDs communicated to any of the fuel dispensers18or to a local server16or the main server12allows the main server12to identify the corresponding customers. For example, when a customer manually enters the customer's EMSID into one of the fuel dispensers18as part of a purchase transaction (e.g., during the purchase transaction or as part of the process of commencing the purchase transaction), the processor60of the fuel dispenser18communicates the EMSID to the main server12which identifies the shopper via the EMSID and associates that shopper with the current purchase transaction being carried out at the corresponding fuel dispenser18. As will be described in greater detail below, the member shopper's EMSID may, in some embodiments, be automatically provided, via the member shopper's mobile communication device80or vehicle communication device90, to the main server12during a purchase transaction, e.g., in a manner that is transparent or semi-transparent to the customer and that does requires the customer to perform few or no manual acts. In any case, all such purchase transaction data relating to fuel purchased by such an identified customer during a purchase transaction carried out via one of the fuel dispensers18of the retail enterprise is illustratively stored in the customer purchase history database808where it is associated with the identified customer via the customer's EMSID. The main server12may, in some embodiments, make virtual discount offers available to the customer and/or associate purchases made by the customer with the customer's purchase history to thereby monitor and track purchases, including fuel purchases, made by the customer from the retail enterprise during purchase transactions. MPERKS®, a virtual customer coupon collection and redemption program offered to customers by Meijer, Inc. of Grand Rapids, Mich., is an example of one such EMS program of the type described herein, although it will be appreciated that any retail enterprise membership service which offers virtual discount coupons and/or other benefits to shopper members, and/or which tracks items purchased by shopper members during item purchase transactions at point-of-sale systems or terminals may be alternatively be used.

As part of the EMS program described herein, the main server12may provide discount rewards or offers to customer members for one or more items purchasable from the business enterprise, e.g., in the form of one or more corresponding virtual discount coupons. In this regard, each customer member is provided by the main server12with access to dedicated rewards repository814in which such discount rewards specific to the customer member are stored and via which the customer member may access and redeem one or more such virtual discount coupons. In one embodiment, the server database802includes a plurality of rewards repositories814; one for each of the plurality of customer members of the EMS program. Alternatively, the server database802may include a single rewards repository814, and each customer member of the EMS program may be provided with access to a dedicated portion of such a single rewards repository814; i.e., a portion of the repository which can be accessed by one customer member to the exclusion of all other customer members. When a customer member's mobile electronic device80or vehicle communication device90provides the customer member's EMSID to the main server12via a wireless communication link, for example, the processor20of the main server12may identify the customer and associate that customer with the current purchase transaction being carried out at the fuel dispenser181-18N,181-18M. The main server12can, during and as long as a wireless communication link is established and maintained between the customer's mobile electronic device and one of the fuel dispensers181-18N,181-18M(or local server161-16Kor main server12), push discount rewards or offers to the customer's mobile electronic device, which the customer can choose, e.g., via simple customer input to the mobile electronic device, to save within the customer's rewards repository808, for subsequent redemption against a corresponding product or service.

The product/service and pricing data812of the server database802contains information relating to the retail products and services sold by the retail enterprise which the main server12serves, which information includes product and pricing information for each of the plurality of different fuels dispensable by a fuel dispenser18from one of the fuel sources212. The information stored in the product/service and pricing database812may further include any one or more of current product inventory information, product/service location within the corresponding retail outlet, past, current and future service usage and cost, past, current and future product cost and ordering information, product and service identification information, past, current and future product and service discount information, and the like for any product and/or service offered by the retail enterprise served by the main server12.

The fuel receipt database806has stored therein virtual, e.g., digital representations, of fuel receipts for fuel purchases made by customer members of the EMS program. The fuel receipt database806may or may not be partitioned, although each fuel receipt is illustratively linked to a corresponding customer member, e.g., via the customer member's EMSID.

The rewards/offers database810illustratively has stored therein an earn/reward offer bank in the form of one or more tables of earn requirements and corresponding discount rewards. The earn/reward offer bank is initially constructed based on the purchase transaction data for all customer members of the EMS program at an arbitrary point in time, and is thereafter periodically updated based on purchase transaction data collected and stored in the purchase history database808since previously updating the earn/reward bank.

The payment interface module820of the main server12is configured, in a conventional manner, to process tangible forms of electronic payment systems (EPS), e.g., tangible electronic funds transfer instruments such as credit cards, debit cards, etc., used at the fuel dispensers181-18N,181-18Mand/or local hubs521-52Kwhen purchasing fuel. In accordance with this disclosure, the payment interface module820is likewise configured to process payment information stored within a mobile electronic device and transmitted via a wireless communication link to the main server12, which identifies one or more customer-specific systems of payment for processing by the payment interface module820for the purchase of fuel to be dispensed from one of the fuel dispensers181-18N,181-18M.

The transaction module822is configured to monitor purchases of fuel and other products and/or services made by customer members of the EMS program using any of the purchase interfaces, e.g., any of the fuel dispensers181-18N,181-18M, and/or any of the local servers161-16K, and to store purchase transaction data associated with such purchases in the purchase history database808. Illustratively, the purchase history database808is partitioned or otherwise configured to store such purchase transaction data in a manner that provides for the separate tracking and identification of at least a portion of the purchase histories of each customer member and further provides for the tracking and identification of at least a portion of the purchase histories of all customer members. For example, which should not be considered to be limiting in any way, the transaction module822is illustratively configured in one embodiment to store the purchase transaction data in the purchase history database808in a manner that separately identifies and tracks identification and pricing information for each fuel purchase and product/service purchase made by each customer member, and that identifies and tracks identification and pricing information for each such product and service purchased by all customer members.

The communication module826is configured, in a conventional manner, to control and manage all communications between the main server12and the local servers161-16Kin embodiments that include the local servers161-16K, to control and manage all communications between the main server12and all fuel dispensers181-18N,181-18Min embodiments that do not include one or more local servers161-16Kand to control and manage all communication between the main server12and all mobile electronic devices, e.g., all mobile communication devices80and all vehicle communication devices90.

The fuel dispenser management module830of the main server12illustratively includes an application download module832, an application set-up module834, a rewards/offers module836, a help module838and a digital receipt module840. The application download module832illustratively includes one or more downloadable versions of the fuel dispenser activation modules502/602, and conventional instructions that are executable by the processor20of the main server to manage downloading of such modules by and to mobile electronic devices. The application set-up module834has stored therein a set-up software program which may downloaded with or separately from the fuel dispenser activation module application software502/602. The application setup software program includes instructions which, when executed by the processor300/400of the mobile electronic device, cause the processor300/400to interactively assist customers in setting up the fuel dispenser activation module application software502/602on their mobile electronic devices, such as by entering and storing payment information, vehicle information and user preferences. One simplified example of such an application setup software program will be described in detail below with reference toFIG. 13.

The rewards/offers module836is illustratively an application program containing instructions which, when executed by the processor20of the main server12, cause the processor20to access at least the purchase history database808, the rewards/offers database810and rewards repository814for the purpose of generating customer-specific rewards, i.e., virtual discount coupons, and pushing such customer-specific rewards to wirelessly connected mobile electronic devices as briefly described above.

The help module838has stored therein a help software program which may downloaded with or separately from the fuel dispenser activation module application software502/602. The help software program includes instructions which, when executed by the processor300/400of the mobile electronic device, cause the processor300/400to interactively assist customers with trouble shooting the fuel dispenser activation module application software502/602on their mobile electronic devices, and to provide information about the software502/602.

The digital receipt module840has stored therein instructions which, when executed by the processor20of the main server12, cause the processor20to manage digital receipts resulting from the purchase of fuel by generating such receipts following completion of customer purchases of fuel, and then storing the generated digital receipts in the fuel receipt database806in a manner that links each such digital fuel receipt to a customer member of the EMS program. Following such storage of the digital fuel receipts in the fuel receipt database806, the digital receipts are generally accessible to and by the customer members as part of the EMS program.

The fuel dispenser management module830further includes a remote controlled fueling module842having stored therein instructions which, when executed by the processor20of the main server12, cause the processor20to control, in one embodiment, payment processing via the payment interface module820. Alternatively or additionally, the instructions stored in the remote controlled fueling module842may include instructions which, when executed by the processor20, cause the processor20to select fuel grade and/or type specified by a customer. Alternatively or additionally still, the instructions stored in the remote controlled fueling module842may include instructions which, when executed by the processor20, cause the processor20to generate and push customer-specific rewards/offers to wirelessly connected customers via the rewards/offers module836. Further details relating to the operation of the main server12in accordance with one embodiment of the instructions stored in the remote controlled fueling module842will be described below with respect toFIGS. 9A-9B and 11, and further details relating to the operation of the server12in accordance with another embodiment of the instructions stored in the remote controlled fueling module842will be described below with respect toFIGS. 14A-22generally and, more specifically, with respect toFIGS. 17-18 and 21-22.

Referring now toFIGS. 9A and 9B, a simplified flow diagram is shown of an embodiment of a process900for wirelessly activating one of the electromechanical fuel dispensers illustrated inFIG. 1via a mobile electronic device, for carrying out the subsequent fuel dispensation process through completion and for providing wirelessly connected purchasers of fuel with purchaser-specific discount rewards/offers for one or more goods and/or services offered for sale by an enterprise via which the fuel is purchased.

As indicated by the framework of the process900illustrated inFIGS. 9A-9B, a portion of the process900, i.e., the portion to the left of the left-most vertical line and centered under the heading “MDC/VCD,” represents the fuel dispenser activation module software application502/602that is executable by a processor (e.g., processor300or400) of a mobile electronic device (e.g., the mobile communication device80and/or vehicle communication device90respectively). In one embodiment, this portion of the process900is illustratively stored in the memory304(and/or data storage306) of the mobile communication device80in the form of instructions executable by the processor300of the mobile communication device80, and the process steps of this portion of the process900will be described below for purposes of this disclosure as being executed by the processor300of the mobile communication device80. It will be understood, however, that in some alternate embodiments, this portion of the process900may be stored in the memory404(and/or data storage406) of the vehicle communication device90in the form of instructions executable by the processor400of the vehicle communication device90. In still other alternate embodiments, this portion of the process900may be stored, in whole or in part, in the memory304(and/or data storage306) of the mobile communication device80in the form of instructions executable, in part, by the processor300of the mobile communication device80and in part by the processor400of the vehicle communication device90, or stored, in whole or in part, in the memory404(and/or data storage406) of the vehicle communication device90in the form of instructions executable, in part, by the processor400of the vehicle communication device90and in part by the processor300of the mobile communication device80.

Another portion of the process900, i.e., the portion between the two vertical lines and centered under the heading “Fuel Dispenser/Local Server,” represents the remote activation module software application252that is executable by the processor60of each of the plurality of fuel dispensers181-18N,181-18Mand/or the remote activation module software application722that is executable by the processor40of each of the local servers161-16K. In one embodiment, this portion of the process900is illustratively stored in the memory64(and/or data storage66) of the fuel dispensers181-18N,181-18Min the form of instructions executable by the processor60of the fuel dispensers181-18N,181-18M, and the process steps of this portion of the process900will be described below for purposes of this disclosure as being executed by the processor60of the fuel dispensers181-18N,181-18M. It will be understood, however, that in some alternate embodiments, this portion of the process900may be stored in the memory44(and/or data storage46) of the local servers161-16K, in the form of instructions executable by the processor40of the local servers161-16K(or stored in the memory24and/or data storage26of the main server12in the form of instructions executed by the processor20of the main server12, in embodiments that do not include the local servers161-16K). In still other alternate embodiments, this portion of the process900may be stored, in whole or in part, in the memory64(and/or data storage66) of the fuel dispensers181-18N,181-18Min the form of instructions executable, in part, by the processor60of the fuel dispensers181-18N,181-18Mand in part by the processor40of a corresponding one of the local servers161-16K, or stored, in whole or in part, in the memory44(and/or data storage46) of the local servers161-16Kin the form of instructions executable, in part, by the processor40of the local servers161-16Kand in part by the processor60of a corresponding one of the fuel dispensers181-18N,181-18M.

Yet another portion of the process900, i.e., the portion to the right of the right-most vertical line and centered under the heading “Main Server,” represents the remote controlled fueling module software application842that is executable by the processor20of the main server12. In one embodiment, this portion of the process900is illustratively stored in the memory24(and/or data storage26) of the main server12in the form of instructions executable by the processor20of the main server12, and the process steps of this portion of the process900will be described below for purposes of this disclosure as being executed by the processor20of the main server. It will be understood, however, that in some alternate embodiments that do not include a main server12, this portion of the process900may be stored in the memory44(and/or data storage46) of one or more of the local servers161-16Kin the form of instructions executable by the processor40of the one or more local servers161-16K.

It will further be understood that portions of the process900illustrated as being executed by one processor/device or one processor/server may alternatively be executed by a different processor/device or processor/server, some examples of which are described above.

Referring now specifically toFIG. 9A, the process900begins at steps902and904where a wireless communication link is established between the mobile electronic device (the mobile communication device80and/or the vehicle communication device90) and one of the plurality of electromechanically controlled fuel dispensers181-18N,181-18M(or a corresponding one of the local servers161-16Kin embodiments which include one or more of the local servers161-16K, or the main server12in embodiments that do not include local servers161-16K). Step902is illustratively carried out by the processor300and step904is illustratively carried out by the processor60to establish a wireless communication link via the wireless communication circuits312and230respectively.

The wireless communication circuits312and230are typically short-range communication circuits having a limited range of communication, i.e., a limited range or maximum distance between the two over which the wireless communication link can be established and maintained. Reference will be made herein to the mobile electronic device being within a wireless communication range of a fuel dispenser or local server and vice versa, and as used herein the phrase “wireless communication range” should be understood to mean that the wireless communication circuits of the devices and/or servers in question are within, i.e., less than or equal to, the maximum distance between the two over which a wireless communication link can be established and maintained. Example wireless communication ranges may vary between 20 cm or so for some near-field communication (NFC) devices to several hundred meters for some outdoor wifi and/or short range wireless devices. The theoretical maximum wireless communication range for standard Bluetooth® transmitters/receivers is about 100 meters or so, and around 50 or so meters for Bluetooth® Low Energy transmitters/receivers. It will be understood that the foregoing wireless communication ranges are provided only by way of example, and should not be considered to be limiting in any way.

The present disclosure contemplates using any of a number of different conventional techniques and/or technologies for establishing a wireless communication link between a mobile electronic device and a corresponding fuel dispenser181-18N,181-18M(or local server161-16K) located within the wireless communication ranges of each other. In accordance with steps902and904, the processor300and the processor60each play a part in establishing such a wireless communication link, although one or the other of the processor300and the processor60may initiate or play a more primary role in establishing the communication link than the other depending upon the technique and/or technology used to establish the wireless communication link. In one embodiment, for example, the fuel dispensers181-18N,181-18M(or local servers161-16K) each include one or more beacons224/710, and the memory84of each fuel dispenser181-18N,181-18M(or local server161-16K) has stored instructions stored therein which, when executed by the processor60, cause the processor60to control the one or more beacons224/710to transmit periodic and repeating wireless signals. When a mobile electronic device is within the wireless communication range of such a fuel dispenser18or local server16, the wireless signals transmitted by the one or more beacons224/710are detected by the wireless communication circuit312of the mobile electronic device, and the processor300responds to such detection by initiating transmission and reception of wireless signals with the processor60of the fuel dispenser18or local server16via the one or more beacons224/710to establish the wireless communication link between the mobile electronic device and the fuel dispenser18or local server16.

In another embodiment, the fuel dispensers181-18N,181-18M(or local servers161-16K) each include the geofence module256/728stored in its memory64/44, and the mobile electronic device includes a GPS receiver324/426. In one implementation, the processor60of the fuel dispenser18or local server16periodically and repeatedly controls the wireless communication circuit230to transmit one or more geographical coordinates stored in the memory64that define the fuel dispenser's (or local server's) geofence. When a mobile electronic device is within the communication range of such a fuel dispenser18or local server16, the processor300is operable to receive via the wireless communication circuit68the transmitted geographical coordinate(s) and compare with the current GPS coordinates provided by the on-board GPS receiver324. The processor60of the fuel dispenser that is closest in proximity to the mobile electronic device then communicates with the processor300of the mobile electronic device, via the wireless communication circuits230and312, to establish the wireless communication link between the mobile electronic device and the fuel dispenser18. In another implementation, the processor300of the mobile electronic device controls the wireless communication circuit312to periodically and repeatedly transmit the current GPS coordinates received by the GPS receiver324, and the processor60of the fuel dispenser18or local server16operates with the processor300of the mobile electronic device to establish a wireless communication link between the two when the processor60detects that the mobile electronic device has entered the virtual boundary defined by the geofence coordinates stored in the memory64and is within the wireless communication range of the fuel dispenser or local server16.

In another embodiment, the fuel dispensers181-18N,181-18M(or local servers161-16K) each include the LPS/LBS module254/726stored in its memory64/44, and the mobile electronic device likewise includes the LPS/LBS module508/608stored in its memory304/404. When a mobile electronic device is within the wireless communication range of such a fuel dispenser18or local server16, wireless signals, e.g., wifi, short-range RF, etc., transmitted by the wireless communication circuit230are detected by the wireless communication circuit312of the mobile electronic device, and the processor300responds to such detection by initiating transmission and reception of wireless signals with the processor60of the fuel dispenser18or local server16via the wireless communication circuit312to establish the wireless communication link between the mobile electronic device and the fuel dispenser18or local server16.

In another embodiment, the fuel dispensers181-18N,181-18M(or local servers161-16K) each include the IDCODE module258/730stored in its memory64/44, and the mobile electronic device likewise includes the IDCODE module510/610stored in its memory304/404. The processor60of the fuel dispenser18or local server controls one of the display monitors214to generate, display, and periodically update/change, a random or pseudo-random number. A customer then enters the random or pseudo-random number into the mobile electronic device when sufficiently near the display monitor214to read the number. The processor300then controls the wireless communication circuit312to transmit the entered number, and upon detection of the transmitted number by the wireless communication circuit230, the processor60initiates transmission and reception of wireless signals with the processor300of the mobile electronic device via the wireless communication circuit312to establish the wireless communication link between the mobile electronic device and the fuel dispenser18or local server16. In a variant of this embodiment, the customer may alternatively scan or capture an image of the ID200/700, e.g., in the form of a barcode or matrix code (such as a QR code), and the processor300may then control the wireless communication circuit312to transmit the captured ID200/700. Upon detection of the transmitted ID200/700by the wireless communication circuit230, the processor60then initiates transmission and reception of wireless signals with the processor300as before to establish the wireless communication link between the mobile electronic device and the fuel dispenser18or local server16. In another variant of this embodiment, the processor300of the mobile electronic device may be response to input of the customer's EMSID or other EMS program identifier to control the wireless communication circuit312to transmit the entered EMSID or other EMS program identifier. Upon detection of the transmitted EMSID or other EMS program identifier by the wireless communication circuit230, the processor60may then initiate transmission and reception of wireless signals with the processor300as before to establish the wireless communication link between the mobile electronic device and the fuel dispenser18or local server16.

In another embodiment, the fuel dispensers181-18N,181-18Mand the mobile electronic device each include an NFC device234/316/418, and the processor300of the mobile electronic device and/or the processor60of a fuel dispenser18operate to establish a wireless communication link between the two when the mobile electronic device is brought within the wireless communication range of the NFC devices.

Those skilled in the art will recognize that the foregoing mechanisms and techniques for establishing a wireless communication link between the mobile electronic device (e.g., the mobile communication device80and/or the vehicle communication device90) and one of the fuel dispensers181-18N,181-18M(or local servers161-16K) may be used alone or in any combination. Moreover, it will be understood that such foregoing mechanisms and techniques are merely illustrative, and that other conventional mechanisms and/or techniques for establishing such a wireless communication links are intended to fall within the scope of this disclosure.

As part of, or following, the process of establishing the wireless communication link, the processor300illustratively provides information relating to the identity of the customer to the wirelessly linked fuel dispenser18(e.g., EMSID and/or other customer-identifying information). In any case, after the wireless communication link is established between the mobile electronic device and the one of the fuel dispensers181-18N,181-18M(or local servers161-16K) within its wireless communication range, the process advances from step904to step906where the processor60illustratively controls one of the display monitors214to display one or more customer-specific message(s), and further controls the communication circuitry68to transfer the customer identity information, e.g., EMSID, to the main server12. Following step906, the processor60is illustratively (and optionally) operable at step908to deactivate the fuel grade/type selectors220,222on the wirelessly linked fuel dispenser18.

At step910, the processor20of the main server is operable to locate customer information in the server database802(e.g., customer account, purchase history, etc.) based on the customer identity information, e.g., EMSID, transmitted by the wirelessly linked fuel dispenser18.

Following establishment of the wireless communication link at step902, the processor300of the mobile electronic device is operable at step912to control the display screen320to display an interface of the fuel dispenser application module502which may include information about the wirelessly linked fuel dispenser18and which may include the display of application information and/or selectable control icons (e.g., help, exit). Thereafter at step914, the processor300is illustratively operable to control the display screen320to display another interface of the fuel dispenser application module502which may include a list of customer vehicles, e.g., a list of motor vehicles pre-designated or pre-entered by the customer that represent motor vehicles which the customer may at some point wish to refuel, and which may further include one or more prompts for customer selection from the list of the motor vehicle being refueled. At step916, the processor300determines whether the customer has selected one of the motor vehicle from the displayed list of motor vehicles. If not, the process900loops back to step914, and if so the process900advances to steps918and920.

At step918, the processor300illustratively controls the display screen320to display a selectable list of fuel types and/or grades that are dispensable from the wirelessly connected fuel dispenser18. In the illustrated embodiment, the fuel types and/or grades available for dispensing from any of the fuel dispensers181-18N,181-18Mare common across all fuel dispensers and, as such, the fuel types and/or grades displayed on the selectable list are preset by the fuel dispenser activation module502. In some alternative embodiments, the available fuel types and/or grades may vary among fuel dispensers181-18N,181-18Mand/or among local hubs161-16K, and in such embodiments the process900may include an additional step executed by the processor60of the wirelessly connected fuel dispenser18to transmit, via the wireless communication link, the selectable list of fuel types and/or grades that are available for dispensing from the wirelessly connected fuel dispenser18. In one embodiment, the processor300may be further illustratively operable at step918to control the display screen320by highlighting a particular fuel type or grade that was pre-designated (e.g., during set-up) by the customer. Alternatively or additionally, the processor300may be further illustratively operable at step918to control the display screen320to delete, either automatically or as designated by the customer during set up of the fuel dispenser activation software application, the display of fuel types and/or grades that are not appropriate for vehicle being refueled (e.g., delete all gasoline options for motor vehicles having diesel engines, and all diesel fuel alternatives for gasoline engines, etc.).

The “YES” branch of step916also advances to step920as the processor300of the mobile electronic device transmits the selected motor vehicle information to the wirelessly connected fuel dispenser18via the wireless communication line. At step920, the processor60of the wirelessly connected fuel dispenser18, in turn, transmits the selected vehicle information to the main server12(e.g., via a corresponding one of the local servers161-16K), and thereafter at step922the processor20of the main server12receives the selected motor vehicle information and determines whether, based on the customer's purchase history and/or other factors which may or may not include the history of fuel purchases for the selected motor vehicle, whether to provide customer with a fuel grade upgrade offer for vehicle being refueled. Optionally, the processor20may alternatively or additionally be operable at step922to determine and generate general and/or customer-specific rewards/offers to offer customer, based on customer purchase history, and in this regard step922may also be executed following step910as illustrated by dashed line connection between the two steps910and922. Following step922, the processor20is operable at step924to transfer the fuel grade upgrade offer, if generated, to the wirelessly connected fuel dispenser18, e.g., via a corresponding one of the local servers161-16K). If any general and/or customer-specific rewards/offers have been generated by the processor20, the processor20also transfers such rewards/offers at step924to the wirelessly connected fuel dispenser18, e.g., via a corresponding one of the local servers161-16K).

At step926A, the processor60of the wirelessly connected fuel dispenser is operable to transfer to the mobile electronic device, via the wireless communication link, the fuel upgrade offer, if any, transferred thereto by the main server12. Such a fuel grade upgrade offer enters the mobile electronic device at step918, e.g., along with current fuel type/grade pricing information. The customer may, in some embodiments, have the option of applying the fuel grade upgrade offer to the current purchase of fuel, or to store the fuel grade upgrade offer in the user data section of the data storage308for subsequent use or transfer to the customer's rewards repository814in the main server12. At step926B, the processor60of the wirelessly connected fuel dispenser18is further operable to store, e.g., within the data storage66or the memory64, any general and/or customer-specific rewards generated by the main server12and transferred to the wirelessly connected fuel dispenser18at step92. Any such general and/or customer-specific rewards may, for example, be transferred to the mobile electronic device during fueling. If no such fuel upgrade offer is generated at step922, the “NO” branch of step924skips step926A and proceeds directly to step918.

Following step918, the processor300of the mobile electronic device determines at step928whether the customer has selected a fuel grade and/or type from the displayed list. If not, the process900loops back to step918, and otherwise the process advances to step930. At step930, the processor300illustratively controls the display screen320to display another interface which includes fuel cost and/or amount areas along with a prompt to the customer to enter amount of fuel to be dispensed, e.g., in monetary cost (e.g., $10.00), in volume (e.g., 10 gallons), or “fill up.” Thereafter as step932, the processor300is operable to determine whether the customer has selected a fuel amount at step930. If not, the process900loops back to step930and otherwise the process900advances to step934during which the processor300transmits, via the wireless communication link, the selected fuel amount to the wirelessly connected fuel dispenser18. At step934, the processor60controls the delivery section204for the delivery of a selected amount of a selected fuel type and/or grade. Illustratively, the processor60may also be operable at step934to limit the amount of fuel delivery to a maximum volume or cost, which may be universally applied or determined on a customer-by-customer basis.

The “YES” branch of step932also advances to step936where the processor300is illustratively operable to control the display screen320to display available car wash options along with a prompt requesting customer selection of one of the displayed options, e.g., good, better, best, free with fill up, no thanks. Thereafter at step938, the processor300determines the car wash option that the customer has selected. If “none” or “no thanks,” the process advances to step948. Otherwise, the process900advances to step940during which the processor300transmits the selected car wash option to the wirelessly connected fuel dispenser18via the wireless communication link. At step940, the processor60of the wirelessly connected fuel dispenser18transfers the customer-selected car wash option to the main server12(e.g., via a corresponding one of the local servers161-16K). At step942, the processor20of the main server generates a coupon code for the customer-selected car wash, and then transfers the generated coupon code back to the wirelessly connected fuel dispenser18(e.g., via a corresponding one of the local servers161-16K). At step944, the wirelessly connected fuel dispenser18transmits the generated coupon code for the customer-selected car wash to the mobile electronic device via the wireless communication link. At step946, the processor300of the mobile electronic device stores the generated coupon code for the customer-selected car wash in the memory304or user data section308of the data storage306for subsequent redemption at a designated car wash facility.

At step948, the processor300of the mobile electronic device is illustratively operable to control the display screen to display another interface which includes payment information identifying one or more systems of payment specific to the user of the mobile electronic device via which payment can be processed for the purchase of fuel to be dispensed from the wirelessly connected fuel dispenser18. The one or more systems of payment may be, for example, one or more credit/debit cards, fuel charge cards, pre-paid charge cards, etc., and such one or more systems of payment are illustratively pre-designated by the customer during set-up of the fuel dispenser activation software application502. In any case, the interface displayed at step948illustratively includes a prompt requesting customer selection of one of the displayed systems of payment, and may further include a highlighted or otherwise designated default preference for one of the displayed systems of payment. Thereafter at step950, the processor300determines whether the customer has selected one of the displayed systems of payment. If not, the process900loops back to step948, and if so the process900advances to step952during which the processor300transmits the payment information for the selected system of payment to the fuel dispenser18via the wireless communication link.

At step952, the processor60of the wirelessly connected fuel dispenser18transfers the payment information for the customer-selected system of payment to the main server12(e.g., via a corresponding one of the local servers161-16K). Thereafter at step954, the processor20of the main server12processes the payment information for the customer-selected system of payment and either accepts or denies the system of payment for the purchase of fuel. Thereafter at step956, if the customer-selected system of payment is denied, the processor20transfers a “denied” message to the wirelessly connected fuel dispenser18(e.g., via a corresponding one of the local servers161-16K), and at step958the processor60of the wirelessly connected fuel dispenser18transmits the “denied” message to the mobile electronic device via the wireless communication medium. At step960, the processor300then controls the display screen320to display a message informing denial of the customer-selected system of payment for payment of fuel to be dispensed from the fuel dispenser18. Step960then loops back to step948where the customer may select payment information for another system of payment or exit the process900. If, at step954the customer-selected system of payment is accepted, the processor20transfers an “accepted” message to the wirelessly connected fuel dispenser18(e.g., via a corresponding one of the local servers161-16K), and at step962the processor60of the wirelessly connected fuel dispenser18activates the dispenser section204of the fuel dispenser18to enable the dispenser section204to be manually manipulated, as described above, to dispense the selected type and/or grade of fuel. The processor60is further operable at step962to transmit an “fuel dispenser enabled” message to the mobile electronic device via the wireless communication medium, and at step964the processor300controls the display screen320to display a message informing that the wirelessly connected fuel dispenser18fuel dispenser is now activated and ready to dispense the selected type/grade of fuel.

Those skilled in the art will appreciate that the process900may alternatively be modified such that execution of the fuel payment steps948-964just described occur prior to execution of the fuel type and/or grade selection steps918and928-934, such that a customer-specific system of payment is processed and must be accepted before the customer selects a type and/or grade to be dispensed. It will be further appreciated that any changes required to effect such modification of the process900would be a mechanical step for a skilled programmer, and therefore well within the skill level of a person of ordinary skill in the computer programming arts.

Referring now toFIG. 9B, the process900advances from step962to step970where the processor60of the wirelessly connected fuel dispenser18monitors one or more of the actuators and/or sensors206to determine whether the fuel nozzle74has been disengaged from the fuel dispenser18and whether the fuel control lever is depressed. If so, fuel delivery is underway with the fuel dispenser18dispensing fuel from a selected one of the plurality of different fuel sources212via the fuel nozzle74, and the process900advances to step972where the processor60of the fuel dispenser18is operable to transmit fuel delivery cost and quantity metrics to the mobile electronic device via the wireless communication link. If the processor60determines at step970that the fuel nozzle74has not been depressed, the process900illustratively loops back to the beginning of step970until fuel delivery is detected. In any case, the processor300of the mobile electronic device is operable follow step972to advance to step974where the processor60is operable to control the display monitor320to display, in real-time or near real-time, the fuel delivery cost and quantity metrics typically otherwise displayed on one of the display monitors214of the fuel dispenser18during manual activation and control of the fuel dispenser18.

The process900also advances from step972to step976where the processor300of the fuel dispenser is operable, during the fuel dispensing process, to transmit one, or sequentially transmit multiple ones, of the general and/or customer-specific rewards/offers, if any, stored in the memory64and/or data storage66at step926B. Although not shown inFIG. 9B, the process900may further include additional sets of the steps922and926B coupled to step976, such that the processor20of the main server12may, partially during or throughout the fuel dispensation process, generate general and/or customer-specific rewards/offers and transfer such rewards/offers to the fuel dispenser18. In one embodiment, the processor60of the fuel dispenser18may temporarily store any such general and/or customer-specific rewards received from the main server12in the memory64and/or data storage66prior to transmitting them to the mobile electronic device via the wireless communication link. Alternatively, the processor60of the fuel dispenser18may operate to transmit any such general and/or customer-specific rewards received from the main server12during the fuel dispensation process directly the mobile electronic device upon receipt. In any case, the processor300of the mobile electronic device is operable thereafter at step978to control the display screen320to display, e.g. sequentially, along with or in place of the fuel metrics, the general and/or customer-specific rewards/offers received from the fuel dispenser18via the wireless communication link.

Following step978, the process900advances to step980where the processor300of the mobile electronic device is operable to determine whether the customer has selected, e.g., via a conventional touch-screen or screen-swipe selection, a displayed one of the general and/or customer-specific rewards/offers. If so, the process900advances to step982where the processor300is operable to store the selected general and/or customer-specific rewards/offer in the memory304or user data section308of the data storage306. If not, the process900loops back to step978, as it also does following completion of step982.

The process900also advances from step976to step984where the processor60of the wirelessly connected fuel dispenser18monitors one or more of the actuators and/or sensors206to determine whether fuel delivery by the fuel dispenser18complete. If so, the process advances to steps986and996, and otherwise the process loops back to step972.

At step986, the processor60of the wirelessly connected fuel dispenser18is operable, following completion of the fuel dispensation process, to transmit a reminder message to the mobile electronic device, via the wireless communication link, to return the nozzle74to the fuel dispenser18. Thereafter at step988, the processor300of the mobile electronic device is operable to control the display320to display the reminder message.

Following step988, the processor300is illustratively operable at step990to transmit all rewards/offers selected during the fuel dispensation processed and stored in the memory304or data storage306to the fuel dispenser18via the wireless communication link. Thereafter at step992, the processor60of the wirelessly connected fuel dispenser18is operable to transfer the transmitted rewards/offers (e.g., via a corresponding one of the local servers161-16K) to the main server12, and thereafter at step994the processor20of the main server12is operable to store all of the received rewards/offers in the rewards repository814for subsequent redemption by the customer.

The “YES” branch of step984also advances to step996following a determination by the processor60of the mobile electronic device18that the fuel dispensation process is complete. At step996, the processor60is operable monitor one or more of the actuators and/or sensors206to determine whether the fuel nozzle74has been returned to the fuel dispenser18. If not, the process900loops back to step986, and otherwise the process900advances to step998where the processor20of the main server12is operable to process payment for the dispensed fuel using the customer-selected system of payment that was accepted by the processor20at step956. Thereafter at step1000, the processor20is operable to store a digital receipt of the payment in the customer-assigned section of fuel receipt database806. Thereafter at step1002, the processor20of the main server12is operable to transfer confirmation of the payment transaction to the wirelessly connected fuel dispenser18(e.g., via a corresponding one of the local servers161-16K). The processor60of the wirelessly connected fuel dispenser18is then operable, at step1004, to transmit the payment confirmation to the mobile electronic device via the wireless communication interface. The processor60is further operable at step1006, following execution of step1004, to reactivate the fuel grade/type selectors220,222on the wirelessly linked fuel dispenser18.

The processor300of the mobile electronic device is operable at step1008to control the display monitor320to display a confirmation of the payment transaction and, optionally, to display a message indicating that the fuel purchase and dispensation process is complete.

In embodiments of the process900in which the mobile electronic device is the mobile communication device80, the process900may advance to step1010. Illustratively step1010begins at step1012where the processor300of the mobile communication device80is operable to control the display screen320to display a message prompting the customer to capture a record of the odometer reading. If, at step1014the processor300determines that the customer has elected to capture a record of the odometer reading, the process advances to step1014, and otherwise the process900advances to step1032. In any case, following the “YES” branch of step1014, the processor300is operable at step1016to enable operation of the on-board camera326and to control the display monitor320to display a prompt to the customer to operate the camera to capture a photograph of the odometer of the motor vehicle76. Thereafter at step1018, the processor60is operable to determine whether the customer has captured the odometer reading in a photo using the camera and, if so, the process900advances to step1020. Otherwise, the process900returns to step1016. At step1020, the processor300is illustratively operable to process the photo to attach time, date and location data thereto, and to then transmit the processed photo to the wirelessly connected fuel dispenser18via the wireless communication link. Thereafter at step1022, the processor60of the wirelessly connected fuel dispenser18is operable to transfer the processed photo to main server12(e.g., via a corresponding one of the local servers161-16K), and thereafter at step1024the processor20of the main server12is operable to store the processed odometer photo in the customer-assigned section of the fuel receipt database806.

In embodiments of the process900in which the mobile electronic device is the vehicle communication device90, the process900may advance to step1026. Illustratively step1026begins at step1028where the processor400of the vehicle communication device90is operable to obtain, e.g., automatically, a current odometer reading from the odometer module612. Thereafter at step1030the processor400is illustratively operable to process the odometer data obtained from the odometer module, e.g., automatically, to include time, date and location data, and to transmit the processed odometer data to the wirelessly connected fuel dispenser18via the wireless communication link. Steps1022and1024are as described above, except that the processors act upon data rather than a photographic file.

In any case, step1020advances to step1032and step1022advances to step1034. The processor300of the mobile electronic device is operable at step1032, and the processor60of the wirelessly connected fuel dispenser18to disestablish the wireless communication link in a conventional manner.

It will be understood that in the illustrated process900just described, one or more of the process steps may be optional, i.e., not required, and that the illustrated processing order of one or a series of the steps of the process900may be modified without detracting from the scope of the disclosed process.

Referring now toFIG. 10, a simplified flow diagram is shown of an embodiment of a process1050for controlling operation of the mobile electronic device during purchaser-initiated exit from the process900illustrated inFIGS. 9A and 9Band/or following loss of a wireless connection with a wirelessly connected fuel dispenser18. The process1050illustratively forms part of the fuel dispenser activation module502/602, and is illustratively stored in the memory304/404and/or data storage306/406of the mobile electronic device in the form of instructions that are executable by the processor300(and/400). The process1050begins at step1052which follows execution of step902of the process900, i.e., after the wireless communication link is established between the mobile electronic device and one of the fuel dispensers18. At step1052, the processor300is operable to determine whether the customer has selected an “exit” button located on the keypad322or displayed on the display screen320throughout the process900in the form of a touch-selectable icon. If so, the process1050advances to step1054where the processor300operates to disestablish, in a conventional manner, the wireless communication link between the mobile electronic device and the wirelessly connected fuel dispenser18. The process1050advances from step1054to step1056where the processor300is operable to control the display screen320to display a message informing exit from the process900and, optionally, to prompt manual completion of the fuel dispensing process.

If, at step1052, the processor300determines that the customer has not selected the “exit” button, the process1050advances to step1058where the processor300is operable to determine whether the wireless connection has been lost. The processor300may be configured to execute step1058in any conventional manner, such as by attempting communication with the fuel dispenser18, transmitting periodic “heartbeat” signal pulses via the wireless communication circuit312, followed by “listening” for return heartbeat signals transmitted by the fuel dispenser18. In any case, if the processor300determines at step1058that the wireless connection with the fuel dispenser18has been lost, the process1050advances to step1060, and otherwise loops back to step1052. At step1060, the processor300is illustratively operable to control the display monitor320to display a message informing of the loss of the wireless connection with the fuel dispenser18and, optionally, to prompt manual completion of the fuel dispensing process. The process1050ends after completion of either of steps1056or1060.

Referring now toFIG. 11, a simplified flow diagram is shown of an embodiment of a process for controlling operation of any of the electromechanical fuel dispensers18following loss of a wireless connection with a mobile or vehicle communication device80,90, i.e., following loss of connection with a mobile electronic device. The process illustrated inFIG. 11illustratively forms part of the process900illustrated inFIGS. 9A-9B, and is therefore subject to the same process and processing described above with respect toFIGS. 9A and 9B. The process illustrated inFIG. 11follows completion of step908of the process900illustrated inFIG. 9A, e.g., following deactivation by the processor60of the fuel grade/type selectors220,222on the wirelessly linked fuel dispenser18, and begins at step1102where the processor60is operable to determine, in a conventional manner, whether the wireless communication link established with the mobile electronic device has been lost. If not, the process loops back to step1102, and if so, the process advances to step1104where the processor60is operable to reactivate the fuel grade/type selectors220,222on the wirelessly linked fuel dispenser18. Thereafter at step1106, the processor60is operable to determine in a conventional manner, e.g., by monitoring the one or more actuators and/or sensors206, whether fuel delivery was in process when the wireless communication link was lost. If not, the process terminates, and otherwise the process advances to step1108where the fuel dispenser18is operable to continue dispensing fuel subject to conventional manual control of the nozzle74. Thereafter at step1110, the processor60is operable to determine in a conventional manner, e.g., by monitoring the one or more actuators and/or sensors206, whether fuel delivery is complete. If not, the process loops back to step1108, and if so the process advances to step1112where the processor60determines, e.g., as described above, whether the fuel nozzle74has been returned to the fuel dispenser18. If not, the process loops back to step1112, and otherwise the process advances to step1114.

At step1114, the processor20of the main server12is operable to process payment for dispensed fuel using customer-selected system of payment, as described above, and thereafter at step1116the processor20is operable to store a digital receipt for the payment in a customer-assigned section of fuel receipt database806. Thereafter at step1118, the processor20is operable to transfer confirmation of completion of the fuel purchase and dispensation transaction to the fuel dispenser18. The processor60of the fuel dispenser18is then operable at step1120to control one of the display monitors214to display a message informing the total amount charged for fuel to the customer-selected system of payment and, optionally, informing of the storage of the digital receipt in customer's fuel receipt database806. Following step1120, the process advances to step1122where the processor60is illustratively operable to control one of the display monitors214to display a message prompting the customer to capture a photo of motor vehicle's odometer reading. If captured, such a photo is illustratively stored temporarily in the memory304or user data area308of the data storage306, and can be subsequently transferred to the fuel receipt database806of the main server12via wireless connection to main server12.

Referring now toFIG. 12, a simplified block diagram is shown of an embodiment of a communication system1200for conducting wireless communications between the main server12and any of a plurality of the mobile and/or vehicle communication devices. In the illustrated embodiment, for example, the main server12is illustratively shown connectable to a public network1202, e.g., the Internet, to which a number, J, of the mobile communication devices801-80Jand a number, L, of the vehicle communication devices901-90Lare also connectable, where J and L may each be any positive integer. The public network1202may illustratively be used to access the application download module832of the main server12so that copies of fuel dispenser activation modules502can be downloaded from the main server12, via the public network1202, to any number of the mobile communication devices801-80J. Likewise, the public network1202may illustratively be used to access the application download module832of the main server12so that copies of fuel dispenser activation modules602can be downloaded from the main server12, via the public network1202, to any number of the vehicle communication devices901-90L.

Referring now toFIG. 13, a simplified flow diagram is shown of an embodiment of a process1300, e.g., a set up process, for entering purchaser-specific information into the memory304and/or user data area308of the mobile communication device80using the fuel dispenser activation software application502executed by the mobile communication device80and/or for entering purchaser-specific information into the memory404and/or user data area408of the vehicle communication device90using the fuel dispenser activation software application602executed by the vehicle communication device90. The process1300may be stored in the memory304and/or data storage306of a mobile communication device80in the form of instructions which, when executed by the processor300, cause the processor300to perform the functional operations of the process1300. Likewise, the process1300may be stored in the memory404and/or data storage406of a vehicle communication device90in the form of instructions which, when executed by the processor400, cause the processor400to perform the functional operations of the process1300.

The process1300illustratively begins at step1302where a counter, K, is set equal to 1. Thereafter at step1304, the processor300,400is operable to control the display screen320,422to display a prompt to the customer to enter identification information for a Kth motor vehicle. The identification information may, in some embodiments, be as simple as a vehicle manufacturer's name, e.g., Buick, and in other embodiments may include more data about the motor vehicle, engine type, fuel type, engine specifications, vehicle specifications, etc. When the customer thereafter indicates, via customer input at step1306, that the customer has completed entry of the vehicle information, the process1300advances to step1308where the processor300,400is operable to control the display screen320,422to display a prompt to the customer to enter a specified fuel type for the Kth vehicle. The fuel type may be, for example, gasoline or diesel. When the customer thereafter indicates, via customer input at step13010, that the customer has completed entry of the fuel type, the process1300advances to step1312where the processor300,400is operable to determine whether the fuel type just entered at step1308is gasoline. If not, the process1300advances to step1318, and if so the processor advances to step1314where the processor300,400is operable to control the display screen320,422to display a prompt to the customer to enter a preferred grade of fuel for the Kth vehicle. The preferred fuel grade may, in one embodiment, be a gasoline octane rating number, e.g., 87, 89 or 93, etc., and in other embodiments may be a gasoline octane level descriptor, e.g., mid, high, performance, etc. In any case, the processor300,400is thereafter operable at step1318to control the display screen320,422to display a prompt to the customer to enter payment information for one or more systems of payment, e.g., of the one or more types described above, to which fuel for the Kth vehicle may be charged. Step1324illustratively increments the counter, K, so that the customer can enter and specify fuel type and/or grade, as well as payment information to be used with any number of motor vehicles. The processor300,400is further operable to store all such information entered by the customer in the memory304,404and/or in the data storage306,406for later recall when remotely controlling activation of one of the fuel dispensers.

Referring now generally toFIGS. 14A-22, another illustrative embodiment of is shown of a system and method for wirelessly activating an electromechanical fuel dispenser, for carrying out the subsequent fuel dispensation process through completion and, optionally, for providing wirelessly connected purchasers of fuel with purchaser-specific discount rewards/offers for one or more goods and/or services offered for sale by an enterprise via which the fuel is purchased. In the embodiment illustrated inFIGS. 14A-22, the system10is illustratively as illustrated and described with respect toFIGS. 1-8 and 12, although in some embodiments the software environment800of the main server12and/or the memory of the mobile electronic device, e.g., the memory304of the mobile communication device80and/or the memory404of the vehicle communication device90, illustratively include one or more alternate or additional modules. Referring toFIG. 14A, for example, a modified embodiment802′ of the server database within the software environment800of the main server12may in some embodiments include fuel center/dispenser location data816having stored therein location data identifying locations of the various fuel centers521-52Kand/or of the various fuel dispensers181-18N,181-18Mrelative to one or more known locations and/or structures, or from which the locations of the various fuel centers521-52Kand/or of the various fuel dispensers181-18N,181-18Mcan be determined by the processor20of the main server12and/or by the processor of a mobile electronic device, e.g., the processor300of a mobile communication device80or the processor400of a vehicle communication device90. Examples of such location data stored in the fuel center/dispenser location data816, as well as example processing of such data, will be described hereinafter with respect toFIGS. 18-22.

Referring toFIG. 14B, modified embodiments830′ of the fuel dispenser management module within the software environment800of the main server12may additionally include one or more of an EMS interface module844, a CUSTID generation module846, a beacon module848, a fuel dispenser ID module850and a fuel center/dispenser locator module852. The EMS interface module844is illustratively operable to provide, control and manage a customer interface to the EMS program, e.g., a web-based EMS interface or EMS website to provide for customer entry of fuel grade/type and automatic fuel purchase payment preferences, some or all of which will illustratively be implemented by the processor20of the main server12via execution of the remote controlled fueling module842during subsequent fuel purchases at any of the fuel dispensers181-18N,181-18M. An example embodiment of a process executed by the EMS interface module844is illustrated inFIG. 15, and an example embodiment of a process executed by the remote controlled fueling module84to implement the customer fuel grade/type and/or payment preferences is illustrated inFIG. 17. Such processes will be described in detail hereinafter.

The CUSTID generation module846is illustratively operable to generate a customer identification code, CUSTID, to be stored in and used by a customer's mobile electronic device, e.g., mobile communication device80and/or vehicle communication device90, to identify the main server12the identity of the customer-member of the EMS program and to securely identify electronic payment information (EPI) previously established by the customer-member for automatic payment for fuel purchases. Referring toFIG. 14C, modified memories304′ of mobile communication devices80and/or404′ of vehicle communication devices90likewise illustratively include in such embodiments a CUSTID generation module520,620respectively. Example embodiments of processes executed in-part by the CUSTID generation module846and in-part by the CUSTID generation module520,620are illustrated inFIGS. 16A and 16B, and such processes will be described in detail hereinafter.

The beacon module848is illustratively included in embodiments in which wireless signal broadcasting devices, e.g., beacons224and/or710, are used to locate fuel dispensers181-18N,181-18Mat which EMS member-customers are located and from which such customer-members desire to dispense fuel. In such embodiments, the beacon module848is illustratively operable to determine the identity of a beacon224(and/or710) associated with the fuel dispenser18from which a customer-member of the EMS program wishes to dispense fuel, and to thus identify the associated fuel dispenser18for purposes of controllably activating the dispensing section204of the identified fuel dispenser18for subsequent dispensation of fuel. In such embodiments, the fuel center/dispenser location data816illustratively contains information about each beacon224,710in the retail enterprise. In some embodiments, such beacon information includes the unique identification codes (UID) of each beacon224,710. In other embodiments, the beacon information may additionally include beacon type information identifying or associating a beacon type, BT, with each beacon224,710. In some such embodiments, the beacon information may be stored, e.g., separately, in the database816according to beacon type. In some embodiments, the database816may include additional information including, for example, but not limited to, positional information corresponding to the coordinates of some or all of the beacons of the retail enterprise and/or of one or more fuel centers521-52Kthereof, relative to one or more sets of base coordinates or positional information corresponding to the coordinates of some or all of the fuel dispensers181-18N,181-18Mof the retail enterprise and/or of one or more fuel centers521-52Kthereof, relative to one or more sets of base coordinates. In such embodiments, the beacon module848is illustratively operable to process beacon-related information transmitted to the main server12by customers' mobile electronic devices, e.g.,80and/or90, and to control transmission of corresponding and related information back to the customers' mobile electronic devices. Referring toFIG. 14C, modified memories304′ of mobile communication devices80and/or404′ of vehicle communication devices90likewise illustratively include in such embodiments a customer/fuel dispenser identification module522,622respectively. An example embodiment of a process executed in-part by the beacon module848and in-part by the customer/fuel dispenser identification module522,622is illustrated inFIG. 18and will be described in detail hereinafter.

The fuel dispenser ID module850is illustratively included in embodiments in which the fuel dispenser ID200and/or fuel center ID700is/are used to locate fuel dispensers181-18N,181-18Mat which EMS member-customers are located and from which such customer-members desire to dispense fuel. In such embodiments, the fuel dispenser ID module850is illustratively operable to determine the identity of a fuel dispenser18from which a customer-member of the EMS program wishes to dispense fuel, and to thus identify the associated fuel dispenser18for purposes of controllably activating the dispensing section204of the identified fuel dispenser18for subsequent dispensation of fuel. In such embodiments, the fuel center/dispenser location data816may illustratively contain information associating fuel dispenser IDs200and/or fuel center IDs700and/or fuel dispenser IDCODEs with corresponding ones of the fuel dispensers181-18N,181-18M. In such embodiments, the customer/fuel dispenser identification module522,622illustrated inFIG. 14Clikewise contains instructions to facilitate locating and identifying fuel dispensers18via the fuel dispenser ID200and/or the fuel center ID700. An example embodiment of a process executed in-part by the fuel dispenser ID module850and in-part by the customer/fuel dispenser identification module522,622is illustrated inFIG. 20and will be described in detail hereinafter.

The fuel center/dispenser module852is illustratively included in embodiments in which the GPS position of the mobile electronic device and geofence data relating to the location-based positions of the various fuel centers521-52Kand/or of the various fuel dispensers181-18N,181-18Mare used to locate fuel dispensers181-18N,181-18Mat which EMS member-customers are located and from which such customer-members desire to dispense fuel. In such embodiments, the fuel center/dispenser module852is illustratively operable to determine the position of a customer-member's mobile electronic device relative to a fuel center52and/or a fuel dispenser18from which a customer-member of the EMS program wishes to dispense fuel, and to identify the associated fuel dispenser18for purposes of controllably activating the dispensing section204of the identified fuel dispenser18for subsequent dispensation of fuel. In such embodiments, the fuel center/dispenser location data816may illustratively contain geofence data in the form of geographic boundaries related to the various fuel centers521-52Kand/or the various fuel dispensers181-18N,181-18M. In such embodiments, the customer/fuel dispenser identification module522,622illustrated inFIG. 14Cillustratively contains instructions to provide geographic position data relating to the location of the customer-member's mobile electronic device to the main server. An example embodiment of a process executed in-part by the fuel center/dispenser module852and in-part by the customer/fuel dispenser identification module522,622is illustrated inFIG. 21and will be described in detail hereinafter.

Referring now toFIG. 15, a simplified flow diagram is shown depicting an embodiment of a process1500for facilitating entry by a customer into the customer's EMS account, e.g., within the customer account data804of the database802, electronic payment information (EPI) for one or more electronic payment systems (EPS) that the customer authorizes, e.g., by entry of the EPI for one or more specified EPSs into the customer's EMS account, the main server12to automatically process in future transactions as payment for the purchase of fuel via an identified one of the fuel dispensers181-18N,181-18M. The process1500may, in some embodiments such as that illustrated inFIG. 15, additionally or alternative include process steps for facilitating entry by a customer into the customer's EMS account fuel grade and/or type information (FGT) corresponding to a type and/or grade of fuel which the customer authorizes, e.g., by entry of the FGT information into the customer's EMS account, the main server12to automatically control the identified fuel dispenser181-18N,181-18Mto deliver in future transactions for the purchase of fuel. In embodiments in which the customer enters multiple EPIs into the customer's EMS account data804, one such EPI, e.g., the first one entered or otherwise designated by the customer, may be referred to herein as a “default EPI,” “default electronic payment information” or “default electronic funds transfer instrument” and in embodiments in which the customer enters a single EPI into the customer's EMS account data804the single EPI may likewise be referred to herein as a “default EPI,” “default electronic payment information” or “default electronic funds transfer instrument.” Similarly, in embodiments in which the customer enters a fuel grade or type FGT into the customer's EMS account data804, the FGT may be referred to herein as a “default FGT” or “default fuel grade or type,” or in some instances more specifically as a “default fuel grade” or “default fuel type.” Such use of the word “default” will generally indicate a first corresponding parameter selected and applied by the main server12in a fuel purchase transaction, and that the customer may in some instances be provided with an opportunity to select an alternate or customer-defined parameter. For example, in some embodiments the default EPI may for some reason fail a payment authorization check carried out or otherwise requested by the main server12, and in such instances the customer may select an alternate in the customer's EMS account data804if the customer has previously entered multiple EPIs therein or the customer may, in some embodiments, manually enter an alternate EPI into the customer's mobile electronic device prior to or as part of the fuel purchase transaction. As another example, in some embodiments the customer may, as part of a fuel purchase transaction, be requested or prompted by the main server12to confirm a default EPI and/or FGT, and in such embodiments the customer may confirm the default EPI and/or FGT or may instead select an alternate EPI or FGT. The process1500further illustratively includes a process for creating or generating a customer identification code, CUSTID, to associate with the customer and with the authorized EPS for the purpose of identifying and authorizing access by the main server12to the authorized EPS in any such future purchase transaction in which the authorized EPS is automatically processed by the main server12. Example embodiments of the CUSTID generation process are illustrated inFIGS. 16A and 16B, and each will be described in detail hereinafter.

In one embodiment, the process1500is stored in the memory24(and/or data storage26) of the main server12in the form of instructions executable by the processor20of the main server12, and the process steps of the process1500will be described below for purposes of this disclosure as being executed by the processor20of the main server12. It will be understood, however, that in some alternate embodiments, the process1500may be alternatively stored, in whole or in part, in the memory44(and/or data storage46) of the one or more of the local servers161-16Kin the form of instructions executable, in whole or in part, by the processor40of one or more of the local servers161-16K, and in still other embodiments the process1500may be stored, in whole or in part, in the memory64(and/or data storage66) of the one or more of the fuel dispensers181-18N,181-18Min the form of instructions executable, in whole or in part, by the processor60of one or more of the one or more of the fuel dispenser181-18N,181-18M. In any such embodiments, the process1500may be executed in whole or in part by one or more processors within any one or a combination of the main server12, any of the one or more local servers161-16Kand any of the one or more of the fuel dispensers181-18N,181-18Mand, wherein information may be shared between the such systems via wired and/or wireless connection.

The process1500illustratively operates separately with respect to each enterprise membership service account number, i.e., each EMSID. In this regard, the process1500begins at step1502where the processor20is operable to determine that a customer has accessed that customer's page of the EMS interface, e.g., an access page of one or more dedicated and private pages of the EMS website hosted by the main server12and associated or assigned to the customer, using the customer's EMSID. Access by the customer of the customer's page of the EMS interface may be accomplished, for example, using a mobile communication device80, a vehicle communication device90or another web-accessible computing device. In any case, upon detection of such access by the customer of the customer's page of the EMS interface, the process1500advances to step1504where the processor20is operable to generate and include for display on the accessed customer's page of the EMS interface a graphic user interface (GUI) which includes a fuel dispenser activation (FDA) element. The FDA element illustratively acts as a gateway by which the customer can enter fuel purchase preferences into the customer's EMS account data804. Upon selection by the customer of the FDA element, the processor20is operable at step1506to generate for display on the accessed customer's page of the EMS interface a prompt for the customer to enter communication information (CI), and thereafter at step1508the customer enters into the EMS interface the communication information (CI) requested by the processor20. Illustratively, the communication information (CI) requested by the processor20and entered into the EMS interface is or includes one or more communication code(s), e.g., in the form of one or more sequences of numbers, letters of any alphabet, punctuation symbols and/or other symbols, that identifies a mobile electronic device, e.g., a mobile communication device80or a vehicle communication device90, that will be used by the customer to communicate with the main server12during fuel purchase transactions in which the authorized EPI and/or authorized FGT will be automatically processed by the main server12. In one embodiment, the communication information (CI) may be or include the telephone number of the identified mobile communication device80. In other embodiments, the communication information (CI) may be or include a serial number, electronic identification code or other communication identifier associated with a vehicle communication device90. In still other embodiments, the communication information (CI) may be or include, in place of or in addition to a telephone number or communication identifier of the customer's mobile electronic device, one or more other unique mobile electronic device identification codes that identify the specified mobile electronic device for purposes of wireless communication therewith. In embodiments in which the customer's EMS account data804already includes or has access to the customer's communication information (CI), steps1506and1508may be omitted or modified to require the customer to acknowledge and authorize use thereof by the processor20, for generation of the CUSTID code, and/or modified to allow the customer to authorize use by the processor20, for generation of CUSTID code, of communication information (CI) other than that identified in the customer's EMS account data804. In any case, following execution of step1508, the communication information (CI) obtained and to which the processor20has access identifies communication information (CI) for a mobile electronic device associated with the customer via which wireless communications with the main server12will be conducted and with which the processor20is authorized to communicate during future fuel purchase transactions.

In the embodiment of the process1500illustrated inFIG. 15, the processor20is operable at step1510, upon customer entry of the communication information (CI), to generate and include for display on the accessed customer's page of the EMS interface a fuel selection graphic user interface (GUI) which includes one or more fields for entering or selecting a preferred fuel grade and/or type (FGT). Thereafter at step1512, the customer enters FGT into the one or more fields of the fuel selection GUI or selects FGT from one or more menus or selectable fuel grade and/or type options pre-populated by the main server12in the one or more fields of the fuel selection GUI. As one example, which should not be considered limiting in any way, the processor20may be operable at step1510to generate the fuel selection GUI to include a menu of fuel types and fuel grades, e.g., “Diesel,” for diesel fuel and “Premium,” “Regular” and “Economy” or octane rating number such as “92,” “89” and “87” for gasoline, and the user may select FGT from such a menu. As another example, which should not be considered limiting in any way, the processor20may be operable at step1510to generate the fuel selection GUI to include a first menu of fuel types, e.g., “Diesel” and “Gasoline,” and after a user selects a fuel type from the first menu the processor20may be operable to generate a second menu of fuel grades, e.g., “Premium,” “Regular” and “Economy” or octane rating number such as “92,” “89” and “87” if the user has first selected “Gasoline” as the fuel type. Those skilled in the art will recognize other techniques for allowing the user to specify at steps1510and1512a fuel type and/or grade, and such other techniques are intended to fall within the scope of this disclosure. Moreover, it will be understood that the processor20may be operable at step1510to generate more, fewer and/or different fuel types and/or grades for customer selection thereof without detracting from the scope of this disclosure.

Following step1512, the process1500advances to step1514where the processor20is operable to generate and include for display on the accessed customer's page of the EMS interface or as a new page for display on the accessed customer's page of the EMS interface, an electronic payment system graphic user interface (EPS GUI) with a plurality of fields in which the user can enter electronic payment information (EPI) associated with an EPS selected by the customer. Thereafter at step1516, the customer enters the EPI of a selected EPS into the plurality of EPS GUI fields. As used herein, the term “electronic payment system” or “EPS” refers generally to any instrument of electronic funds transfer that is identifiable by an account number, card number, access number, code or other identification and that may be used by a customer and accepted by the retail enterprise in the course of a fuel purchase transaction to satisfy payment for fuel purchased by the customer from the retail enterprise via a one of the fuel dispensers181-18N,181-18M. Examples of such instruments of electronic funds transfer include, but are not limited to, credit cards, debit cards, pre-paid credit cards, on-line money transfer accounts, wire transfer accounts, electronic or digital money certificates and/or accounts, ecommerce payment systems, and the like.

As used herein, the term “electronic payment information” or “EPI” refers generally to information uniquely associated with an EPS that identifies the EPS for purposes of transferring funds from the EPS to the retail enterprise. In some embodiments, the EPI may be or include an account or identification number or code that specifically identifies the EPS, e.g., a credit card number. In other embodiments, the EPI may include one or more numbers or codes, e.g., a security code, in addition to the identification number or code. Any such “code” referred to in herein will be understood to be a unique combination, at least for purposes of identifying an EPS account, of one or more numerical digits, one or more letters of an alphabet in any language, one or more punctuation symbols and/or one or more symbols other than punctuation symbols. In still other embodiments, the EPI may include information alternatively to, or in addition to, an account or identification number/code (and, in some embodiments, further alternatively to or in addition to a security number/code), examples of which may include the name of the person to whom the EPS is issued, birthdate of the person to whom the EPS is issued, part or all of the address of the person to whom the EPS is issued, part or all of the billing address of the payer or other funding source of the EPS, contact information, such as one or more telephone or mobile phone numbers, one or more email addresses, etc. of the person to whom the EPS is issued and/or of the payer or other funding source of the EPS, identity of and/or other information about the EPS issuer, the EPS payment processing organization, e.g., Visa®, MasterCard®, etc., or the like. It will be understood that “EPI,” as used herein, may be or include one or any combination of any of the foregoing numbers, codes and/or information, and that information about the EPS, in addition to EPI, may be required by the process1500to be entered by the customer into the EPS GUI displayed at step1514. As one specific example, the EPI in one embodiment may be defined completely by a combination of an account or identification number and security code of the EPS, although the process1500may additionally require some or all of the information just described to be entered into the displayed EPS GUI in order to completely satisfy step1516, i.e., in order for the process1500to advance from step1516to step1518.

Following step1516, the process1500advances to step1518where the processor20is illustratively operable to store EMSID, CI, FGT and EPI in the customer account database804, and further to associate EMSID, CI, FGT and EPI with each other in the database804. It will be understood that the term “associate” as used in the previous sentence refers to a linking of parameters within the database such that a successful search for one parameter by the processor20in the database804will provide access to the remaining associated parameters. Such data association may be accomplished using, for example, one or more conventional tables, charts, arrays, linked lists, or other conventional data association techniques. While in the embodiment just described the EPI is stored by the processor20in the customer account data804of the database402, the EPI and or one or more of the remaining parameters listed above may be stored, in whole or in part, elsewhere in one or more other databases or memory units within or outside of the system10.

Following step1518, the process1500illustratively advances to step1520where the processor20is operable to prompt the customer, e.g., via a suitable graphic user interface or graphic user interface element displayed on the accessed customer's page of the EMS interface, for additional EPI, i.e., to add EPI for another EPS different and separate from that just entered. If the customer elects to do so by selecting the GUI prompt at step1520, the process1500loops back to step1514where a customer may enter EPI for another EPS. Illustratively, the first-entered EPI may be the “default EPI” or the process1500may further include another one or more steps via which the customer may select as the default EPI one of multiple EPIs entered by the customer. In any case, if/when the customer declines to enter one or more additional EPIs, the process1500follows the “NO” branch of step1520to step1522.

At step1522the processor20is operable to execute the CUSTID generation process in which the processor20generates the CUSTID, i.e., a customer identification code which will be used to by the processor20to identify the customer and an EPS authorized by the customer for processing of payment for the purchase of fuel at future fuel purchase transactions conducted via one of the fuel dispensers181-18N,181-18M. A number of different embodiments of the CUSTID generation process executed at step1522are illustrated by example inFIGS. 16A and 16B. Following step1522, the process1500illustratively ends. It will be understood that the process1500may illustratively include more, fewer and/or different steps to include correspondingly more, fewer and/or different features. In one alternative embodiment, for example, steps1510-1512may be omitted such that the process1500provides only for the entry and identification of EPI for one or more electronic payment systems (EPS) to be processed by the main server12in the course of subsequent fuel purchase transactions to satisfy payment for fuel purchased by the customer from the retail enterprise via a one of the fuel dispensers181-18N,181-18M. In other alternative embodiments, steps1514-1516may be omitted such that the process1500provides only for the entry and identification of FGT to be processed by the main server12in the course of subsequent fuel purchase transactions for the purpose of controlling an identified fuel dispenser181-18N,181-18Mfor dispensation of fuel corresponding FGT. In still further alternative embodiments, steps may be added to the process1500to include one or more additional features, examples of which may include, but are not limited to, automatic or selective application of discount fuel coupons, automatic or selective application to the fuel purchase price of monetary credit in the form of “digital cash” contained in a digital wallet or other account that is part of or otherwise inked to the customer's EMS account, or the like.

Referring now toFIG. 16A, a simplified flow diagram is shown of an embodiment of a process1600for executing the CUSTID (customer identification) generation process1602identified at step1522of the process1500illustrated inFIG. 15. In the embodiment illustrated inFIG. 16A, CUSTID is illustratively generated in a form that will be stored in, or accessed by, a mobile electronic device such as a mobile communication device80carried by the customer or a vehicle communication device90carried by or mounted in a vehicle76to be refueled, which will then be automatically transferred from the mobile electronic device to the main server12during transactions for the purchase of fuel via one of the fuel dispensers181-18N,181-18Min which an authorized EPS is to be automatically processed by the main server12.

In one embodiment, the process1600is stored in the memory24(and/or data storage26) of the main server12in the form of instructions executable by the processor20of the main server12, and the process steps of the process1600will be described below for purposes of this disclosure as being executed by the processor20of the main server12. It will be understood, however, that in some alternate embodiments, the process1600may be alternatively stored, in whole or in part, in the memory44(and/or data storage46) of the one or more of the local servers161-16Kin the form of instructions executable, in whole or in part, by the processor40of one or more of the local servers161-16K, and in other embodiments the process1600may be stored, in whole or in part, in the memory64(and/or data storage66) of the one or more of the fuel dispensers181-18N,181-18Min the form of instructions executable, in whole or in part, by the processor60of one or more of the one or more of the fuel dispensers181-18N,181-18M. In any such embodiments, the process1600may be executed in whole or in part by one or more processors within any one or a combination of the main server12, any of the one or more local servers161-16Kand any of the one or more of the fuel dispensers181-18N,181-18M, wherein information may be shared between the such systems via wired and/or wireless connection.

The embodiment illustrated inFIG. 16Aillustratively requires the mobile electronic device, e.g., the mobile communication device80or the vehicle communication device90, to include the CUSTID generation module520,620described hereinabove with respect toFIG. 14C. In the embodiment illustrated inFIG. 16A, the CUSTID generation module520,620is or includes a software application which, when executed by the processor300,400of the mobile electronic device, causes the processor300,400to load the CUSTID code generated by the process1600from a memory location within or outside of the customer's mobile electronic device into the customer/fuel dispenser identification module522,622also illustrated inFIG. 14C.

In the embodiment illustrated inFIG. 16A, the CUSTID generation process1600begins at step1604where the processor20is operable to create the CUSTID code. Illustratively, the CUSTID code is created by the processor20in the form of a passcode, pin, token or other code as one or more unique sequences of bits. In one embodiment, the one or more unique sequences may be defined by or include one or more digits, one or more letters of any alphabet, one or more punctuation symbols or one or more other symbols, and may be assembled in the form of one or more appended or integrated sequences of bits or in the form of one or more separate sequences of bits. In other embodiments, some or all of any such one or more sequences of bits may be or include one or more sequences of bits that do/does not define any digit, letter, punctuation symbol or other symbol. In some embodiments, the CUSTID code may be generated by the processor20randomly or pseudo-randomly. In other embodiments, the CUSTID code may be generated by the processor20as a function of one or more variables generally. In some such embodiments, the CUSTID code may be generated by the processor20as a function of information relating to the customer, to the customer's EMS account, to the customer's mobile electronic device, or as any combination thereof. Examples of information relating to the customer include, but are not limited to, customer's name, customer's address, customer's email address, or the like, examples of information relating to the customer's EMS account include, but are not limited to, the customer's EMSID, one or more portions of the EPI defined by or relating to the authorized EPS (i.e., an EPS authorized according to a process such as that illustrated at steps1514-1516ofFIG. 15), one or more portions of EPI relating to one or more additional EPSs identified within the customer's EMS account, or the like, and examples of information relating to the customer's mobile electronic device include, but are not limited to, any portion of the communication information provided at step1508of the process1500illustrated inFIG. 15or the like.

In some embodiments the CUSTID code may be generated solely by the processor20in the form of a single code or two or more appended or separate codes. In other embodiments, customer may specify, e.g., via a suitable GUI, some or all of the CUSTID code. In some such embodiments in which the customer enters some of all of the CUSTID code, the customer-entered CUSTID code may act as an initial customer code which the processor20is operable to process using any conventional processing technique to produce a second CUSTID code which then replaces, is integrated with or is appended to the customer-entered CUSTID code. Those skilled in the art will recognize other techniques for generating a CUSTID code that may or may not be a function of one or more variables, and it will be understood that any such alternate techniques are contemplated by this disclosure.

Following step1604, the process1600advances to step1606where the processor20is operable to associate the generated CUSTID code with the customer's EMSID, i.e., the EMSID entered by the customer to access the process1500. In some embodiments, the processor20is alternatively or additionally operable at step1606to associate the generated CUSTID code with the EPI of the authorized EPS, i.e., the EPI entered by the customer at step1516of the process1500. In some embodiments, the processor20is alternatively or additionally operable at step1606to associated the generated CUSTID code with FGT and/or CI entered by the customer in the process1500. In one embodiment, the processor20is operable to execute step1606by storing the CUSTID code in a database and then linking the stored CUSTID code to stored values of EMSID and/or EPI and/or FGT and/or CI using one or more conventional data association techniques. Illustratively, the generated CUSTID code may be stored by the processor20, in whole or in part, in the customer account data804of the database802, or elsewhere in one or more other databases or memory units within or outside of the system10. In such embodiments, the processor20is illustratively operable to link the stored CUSTID code to stored values of EMSID and/or EPI and/or FGT and/or CI using one or more conventional linking or pointing mechanisms, examples of which include, but are not limited to, a table, a chart, a linked list or other pointer, or the like. In embodiments in which the CUSTID code includes the customer's EMSID, the processor20is illustratively operable at step1606to associate the CUSTID code only with the stored value(s) of EPI, FGT and/or CI.

Following step1606, the process1600advances to step1608where the processor20is operable to transmit the generated CUSTID code to the customer, e.g., via email, or to the customer's mobile electronic device, e.g., via a short message service (sms) or other wireless communication technique or protocol. Alternatively, the processor20may make the CUSTID code available to the customer via the customer's EMS account. In any case, outside of the process1600controlled by the processor50, the customer loads the CUSTID code into the CUSTID generation module520,620on the customer's mobile electronic device, or into the customer's mobile electronic device for subsequent transfer by the CUSTID generation module520,620to the customer/fuel dispenser identification module522,622, as illustrated inFIG. 6Aby the process step A. In one embodiment, the CUSTID generation module520,620includes conventional software which guides the customer in transferring the generated CUSTID code from the customer's email or sms into the customer/fuel dispenser identification module522,622, and in other embodiments the CUSTID generation module520,620includes conventional software that automatically transfers the generated CUSTID code into the customer's mobile electronic device from the customer's EMS account or other location. In any case, following completion of step1608, the process1600returns to the process1500illustrated inFIG. 15.

Referring now toFIG. 16B, a simplified flow diagram is shown of another embodiment of a process1650for executing the CUSTID code generation process identified at step1522of the process1500illustrated inFIG. 15. Illustratively, the process1650may be used in addition to or in place of the CUSTID generation process1600illustrated inFIG. 16A. In the embodiment illustrated inFIG. 16B, the CUSTID generation process1650is an interactive process that takes place between the processor20of the server12and the processor300,400of a customer's mobile electronic device (e.g., the customer's mobile communication device80or the customer's vehicle communication device90), and which is therefore executed, in-part, by the processor20and, in-part, by the processor300,400. In this regard, the process1650is illustratively one that is stored, in one embodiment, in-part in the memory24(and/or data storage26) of the main server12in the form of instructions executable by the processor20of the main server12and in-part in the memory304,404or data storage306,406of customer mobile electronic device(s) in the form of instructions executable by the processor300,400of the mobile electronic device(s), and the process steps of the process1650will thus be described below for purposes of this disclosure as being executed in part by the processor20of the main server12and in part by the processor300,400of the mobile electronic device(s). It will be understood, however, that in some alternate embodiments, the part of the process1650executed by the processor20of the main server12may be alternatively stored, in whole or in part, in the memory44(and/or data storage46) of the one or more of the local servers161-16Kin the form of instructions executable, in whole or in part, by the processor40of one or more of the local servers161-16K, and in other embodiments this part of the process1650may be stored, in whole or in part, in the memory64(and/or data storage66) of the one or more of the fuel dispensers181-18N,181-18Min the form of instructions executable, in whole or in part, by the processor60of one or more of the one or more of the fuel dispensers. In any such embodiments, the part of the process1650indicated inFIG. 16Bas being executed by the main server12may be executed in whole or in part by one or more processors within any one or a combination of the main server12, any of the one or more local servers161-16Kand any of the one or more of the fuel dispensers181-18N,181-18M, wherein information may be shared between the such systems via wired and/or wireless connection.

In the embodiment illustrated inFIG. 16B, as with that illustrated inFIG. 16A, the CUSTID code is illustratively generated in a form that will be stored in, or accessed by, the customer's mobile electronic device, e.g., the customer's mobile communication device80and/or the customer's vehicle communication device90. As described hereinabove with respect toFIG. 16A, the CUSTID code stored in or accessed by the customer's mobile electronic device will then be automatically transferred from the mobile electronic device to the main server12during transactions for the purchase of fuel from the retail enterprise11via one of the fuel dispensers181-18N,181-18Min which an authorized EPS is to be automatically processed by the main server12.

The process1650illustrated inFIG. 16Bbegins at step1652where the processor20of the main server12is operable to generate and include for display on the accessed customer's page of the EMS interface, or as a new page for display on the accessed customer's page of the EMS interface, a graphic user interface (GUI) prompting the customer to activate the software application contained in the CUSTID generation module520,620on the customer's mobile electronic device. If the customer has not already activated the CUSTID generation software application on the customer's mobile electronic device, the customer does so at step1654in response to the prompt at step1652.

Following step1652, the processor20is operable at step1656to generate and display code, e.g., a random, pseudo-random or other code, RC, and to instruct the customer to enter RC into a corresponding screen or field displayed or accessible on the customer's mobile electronic device as part of the CUSTID generation software application. Thereafter at step1658, the customer is responsive to the instructions at step1656to enter the code, RC, into the corresponding field or screen displayed on the customer's mobile electronic device, and the processor300,400of the mobile electronic device is thereafter responsive at step1660to such customer entry of the code, RC, to transmit the code, RC, and one or more additional data to the main server12, which transmission is thereafter received by the processor20at step1662. The steps1656-1660are illustratively included in the process1650to establish communication between the processor20and the processor300,400, and to further establish the identity of the mobile electronic device with which the processor20is communicating. In this regard, the one or more additional data which may accompany the code, RC, transmitted by the customer's mobile electronic device at step1660may be or include any information which establishes the identity of the customer within the EMS program and/or the identity of the mobile electronic device as one that is associated with the customer within the EMS program. Examples of such data may include, but are not limited to, one or more of the customer's EMSID, the customer's email address, the communication code, e.g., cellular telephone number or other communication identifier, of the customer's mobile electronic device with which the processor20is communicating, and the like.

Following receipt of the code, RC, (and, in some embodiments, any additional data) from the mobile electronic device at step1662, the processor20is operable at step1664to generate a CUSTID code and to transmit the generated CUSTID code to the mobile electronic device. After receipt by the mobile electronic device at step1666of the generated CUSTID code transmitted by the processor20, the processor300,400of the mobile electronic device is operable at step1668to store the CUSTID code in the memory304,404or data storage306,406, and/or in one or more off-board but otherwise accessible memories, for subsequent recall in a conventional manner. In the meantime, the processor20of the main server12is operable following step1664to locate within the customer's EMS account, at step1670, the customer's EMSID and/or EPI of the authorized EPS and/or FGT and/or CI, and thereafter at step1672to store the generated CUSTID code in memory and associate the generated CUSTID code with the customer's EMSID and/or the EPI and/or the FGT and/or the CI.

In one embodiment, the generated CUSTID code is stored by the processor20in the customer account data804of the database802. In alternate embodiments, the CUSTID code may be stored, in whole or in part, elsewhere in one or more other databases or memory units within or outside of the system10. The association between the CUSTID code and the customer's EMSID and/or the EPI of the authorized EPS and/or the FGT and/or the CI may likewise be stored in the customer account data804of the database802, although such association may in alternate embodiments be stored, in whole or in part, elsewhere in one or more other databases or memory units within or outside of the system10. The CUSTID code itself may also be stored in the same database as the EPI and/or EMSID and/or FGT and/or CI, or may alternatively be stored, in whole or in part, in one or more other databases or memory units within our outside of the system10. In any case, the processor20is illustratively operable to execute step1672using any one or more conventional data association mechanisms, examples of which include, but are not limited to, a table, a chart, a linked list or other pointer, or the like.

It will be understood that the CUSTID code described above with respect to the processes1600and1650may be or include one or more combined codes or sequences of codes or may alternatively be or include a plurality of separate codes or sequences of codes. In some embodiments, for example, the CUSTID code may be generated and stored as a single sequence of bits or characters, while in other embodiments the CUSTID code may be generated and stored in the form of two or more distinct and separate sequences of bits or characters. In one specific example, which should not be considered to be limiting in any way, the CUSTID code may be generated as a first sequence of bits that is or is a function of the customer's EMSID and a second, separate sequence of bits in the form of a security code that may or may not be a function of information relating to the customer, the customer's EMS account and/or the customer's mobile electronic device. As will be described in greater detail below, the customer's mobile electronic device may wirelessly transmit any such CUSTID code to the main server12as a single code as part of a single transmission, as a single code broken up into multiple transmissions, as multiple codes transmitted in a single transmission or as multiple codes each transmitted in separate, multiple transmissions. Moreover, in any such multiple transmissions of the CUSTID code, the customer's mobile electronic device may be operable to execute such multiple transmissions without interruption by or data requests by the processor20of the main server12. In some alternative embodiments, the customer's mobile electronic device and the processor20may be operable to accomplish the multiple transmissions with the customer's mobile electronic device executing one or more of the multiple transmissions in response to one or more requests transmitted by the processor20to the customer's mobile electronic device. In other alternative embodiments, the customer's mobile electronic device and the processor20may be operable to accomplish the multiple transmissions with the customer's mobile electronic device executing one or more of the multiple transmissions in response to one or more acknowledgements transmitted by the processor20to the customer's mobile electronic device of one or more data transmission notifications previously transmitted by the customer's mobile electronic device.

Referring now toFIG. 17, a simplified flow diagram is shown depicting another embodiment of a process1700for wirelessly activating one of the electromechanical fuel dispensers illustrated inFIG. 1and for carrying out the subsequent fuel dispensation process through completion. As indicated by the framework of the process1700illustrated inFIG. 17, a portion of the process1700, i.e., the portion to the left of the left-most vertical line and centered under the heading “MDC/VCD,” represents one or more software applications executed by a processor (e.g., processor300or400) of a mobile electronic device (e.g., the mobile communication device80and/or vehicle communication device90respectively). In one embodiment, as will be described in greater detail below, part of this portion of the process1700is illustratively contained in the fuel dispenser activation module502and part is contained in the customer/fuel dispenser identification module530, both stored in the memory304(and/or data storage306) of the mobile communication device80in the form of instructions executable by the processor300of the mobile communication device80, and the process steps of this portion of the process1700will be described below for purposes of this disclosure as being executed by the processor300of the mobile communication device80. It will be understood, however, that in some alternate embodiments, part of this portion of the process1700may be alternatively contained in the fuel dispenser activation module602and part contained in the customer/fuel dispenser identification module630, both of which may be stored in the memory404(and/or data storage406) of the vehicle communication device90in the form of instructions executable by the processor400of the vehicle communication device90. In still other alternate embodiments, part of this portion of the process1700may alternatively still be contained in the fuel dispenser activation module502, part may be contained in the fuel dispenser activation module602, part may be contained in the customer/fuel dispenser identification module530, and/or part may be contained in the customer/fuel dispenser identification module630, all of which may be stored in the memory304(and/or data storage306) of the mobile communication device80in the form of instructions executable, in part, by the processor300of the mobile communication device80and/or in the memory404(and/or data storage406) of the vehicle communication device90in the form of instructions executable, in part, by the processor400of the vehicle communication device90.

Another portion of the process1700, i.e., the portion between the two vertical lines and centered under the heading “Fuel Dispenser” represents the remote activation module software application252that is executable by the processor60of each of the plurality of fuel dispensers181-18N,181-18Mand/or the remote activation module software application722that is executable by the processor40of each of the local servers161-16K. In one embodiment, this portion of the process1700is illustratively stored in the memory64(and/or data storage66) of the fuel dispensers181-18N,181-18Min the form of instructions executable by the processor60of the fuel dispensers181-18N,181-18M, and the process steps of this portion of the process1700will be described below for purposes of this disclosure as being executed by the processor60of the fuel dispensers181-18N,181-18M. It will be understood, however, that in some alternate embodiments, this portion of the process1700may be stored in the memory44(and/or data storage46) of the local servers161-16K, in the form of instructions executable by the processor40of the local servers161-16K(or stored in the memory24and/or data storage26of the main server12in the form of instructions executed by the processor20of the main server12, in embodiments that do not include the local servers161-16K). In still other alternate embodiments, this portion of the process1700may be stored, in whole or in part, in the memory64(and/or data storage66) of the fuel dispensers181-18N,181-18Min the form of instructions executable, in part, by the processor60of the fuel dispensers181-18N,181-18Mand in part by the processor40of a corresponding one of the local servers161-16K, or stored, in whole or in part, in the memory44(and/or data storage46) of the local servers161-16Kin the form of instructions executable, in part, by the processor40of the local servers161-16Kand in part by the processor60of a corresponding one of the fuel dispensers181-18N,181-18M.

Yet another portion of the process1700, i.e., the portion to the right of the right-most vertical line and centered under the heading “Main Server,” partly represents the remote controlled fueling module software application842and partly represents software application(s) in one or more of the modules846-842illustrated inFIG. 14B, all executable by the processor20of the main server12. In one embodiment, this portion of the process1700is illustratively stored in the memory24(and/or data storage26) of the main server12in the form of instructions executable by the processor20of the main server12, and the process steps of this portion of the process1700will be described below for purposes of this disclosure as being executed by the processor20of the main server. It will be understood, however, that in some alternate embodiments that do not include a main server12, this portion of the process1700may be stored in the memory44(and/or data storage46) of one or more of the local servers161-16Kin the form of instructions executable by the processor40of the one or more local servers161-16K.

It will further be understood that portions of the process1700illustrated as being executed by one processor/device or one processor/server may alternatively be executed by a different processor/device or processor/server in the system10, some examples of which are described above.

The process1700begins at step1702in which the customer and fuel dispenser from which the customer desires to dispense fuel are identified by or for the main server12. In the embodiment illustrated inFIG. 17, step1702may include step1704associated with the fuel dispensers181-18N,181-18M, step1705associated with the mobile electronic devices (e.g., mobile communication devices80and/or vehicle communication devices90) and step1706associated with the main server12. In some embodiments, step1702includes all of the steps1704-1706, and in other embodiments step1702may include only steps1705and1706. In any case, execution of step1702illustratively produces at least an identification of the customer-member of the EMS program that seeks to dispense fuel from one of the fuel dispensers181-18N,181-18M, and an identification of the one of the fuel dispensers181-18N,181-18Mfrom which the identified customer-member wishes to dispense fuel. In some embodiments, the identification of the customer-member may be or include an identification of at least the customer's EMSID or communication information (CI), and the processor20of the main server12may then obtain other customer-related information by searching the database802and/or one or more other databases for customer-related information associated therewith, i.e., linked thereto. In other embodiments, the identification of the customer-member may additionally include receipt by the processor20of a security code, e.g., in the form of or as part of the CUSTID code, which the processor20of the main server12then subsequently validates or authenticates in order to gain access to the customer-member's stored EPS/EPI data for the purpose of authorizing, and then subsequently processing, the customer's stored EPI in payment for fuel to be dispensed by the customer-member from the identified fuel dispenser181-18N,181-18M.

Referring now toFIG. 18, a simplified flow diagram is shown of one embodiment of a process1800for executing the process step1702illustrated inFIG. 17in which the customer and fuel dispenser181-18N,181-18Mfrom which the customer desires to dispense fuel are identified based, at least in part, on detection and processing of wireless signals broadcast by one or more wireless signal broadcasting devices, e.g., beacons,224located in, on, at or near each of the fuel dispensers181-18N,181-18M. In the embodiment illustrated inFIG. 18, such customer and fuel dispenser identification illustratively occurs automatically, i.e., without intervention or input required by the customer. In the illustrated embodiment, the process1800is illustratively executed in part by the processor20of the main server12and in part by the processor300,400of the customer's mobile electronic device, and in this regard part of the process1800is illustratively stored in the memory24(and/or data storage26) of the main server12in the form of instructions executable by the processor20of the main server12, and part is illustratively stored in the memory304(and/or data storage306) of the customer's mobile communication device80in the form of instructions executable by the processor300of the customer's mobile communication device80or in the memory404(and/or data storage406) of the customer's vehicle communication device90in the form of instructions executable by the processor400of the customer's vehicle communication device90. It will be understood, however, that in some alternate embodiments the part of the process1800just described as being stored in the main server12and executed by the processor20may be alternatively stored, in whole or in part, in the memory44(and/or data storage46) of the one or more of the local servers161-16Kin the form of instructions executable, in whole or in part, by the processor40of one or more of the local servers161-16K, or stored, in whole or in part, in the memory64(and/or data storage66) of the one or more of the fuel dispensers181-18N,181-18Min the form of instructions executable, in whole or in part, by the processor60of one or more of the one or more of the fuel dispensers181-18N,181-18M. In any such embodiments, this portion of the process1800may be executed in whole or in part by one or more processors within any one or a combination of the main server12, any of the one or more local servers161-16Kand any of the one or more of the fuel dispensers181-18N,181-18M, wherein information may be shared between the such systems via wired and/or wireless connection.

The process1800illustratively begins at step1802where each of the beacons224associated with, i.e., positioned at, near, in, on or part of, a corresponding one of the various fuel dispensers181-18N,181-18Mperiodically and continually broadcast one or more unique wireless identification signals, i.e., identification signals that distinguish that particular beacon224from beacons224associated with other co-located fuel dispensers181-18N,181-18M, e.g., other fuel dispensers18located at the same fuel center52, and illustratively also from one or more beacons710associated with the fuel center52. In some embodiments, the unique signals broadcast by each beacon224further distinguishes that beacon224from other beacons224located at other fuel centers521-52Kcontrolled by the retail enterprise. In some embodiments, one or more of the beacons224may broadcast the unique wireless identification signals non-periodically, and/or may broadcast unique wireless identification signals non-continually but rather only upon detection of a nearby customer electronic device, e.g., via detection by the communication circuitry68of the corresponding fuel dispenser18of one or more short-range wireless signals produced by the customer electronic device, via proximity detection of the customer and/or vehicle76using a suitable proximity sensor included in the sensors428of the corresponding fuel dispenser18, or the like. In any case, at some point while the beacon(s)224is/are broadcasting the one or more unique wireless signals, the customer, carrying the customer's the mobile communication device80or approaching in a vehicle carrying the vehicle communication device90, approaches one of the fuel dispensers181-18N,181-18Mfor the purpose of commencing a fuel purchase transaction. This scenario is depicted inFIG. 19which illustrates one such beacon224, mounted to, in, on or near the fuel dispenser18, periodically broadcasting unique wireless signals which are represented inFIG. 19by the semi-circular dashed lines emanating outwardly from the beacon224.

The fuel dispenser18is communicatively coupled to the main server12via the private network14and, in the illustrated embodiment, via one of the local hub servers16. In the embodiment illustrated inFIG. 19, the fuel dispenser18and the fuel center52at which the local hub server16is illustratively located are those at which the current fuel purchase transaction is to be conducted. The customer's mobile electronic device80,90and the main server12are each illustratively configured to communicate wirelessly with each other via the public network1202. In some embodiments, one or more of the fuel centers521-52Kmay illustratively implement one or more local or wide area networks for the purpose of providing or enhancing communication access by mobile electronic devices80,90to the public network1202in and around the vicinity of the fuel centers521-52K. In any case, as the customer's mobile electronic device80,90approaches the fuel dispenser18the customer's mobile electronic device80,90enters the broadcast range of the beacon222as depicted inFIG. 19. When within the broadcast range of the beacon224, the mobile electronic device80,90is able to detect the unique identification signals being periodically (or non-periodically) broadcast by the beacon224. Illustratively, the broadcast range of the beacon is sufficiently large, wide and/or oriented to be detected by customers' mobile electronic devices80,90during the normal approach to the fuel dispenser18by vehicle76and/or by foot, while is at the same time sufficiently small, narrow and/or oriented so as not to be detected by mobile electronic devices80,90of customers being processed by one or more adjacent fuel dispensers181-18N,181-18M.

Referring again toFIG. 18, the customer's mobile electronic device80,90is operable at step1804to detect the unique identification signals wirelessly broadcast by the beacon224associated with one of the fuel dispensers181-18N,181-18Mwhen the customer's mobile electronic device80,90is within the broadcast range of the beacon224as illustrated by example inFIG. 19. Thereafter at step1806, the processor300,400of the customer's mobile electronic device80,90is illustratively responsive to such detection of the unique identification signals broadcast by the beacon224to wake up and activate the customer/fuel dispenser identification module530,630stored in the memory304,404or data storage306,406of the mobile electronic device80,90(or stored in off-board storage that is accessible to the mobile electronic device80,90). For the remainder of the process1800, the processor300,400of the customer's mobile electronic device80,90is operable to execute the device's80,90portion of the process1800according to the software application contained in the customer/fuel dispenser identification module530,630, i.e., the processor300,400of the customer's mobile electronic device80,90is operable to execute the instructions contained in the customer/fuel dispenser identification module530,630to execute the remainder of the process1800.

Following step1806, the process1800advances, in one embodiment of the process1800, to step1808where the processor300,400of the customer's mobile electronic device80,90is operable to transmit one or more wireless signals to the main server12, e.g., to control the communication circuitry in the device80,90to wirelessly transmit one or more signals to the main server12via the public network1202as illustrated inFIG. 19. The one or more wireless signals contain(s) the unique identification (UID) of the beacon224that wirelessly broadcast the signals detected by the mobile electronic device80,90, and also illustratively contain(s) an identification of the customer's mobile electronic device80,90. The identification of the customer's mobile electronic device80,90may be, for example, the communication information (CI), e.g., cellular telephone number and/or other communication identifier, which identifies the customer's mobile electronic device80,90to the main server12for the purpose of communicating information from the main server12back to the customer's mobile electronic device80,90. In one embodiment, the processor300,400of the customer's mobile electronic device80,90is operable at step1808to process one or more of the unique identification signals wirelessly broadcast, e.g., periodically, by the beacon224and detected by the customer's mobile electronic device80,90to determine therefrom the UID of the beacon224and to include the UID of the beacon224in the one or more wireless signals transmitted by the mobile electronic device80,90to the main server at step1808. In other embodiments, the processor30,400is operable at step1808to process one or more of the unique identification signals wirelessly broadcast, e.g., periodically, by the beacon224and detected by the customer's mobile electronic device80,90to include in the UID transmitted by the mobile electronic device80,90to the main server at step1808only the raw signal content of one or more of the unique identification signals broadcast by the beacon224. In such embodiments, the processor20of the main server12may be operable to thereafter process the raw signal content transmitted thereto by the customer's mobile electronic device80,90to determine therefrom the UID of the beacon224.

Following step1808, the main server12is operable at step1810to receive the one or more wireless signals transmitted by the customer's mobile electronic device80,90at step1808, and the processor20is operable at step1810to process the UID contained therein to determine the corresponding one of the fuel dispensers181-18N,181-18Mwith which the beacon224detected by the customer's mobile electronic device80,90is associated, i.e., at which the beacon224is located. As described briefly above with respect toFIG. 14A, the fuel center/dispenser location data816in the database802′ of the main server12illustratively has stored therein the beacon identity information for each beacon224in the retail enterprise as well as additional information from which the processor20can determine and identify, for each beacon224located at one of the fuel dispensers181-18N,181-18M, the particular fuel dispenser181-18N,181-18Mat which each such beacon224is located. In one embodiment, for example, the beacon identity information is or includes the UIDs for each beacon224located at one of the fuel dispensers181-18N,181-18M, and each such UID includes or is associated with, e.g., linked to, mapped to, or otherwise identified with, a fuel dispenser identifier (FDID), e.g., in the form of a designation number or code, which identifies the corresponding one of the fuel dispensers181-18N,181-18Mat which the beacon224is located. In such embodiments, the processor20is illustratively operable at step1810to process the UID by searching for a matching UID stored in the fuel center/dispenser location data816and determining the FDID associated in the database816with the matched UID to determine the identity of the corresponding one of the fuel dispenser181-18N,181-18Mto which the detected beacon224is mounted to, in, on or near.

In other embodiments, the UID of each beacon224located at one of the fuel dispensers181-18N,181-18Mis associated in the database816with a unique beacon location (UBL). In such embodiments, the unique beacon locations, UBL, are stored in the database816and associated in the database816with, e.g., linked to, mapped to or otherwise identified with, the UID of a corresponding beacon224. In one embodiment, the unique beacon locations, UBL, may illustratively include, or be mapped to, location coordinates relative to one or more sets of base coordinates of a corresponding one of the fuel centers521-52Kof the retail enterprise. In such embodiments, the locations of each of the fuel dispensers181-18N,181-18Mof the retail enterprise may likewise be stored in the database816also in the form of location coordinates relative to the one or more sets of base coordinates of the corresponding fuel centers521-52K. In such embodiments, the processor20is illustratively operable at step1810to process the UID by searching for a matching UID stored in the database816and comparing the location coordinates associated with the matched UID with those of the fuel dispensers181-18N,181-18Mstored in the database816to determine the identity of the corresponding one of the fuel dispensers181-18N,181-18Mto which the detected beacon224is mounted to, in, on or near.

In either of the foregoing embodiments, the UID contained in the wireless signals broadcast by the beacons224may further include a beacon type (BT), and the beacon identity information stored in the database816may likewise include, or be mapped to, corresponding beacon type information. Illustratively, the beacon identity information of the various beacons224stored in the database816may, in such embodiments, be stored according to beacon type, e.g., such that the beacon identity information stored in the database816is or can be categorized by beacon type. The beacon type may illustratively be or include an indicator of the general location or use of the beacon224, and example beacon types may include, but should not be limited to, fuel dispenser beacons, fuel center beacons, point-of-sale beacons, brick-and-mortar location entrance beacons, beacons associated with specific departments or product category locations within the retail enterprise, general store location beacons, or the like. In such embodiments, the processor20is illustratively operable at step1810to process the UID received from the customer's mobile electronic device80,90by first determining the beacon type, BT, of the beacon224detected by the customer's mobile electronic device80,90, e.g., from the BT included in or appended to the UID received from the customer's mobile electronic device80,90, then searching for a matching UID stored in the database816only among the stored beacon identity information having beacon types that match BT, and then proceeding as described above with respect to a matched UID. Those skilled in the art will recognize additional or alternative information that may be included in, with and/or appended to the UID, and/or additional or alternative information about the retail location and the infrastructure of its various fuel centers521-52Kthat may be collected and stored or otherwise be made accessible to the main server12, which the processor20of the main server12may be configured and operable to process at step1810to determine the identity and/or location of fuel dispensers detected by and identified to the main server12by the customer's mobile electronic device80,90. It will be understood that any such additional or alternate forms of information are contemplated by this disclosure.

Further at step1810, the processor20of the main server is operable to process the communication information included in or with the wireless signal(s) transmitted by the customer's mobile electronic device80,90at step1808to determine the identity of the customer's mobile electronic device80,90for purposes of wirelessly transmitting information thereto, e.g., via the public network1202.

Following step1810, the processor20of the main server12is operable at step1812to determine whether a matching UID was found, e.g., in the database816, at step1810. Generally, if the processor20is unable to locate a matching UID at step1810, this means that the beacon224detected by the customer's mobile electronic device80,90is not associated with any of the fuel dispensers181-18N,181-18Mof the retail enterprise, i.e., is not a fuel dispenser beacon224, or that there were one or more errors in receiving, processing and/or transmitting one or more wireless signals by the customer's181-18N,181-18M, the main server12and/or the network1202. It will be understood that the process1800may be modified to include one or more conventional diagnostic processes for processing and addressing any such one or more errors, including for example re-executing one or more of the steps1802-1810, and that any such modifications are contemplated by this disclosure. Those skilled in the art will recognize that any such modifications to the process1800would be a mechanical step for a skilled software programmer. If the processor20determines at step1812that the beacon224detected by the customer's mobile electronic device80,90is not associated with any of the fuel dispensers181-18N,181-18Mof the retail enterprise, the process1800follows the NO branch of step1812and terminates without returning any information which would allow the process1700illustrated inFIG. 17to execute its remaining steps.

If, at step1812, the processor20of the main server12determines that the beacon224detected by the customer's mobile electronic device80,90is associated with an identified one of the fuel dispensers181-18N,181-18Mof the retail enterprise, the process1800advances to step1814where the processor20of the main server12is operable to transmit a CUSTID request signal back to the customer's mobile electronic device80,90, i.e., back to a communication recipient address, number or code of the customer's mobile electronic device80,90identified by the processor20based on the communication code included in or with the wireless signal(s) transmitted by the customer's mobile electronic device80,90at step1808. Illustratively, the CUSTID request signal is or contains a request or instruction by the processor20to the customer's mobile electronic device80,90to transmit the CUSTID code stored therein or accessible thereto, e.g., created according to the process1600and/or1650illustrated and described with respect toFIGS. 16A and 16Brespectively. At step1816, the customer's mobile electronic device80,90receives the CUSTID request signal, and thereafter at step1818the processor300,400of the customer's mobile electronic device80,90is operable to access the CUSTID code stored therein or otherwise accessible thereto, and to transmit the CUSTID code to the main server12.

In some embodiments, the process steps1808-1818just described may be replaced by step1820, as shown in dashed outline, to which the process1800advances following execution of step1806(in which the processor300,400of the mobile electronic device80,90has awoken and activated the customer/fuel dispenser identification module530,630in response to detection of one or more unique identification signals broadcast by the beacon224). In some such embodiments, the memory304,404and/or data storage306,404of the customer's mobile electronic device80,90illustratively has beacon information stored therein, as part of the customer/fuel dispenser identification module530,630, which relates to some or each of the various beacons in or at one or more of the fuel centers521-52Kof the retail enterprise. In one embodiment in which the UID includes or has appended thereto a beacon type, BT, the beacon information stored in the customer's mobile electronic device80,90illustratively is or includes beacon type information which identifies different beacon types, e.g., fuel dispenser beacons, fuel center beacons, etc. as described above. In such embodiments, the processor300,400is operable at step1822to process the unique identification signals broadcast by the beacon224to determine the UID of the beacon224, to then process the UID to determine the beacon type, BT, of the beacon224, and to then compare BT to the stored beacon information to determine whether the beacon224is a fuel dispenser beacon. If so, the processor300,400is operable at step1824to access the CUSTID code stored therein or otherwise accessible thereto, and to then transmit the CUSTID code and the UID of the beacon224to the main server12. Otherwise, the process1800terminates without returning any information which would allow the process1700illustrated inFIG. 17to execute its remaining steps, as shown by the dashed line extending from step1820to DONE inFIG. 18.

In other embodiments that include step1820, the beacon information stored in the customer's mobile electronic device80,90illustratively is or includes information that links, maps or otherwise associates beacon UIDs of at least the beacons224at some or all of the fuel centers521-52Kof the retail enterprise to identifiers of the fuel dispensers181-18N,181-18Mat which they are located, e.g., FDIDs. In such embodiments, the processor300,400is operable at step1822to process the unique identification signals broadcast by the beacon224to determine the UID of the beacon224, and to then compare the UID to the stored beacon information to identify the FDID of the particular one of the fuel dispensers181-18N,181-18Mat which the beacon224is located. If the comparison made by the processor300,400at step1822produces a valid FDID, the processor300,400is thereafter operable at step1824to access the CUSTID code stored therein or otherwise accessible thereto, and to then transmit the CUSTID code along with the FDID to the main server12. If the comparison made by the processor300,400at step1822does not produce a FDID, or in some embodiments a valid FDID, the process300,400terminates without returning any information which would allow the process1700illustrated inFIG. 17to execute its remaining steps, as shown by the dashed line extending from step1820to DONE inFIG. 18.

In still other embodiments that include step1820, the beacon information acted upon by the processor300,400of the customer's mobile electronic device80,90at step1822is not stored in the memory304,404and/or data storage306,404, but is rather stored elsewhere or transmitted to or otherwise made accessible to the customer's mobile electronic device80,90by the main server12according to a fuel center identification process that is triggered by activation of the software application in the customer/fuel dispenser identification module530,630in response to detection of one or more unique identification signals broadcast by the beacon224at step1804. In such embodiments, the fuel center identification process is illustratively an interactive process between the processor300,400of the customer's mobile electronic device80,90and the processor20of the main server in which the processor300,400of the customer's mobile electronic device80,90is operable upon activation of the software application stored in the customer/fuel dispenser identification module530,630to transmit a location identification signal to the main server12indicative of a current location of the customer's mobile electronic device80,90. In one embodiment, the location signal includes the current or most recent GPS coordinates of the customer's mobile electronic device80,90, and the processor20of the main server12is operable to identify the specific one of the fuel centers521-52Kof the retail enterprise at which the customer's mobile electronic device80,90is currently located, e.g., by comparing such coordinates to known coordinates of the various fuel centers521-52Kof the retail enterprise that are stored in the database816or other database. In other embodiments, the location signal transmitted by the customer's mobile electronic device80,90may not include any specific information relating to the coordinates of the customer's mobile electronic device80,90, but may rather include information relating to the identity of the LAN or WAN implemented in the particular fuel center521-52Kat which the customer's mobile electronic device80,90is currently located and which is used by the customer's mobile electronic device80,90to access the public network1202in order to transmit the signal. In such embodiments, the processor20of the main server12may be operable to process the location signal to determine the specific one of the fuel centers521-52Kof the retail enterprise at which the customer's mobile electronic device80,90is currently located, e.g., by comparing the information in or carried by the location signal relating to the LAN or WAN used by the customer's mobile electronic device80,90to access the network1202with known LAN or WAN information stored in the database816or other database to determine the fuel center521-52Kat which the transmitting LAN or WAN is located. In any case, following identification of the specific fuel center521-52Kat which the customer's mobile electronic device80,90is currently located, the processor20of the main server12is operable in one embodiment to transmit to the customer's mobile electronic device80,90the beacon information relating only to the beacons at the identified fuel center521-52K. In other embodiments, the processor20of the main server12is operable to provide access by the processor300,400of the customer's mobile electronic device80,90to such beacon information stored in the database816(or other database) so that the processor300,400may thereafter process such beacon information as described above.

In any case, the process1800advances from step1818, in embodiments that include steps1808-1818, or from step1824in embodiments that include step1820, to step1826where the processor20of the main server12is operable to receive the CUSTID code transmitted by the customer's mobile electronic device80,90. In some embodiments that include step1820, the CUSTID code transmitted by the customer's mobile electronic device80,90may be accompanied by the UID of the beacon224and in other such embodiments the CUSTID code may be accompanied by the FDID of the particular one of the fuel dispensers181-18N,181-18Mat which the beacon224is located. In the former case, the processor20of the main server12is further operable at step1826to process the UID of the beacon224to determine the FDID of the particular one of the fuel dispensers181-18N,181-18Mat which the beacon224is located, as described hereinabove with respect to step1810.

Following step1826, the processor20of the main server12is operable at step1828to determine whether the CUSTID code transmitted to the main server12by the customer's mobile electronic device80,90matches a CUSTID code stored in one or more databases, i.e., whether the CUSTID code matches a corresponding CUSTID code of one of the customer-members of the EMS program. The processor20is illustratively operable to execute step1828of the process1800by searching for the CUSTID code in the EMS customer account data804in embodiments in which the CUSTID codes are stored in the EMS customer accounts data804, or in one or more other databases in which CUSTID codes are stored. If a matching CUSTID code is found at step1828, the process1800advances to step1830where the processor20is operable to identify, in the database402or other database, one or more codes or other information that is associated with, e.g., stored with, mapped to or linked to, the matching CUSTID code in the database802or other database which the processor20may then use to process a transaction for the purchase of fuel to be dispensed from the identified fuel dispenser18according to the fuel purchase preferences established by the corresponding customer member of the EMS program (e.g., according to a process such as the process1500illustrated inFIG. 15). In one embodiment, the processor20is operable at step1830to identify the enterprise membership identification, EMSID, as the code associated with the matching CUSTID code, which thus identifies the EMS account of the customer member associated with the mobile electronic device80,90. In other embodiments, the processor20may be operable at step1830to identify one or more other codes or other information associated in the database802or other database with the matching CUSTID code, and in such embodiments the processor20may use such one or more other codes or other information to identify the EMS account of the customer member and/or to identify specific information associated with the EMS account, e.g., the authorized EPS, etc. In some embodiments, the CUSTID code or some portion thereof may be or include the code identified at step1830, and in such embodiments the processor20need not search the database802or other database to determine the identified code. In any case, following step1830, the process1800is complete and the process step1702illustrated inFIG. 17returns the identity of the customer associated with the CUSTID code transmitted to the main server12by the customer's mobile electronic device80,90, e.g., the EMSID of the customer associated with the mobile electronic device80,90, and also returns the identity of the fuel dispenser181-18N,181-18Mat which the beacon224is located which broadcast the wireless signals detected by the customer's mobile electronic device80,90at step1804of the process1800. If, at step1828, the processor20determines that none of the one or more databases in which CUSTID codes are stored has stored therein a CUSTID code that matches the CUSTID code transmitted to the main server12by the customer's mobile electronic device80,90, the process1800terminates without returning any information which would allow the process1700illustrated inFIG. 17to execute its remaining steps, as shown by the arrowed line extending from step1828to DONE inFIG. 18.

It will be understood that the CUSTID code described above with respect to the process1800may be or include one or more combined or separate codes as briefly described above. It will be further understood that while the process1800has been described in the context of transmitting, receiving and searching one or more databases for a CUSTID code, nothing in this disclosure is intended to limit such a CUSTID code to a single sequence of bits or characters. In some embodiments, for example, the CUSTID code may be implemented as a single sequence of bits or characters, while in other embodiments the CUSTID code may be implemented in the form of two or more separate, and in some cases separately transmitted and received, sequences of bits or characters. As one specific example of the latter implementation, which should not be considered limiting in any way, the CUSTID code may include a first CUSTID code in the form of, e.g., the customer's EMSID or coded version thereof, and a second CUSTID code in the form of, e.g., a random or otherwise generated security code, which is separate and distinct from the first CUSTID code and which is transmitted and received separately from the first CUSTID code.

In some embodiments, the customer's mobile electronic device80,90may be operable to transmit such multiple CUSTID codes, or to transmit a single CUSTID code in multiple wireless signal transmissions, without interruption by or data requests by the processor20of the main server12. In some alternative embodiments, the customer's mobile electronic device80,90may be operable to transmit such multiple CUSTID codes, or to transmit a single CUSTID code in multiple wireless signal transmissions, by executing one or more of the multiple signal transmissions in response to one or more requests transmitted by the processor20to the customer's mobile electronic device80,90. In other alternative embodiments, the customer's mobile electronic device80,90may be operable to transmit such multiple CUSTID codes, or to transmit a single CUSTID code in multiple wireless signal transmissions, by executing one or more of the multiple signal transmissions in response to one or more acknowledgements transmitted by the processor20to the customer's mobile electronic device80,90of one or more data transmission notifications previously transmitted by the customer's mobile electronic device80,90.

In any case, it will be further understood that in embodiments in which the CUSTID code, whether in the form of a single transmitted/received signal or multiple, separate transmitted/received signals, includes two or more codes, the processor20will be operable at step1828to determine whether the CUSTID code transmitted to the main server12by the customer's mobile electronic device80,90matches a CUSTID code stored in one or more databases by comparing each such transmitted/received code with codes stored in the database802or other database, and that a determination by the processor20that the CUSTID code matches a CUSTID code stored in one or more databases requires a match for each code contained in the CUSTID code. As an example in which the CUSTID code includes an EMSID and a security code, a determination by the processor20at step1828that the CUSTID code transmitted to the main server12by the customer's mobile electronic device80,90matches a CUSTID code stored in one or more databases will require a match between the transmitted EMSID and one of the plurality of EMSIDs stored in one or more databases as well as a match between the transmitted security code and a corresponding security code stored in the one or more databases and associated in the one or more databases with the matching EMSID.

Referring now toFIG. 20, a simplified flow diagram is shown of another embodiment of a process2000for executing the process step1702illustrated inFIG. 17in which the customer and fuel dispenser181-18N,181-18Mfrom which the customer desires to dispense fuel are identified via wireless signals transmitted to the main server12by the customer's mobile electronic device80,90. In some embodiments of the process2000, such as that illustrated inFIG. 20, such customer and fuel dispenser identification illustratively requires the customer to provide, e.g., to manually enter, information that identifies the fuel dispenser181-18N,181-18Mfrom which the customer desires to dispense fuel. In the illustrated embodiment, the process2000is illustratively executed in part by the processor20of the main server12and in part by the processor300,400of the customer's mobile electronic device, and in this regard part of the process2000is illustratively stored in the memory24(and/or data storage26) of the main server12in the form of instructions executable by the processor20of the main server12, and part is illustratively stored in the memory304(and/or data storage306) of the customer's mobile communication device80in the form of instructions executable by the processor300of the customer's mobile communication device80or in the memory404(and/or data storage406) of the customer's vehicle communication device90in the form of instructions executable by the processor400of the customer's vehicle communication device90. It will be understood, however, that in some alternate embodiments the part of the process2000just described as being stored in the main server12and executed by the processor20may be alternatively stored, in whole or in part, in the memory44(and/or data storage46) of the one or more of the local servers161-16Kin the form of instructions executable, in whole or in part, by the processor40of one or more of the local servers161-16K, or stored, in whole or in part, in the memory64(and/or data storage66) of the one or more of the fuel dispensers181-18N,181-18Min the form of instructions executable, in whole or in part, by the processor60of one or more of the one or more of the fuel dispensers181-18N,181-18M. In any such embodiments, this portion of the process2000may be executed in whole or in part by one or more processors within any one or a combination of the main server12, any of the one or more local servers161-16Kand any of the one or more of the fuel dispensers181-18N,181-18M, wherein information may be shared between the such systems via wired and/or wireless connection.

The process2000is illustratively stored in the form of a software application in the customer/fuel dispenser identification module522,622, and illustratively begins at step2002when the customer launches, i.e., activates, the fuel dispenser activation application stored in the fuel dispenser activation module502,602(seeFIGS. 5 and 6). In some embodiments of the fuel dispenser activation application, the processor300,400of the customer's mobile electronic device80,90illustratively accesses the process2000contained in the customer/fuel dispenser identification module522,622upon launch (step2002), and in such embodiments the processor300,400is operable (following step2002) at step2004to control the display320,422of the of the customer's mobile electronic device80,90to display a graphic user interface (GUI) which includes at least one fuel dispenser identification field and prompts the customer to enter an identification code (IC) which uniquely identifies the fuel dispenser181-18N,181-18Mfrom which the customer desires to dispense fuel. In some embodiments, IC may be or include the fuel dispenser ID200illustrated and described with respect toFIG. 2, and in such embodiments the fuel dispenser ID200included and displayed on each of the fuel dispensers181-18N,181-18Mis different from the fuel dispenser ID200displayed on any other fuel dispenser181-18N,181-18Mand therefore uniquely identifies each one of the fuel dispensers181-18N,181-18M. Alternatively or additionally, the identification code, IC, may be or include the IDCODE generated by the module64as described hereinabove with respect toFIG. 2, wherein the IDCODE displayed on the display monitor214of each fuel dispenser181-18N,181-18Muniquely identifies that fuel dispenser181-18N,181-18M. Alternatively or additionally still, the identification code, IC, may be or include the fuel center ID700displayed at or on each of the fuel center521-52K, and in such embodiments the fuel center ID700included and displayed on each of the fuel centers521-52Kis different from the fuel center ID700displayed on any other fuel center521-52Kand therefore uniquely identifies each one of the fuel centers521-52K. Those skilled in the art will recognize other techniques for displaying one or more fuel dispenser identifiers in view of a customer approaching a fuel dispenser181-18N,181-18M, and any such other techniques are contemplated by this disclosure. In any case, in response to customer entry of the identification code, IC, which uniquely identifies the fuel pump181-18N,181-18Mfrom which the customer desires to dispense fuel, the processor300,400is operable, following step2004, at step2006to control the communication circuitry310,410to wirelessly transmit information to the main server, wherein such information illustratively includes the CUSTID code described hereinabove and the identification code, IC, of the fuel dispenser181-18N,181-18Mfrom which the customer desires to dispense fuel to the main server12.

As described hereinabove with respect toFIGS. 16A, 16B and 18, the CUSTID code may include one or more sequences of codes and/or include multiple, separate codes. Moreover, the CUSTID code may be wirelessly transmitted by the customer's mobile electronic device80,90in the form of a single transmission of a single signal code or a single transmission of multiple, separate codes, or in the form of two or more separate transmissions of one or more separate codes. In embodiments in which the CUSTID code is transmitted in the form of multiple, separate transmissions, the customer's mobile electronic device80,90may be operable to transmit such multiple CUSTID codes, or to transmit a single CUSTID code in multiple wireless signal transmissions, without interruption by or data requests by the processor20of the main server12. In some alternative embodiments, the customer's mobile electronic device80,90may be operable to transmit such multiple CUSTID codes, or to transmit a single CUSTID code in multiple wireless signal transmissions, by executing one or more of the multiple signal transmissions in response to one or more requests transmitted by the processor20to the customer's mobile electronic device80,90. In other alternative embodiments, the customer's mobile electronic device80,90may be operable to transmit such multiple CUSTID codes, or to transmit a single CUSTID code in multiple wireless signal transmissions, by executing one or more of the multiple signal transmissions in response to one or more acknowledgements transmitted by the processor20to the customer's mobile electronic device80,90of one or more data transmission notifications previously transmitted by the customer's mobile electronic device80,90.

In the process2000, the processor20of the main server12is illustratively operable to execute the software application stored in the fuel dispenser ID module850, and at step2008the processor20is operable to receive the information transmitted thereto by the customer's mobile electronic device80,90. Thereafter at step2010, the processor20of the main server12is operable to determine whether the CUSTID code transmitted to the main server12by the customer's mobile electronic device80,90matches a CUSTID code stored in one or more databases, i.e., whether the CUSTID code matches a corresponding CUSTID code of one of the customer-members of the EMS program. Illustratively, the processor20is operable to execute step2010as described above with respect to steps1828-1830of the process1800illustrated inFIG. 18.

Following execution of step2010, the process2000advances to step2012where the processor20of the main server12is operable to determine whether the identification code, IC, transmitted to the main server12by the customer's mobile electronic device80,90matches a fuel dispenser identification code stored in the fuel center/dispenser location database816or other database. As briefly described above with respect toFIG. 14B, the fuel dispenser ID module850is illustratively included in embodiments in which the fuel dispenser ID200and/or the fuel dispenser identifier IDCODE and/or fuel center ID700is/are used to locate fuel dispensers181-18N,181-18Mat which EMS member-customers are located and from which such customer-members desire to dispense fuel. In such embodiments, the fuel center/dispenser location database816illustratively contains information associating identification codes, IC, e.g., in the form of one or any combination of the fuel dispenser IDs200and/or IDCODEs and/or fuel center IDs700, with corresponding ones of the fuel dispensers181-18N,181-18M. In one embodiment, for example, the identification code, IC, of each fuel dispenser181-18N,181-18Mis associated with, e.g., linked to, mapped to, or otherwise identified with, a fuel dispenser identifier (FDID), e.g., in the form of a designation number, address or code, which identifies the corresponding one of the fuel dispensers181-18N,181-18Mto the main server12so that the processor20of the main server12can control operation of thereof in accordance with the customer's pre-established fueling preferences, e.g., via the process1500illustrated inFIG. 15. In such embodiments, the processor20is illustratively operable at step1810to process IC by searching for a matching IC stored in the fuel center/dispenser location data816and determining the FDID associated in the database816with the matched IC to determine the identity of the corresponding one of the fuel dispenser181-18N,181-18Mfrom which the customer identified by CUSTID code desires to dispense fuel.

In other embodiments, the identification codes, IC, may be stored in the database816and associated in the database816with, e.g., linked to, mapped to or otherwise identified with, location coordinates, relative to one or more sets of base coordinates, corresponding to the locations of each of the fuel dispensers181-18N,181-18M of the retail enterprise. In such embodiments, the processor20is illustratively operable at step1810to process IC by searching for a matching IC stored in the database816and comparing the location coordinates associated with the matched IC with those of the fuel dispensers181-18N,181-18Mstored in the database816to determine the identity of the corresponding one of the fuel dispenser181-18N,181-18Mfrom which the customer identified by CUSTID code desires to dispense fuel.

In any case, following step2012, the process2000is complete and the process step1702illustrated inFIG. 17returns the identity of the customer associated with the CUSTID code transmitted to the main server12by the customer's mobile electronic device80,90, e.g., the EMSID of the customer associated with the mobile electronic device80,90, and also returns the identity of the fuel dispenser181-18N,181-18Mfrom which the identified customer wishes to dispense fuel. If, at step2010, the processor20determines that none of the one or more databases in which CUSTID codes are stored has stored therein a CUSTID code that matches the CUSTID code transmitted to the main server12by the customer's mobile electronic device80,90, the process2000may illustratively terminate without returning any information which would allow the process1700illustrated inFIG. 17to execute its remaining steps, as described above with respect to step1828of the process1800ofFIG. 18.

In some alternative embodiments of the process2000, the customer and fuel dispenser identification process just described may be modified such that more or all of the process200occurs automatically, i.e., without intervention or input required by the customer. In such embodiments, each fuel dispenser181-18N,181-18Mmay further illustratively be operable to periodically or non-periodically broadcast or otherwise transmit, e.g., via the wireless communication circuitry230and/or other wireless signal broadcasting device such as a beacon224, the identification code, IC, corresponding thereto. In such embodiments, the customer's mobile electronic device80,90may be responsive to such wirelessly broadcast signals to wake up and activate the fuel dispenser activation application stored in the fuel dispenser activation module502,602as described above with respect toFIG. 18and to wireless transmit the CUSTID code and IC to the main server12as described above with respect to the process2000illustrated inFIG. 20. Alternatively, the modified process may include step2002as described above such that the customer manually launches the fuel dispenser activation application prior to or after arriving at the fuel center521-52K. In such alternative embodiments, the fuel dispenser activation application may be responsive to such manual activation thereof to monitor for wireless signals broadcast by a proximate fuel dispenser18, or to wirelessly transmit one or more signals receivable by the wireless communication circuitry230of the fuel dispenser18that identifies the presence of the customer mobile electronic device80,90proximate to the fuel dispenser18, to which the processor60of the fuel dispenser18may be responsive to control the wireless communication circuitry230and/or one or more beacons224to wirelessly broadcast the identification code, IC. In such embodiments, the processor300,400of the customer's mobile electronic device80,90and the processor20of the main server12may thereafter be operable as described with respect to steps2006-2012above or may alternatively be operable as described with respect to steps1806-1830of the process1800illustrated inFIG. 18.

Referring now toFIG. 21, a simplified flow diagram is shown of another embodiment of a process2100for executing the process step1702illustrated inFIG. 17in which the customer and fuel dispenser181-18N,181-18Mfrom which the customer desires to dispense fuel are identified via GPS information transmitted to the main server12by the customer's mobile electronic device80,90. In some embodiments of the process2100, such as that illustrated inFIG. 21, such customer and fuel dispenser identification illustratively occurs automatically, i.e., without intervention or input required by the customer. In the illustrated embodiment, the process2100is illustratively executed in part by the processor20of the main server12and in part by the processor300,400of the customer's mobile electronic device, and in this regard part of the process2100is illustratively stored in the memory24(and/or data storage26) of the main server12in the form of instructions executable by the processor20of the main server12, and part is illustratively stored in the memory304(and/or data storage306) of the customer's mobile communication device80in the form of instructions executable by the processor300of the customer's mobile communication device80or in the memory404(and/or data storage406) of the customer's vehicle communication device90in the form of instructions executable by the processor400of the customer's vehicle communication device90. It will be understood, however, that in some alternate embodiments the part of the process2100just described as being stored in the main server12and executed by the processor20may be alternatively stored, in whole or in part, in the memory44(and/or data storage46) of the one or more of the local servers161-16Kin the form of instructions executable, in whole or in part, by the processor40of one or more of the local servers161-16K, or stored, in whole or in part, in the memory64(and/or data storage66) of the one or more of the fuel dispensers181-18N,181-18Min the form of instructions executable, in whole or in part, by the processor60of one or more of the one or more of the fuel dispensers181-18N,181-18M. In any such embodiments, this portion of the process2100may be executed in whole or in part by one or more processors within any one or a combination of the main server12, any of the one or more local servers161-16Kand any of the one or more of the fuel dispensers181-18N,181-18M, wherein information may be shared between the such systems via wired and/or wireless connection.

The process2100is illustratively stored in the form of a software application in the customer/fuel dispenser identification module522,622, and illustratively begins at step2102when the fuel dispenser activation application stored in the fuel dispenser activation module502,602(seeFIGS. 5 and 6) is activated, e.g., either manually by the customer or automatically in response to a detected signal as described above with respect to the process2000ofFIG. 20. In some embodiments of the fuel dispenser activation application, the processor300,400of the customer's mobile electronic device80,90illustratively accesses the process2100contained in the customer/fuel dispenser identification module522,622upon launch (step2102), and in such embodiments the processor300,400is operable (following step2102) at step2104to update the current geographical location of the customer's mobile electronic device80,90by receiving from the on-board GPS receiver324,426updated geographical location data in the form of geographical coordinates, e.g., at least latitudinal and longitudinal coordinates. For purposes of this document, such geographical coordinates defining the geographical location or position of the customer's mobile electronic device80,90may be referred to as “GPS coordinates.”

In one embodiment, the processor300,400is operable at2106, following step2104, to compare the updated GPS coordinates to so-called “geofence” data relating to the geographical locations of the fuel center521-52K. In some embodiments, the customer/fuel dispenser identification module522,622and/or fuel dispenser activation module502,602may have access to, either stored in the on-board memory304,404or data storage306,406, or stored in the database816or other database and accessible via the public network1202, “geofence” data identifying the various fuel centers521-52Kand/or identifying one or more of the fuel dispensers18located at the various fuel centers521-52K. In such embodiments, the processor300,400is illustratively operable at step2110to process the GPS coordinates and the geofence data to determine the location of the customer's mobile electronic device80,90relative to one or more geofences defined by the geofence data. In alternative embodiments, the processor300,400may be operable at step2106to instead wirelessly transmit the updated GPS coordinates to the main server12, and the processor20of the main server12may be operable to execute such comparisons and then wirelessly transmit the results of such comparisons back to the customer's mobile electronic device80,90, as shown by the dashed-line process step2108.

For purposes of this disclosure, “geofence” data generally is or includes open or closed-boundary geographical data which defines one or more specific geographical points, areas or regions, and a “geofence” is any single such boundary which defines a specific geographical point, area or region. In this regard, the geofence data stored on-board the customer's mobile electronic device80,90or in the fuel center dispenser location database816or other database illustratively defines a number of different geofences each defining a closed or open border about, or at least partially about, a different one of the fuel centers521-52K. InFIG. 22, for example, one such closed-boundary geofence2200is shown extending about an example fuel center52at which twelve fuel dispensers181-1812are located and positioned as shown. In this example, the geofence2200is illustratively stored in the form of a set of geofence coordinates that include a number of ordered sets of different geographical coordinates, e.g., latitudinal and longitudinal coordinate pairs, which together define the boundary of the geofence2200illustrated inFIG. 22. In this embodiment, the geofence data stored on-board the customer's mobile electronic device80,90or in the fuel center dispenser location database816or other database illustratively includes a set of geofence coordinates for each of the fuel centers521-52K. In some embodiments, the geofence data may further include one or more sets of geofence coordinates each of which define an open or closed boundary about a corresponding one the fuel dispensers, e.g., one of the fuel dispensers181-1812inFIG. 22.

In any case, referring again toFIG. 21, the processor300,400(or the processor20in embodiments which include step2108in place of step2106), is illustratively operable to execute step2110by comparing the updated GPS coordinates received at step2104with all or one or more subsets of the geofence data stored on-board the customer's mobile electronic device80,90or in the database816or other database to determine whether the customer's mobile electronic device80,90is located within any of the geofences defined by the geofence data. In the example illustrated inFIG. 22, the result of such comparison would reveal that the customer's mobile electronic device80,90is located within the geofence2200. If the processor300,400(alternatively the processor20) determines at step2110that the customer's mobile electronic device80,90is not located within any geofence included in the geofence data, the process2100loops back to step2104to acquire updated GPS coordinates. If, on the other hand, the processor300,400(alternatively the processor20) determines at step2110that the customer's mobile electronic device80,90is located within a geofence included in the geofence data, the process2100advances to step2112where the processor300,400is operable to control the wireless communication circuit312,410to wirelessly transmit the CUSTID code and the updated GPS coordinates to the main server12, and the processor20of the main server is thereafter operable at step2114to receive the transmitted CUSTID code and updated GPS coordinates. In embodiments in which the processor20of the main server12is operable to execute such comparisons and determinations, step2112illustratively includes transmission only of the CUSTID code if not previously transmitted by the processor300,400, and otherwise steps2112and2114may be omitted as the processor20will have already received the CUSTID code and the updated GPS coordinates.

In embodiments in which the geofence detected at step2110corresponds to a geofence defined about, or at least partially about, one of the fuel dispensers181-18N,181-18M, the identified geofence along with the updated GPS position of the customer's mobile electronic device80,90, is sufficient for the processor20of the main server12to determine the fuel dispenser ID, FDID, of the corresponding one of the fuel dispenser181-18N,181-18M. Likewise, in embodiments in which the geofence detected at step2110corresponds to a geofence defined about, or at least partially about, one of the fuel centers521-52Kand in which the geographical coordinates of each fuel dispenser181-18Nor181-18Mlocated at the identified one of the fuel centers521-52Kare accessible to the processor20, such information, along with the updated GPS position of the customer's mobile electronic device80,90, is sufficient for the processor20of the main server12to determine the fuel dispenser ID, FDID, of the corresponding one of the fuel dispenser181-18N,181-18M. In such embodiments, step2116of the process2100may illustratively include only step2118as will be discussed below.

In other embodiments in which the geofence detected at step2110corresponds to a geofence defined bout, or at least partially about, one of the fuel centers521-52K, but in which the geographic positions of the fuel dispensers181-18N,181-18Mare not specifically known, the processor20can only estimate an identity of the one of the fuel dispensers181-18N,181-18Mmost proximate to the customer's mobile electronic device80,90and from which the customer desires to dispense fuel. In such embodiments of the process2100, step2116may illustratively include steps2118-2130as shown by dashed-line representation inFIG. 21. In such embodiments, identification of the fuel dispenser18illustratively may require intervention or input by the customer.

Step2116, in embodiments which step2116includes steps2118-2130, illustratively includes a number of steps to be executed in-part by the processor20of the main server12and in-part by the processor300,400of the mobile electronic device80,90. For example, the process step2116illustratively includes step2118at which the processor20of the main server12is operable to estimate the identity of the one of the fuel dispensers181-18Nor181-18Mmost proximate to the customer's mobile electronic device80,90and from which the customer desires to dispense fuel. As briefly described above with respect toFIG. 14B, the fuel center/dispenser locator module852is illustratively included in embodiments in which the GPS position of the customer's mobile electronic device80,90and geofence data are used to locate fuel dispensers181-18N,181-18Mat which EMS member-customers are located and from which such customer-members desire to dispense fuel. In some such embodiments, the fuel center/dispenser location database816illustratively contains information associating geofence data for the various fuel centers521-52Kwith identities of such fuel centers521-52Kand further illustratively contains information uniquely identifying each fuel dispenser18located at each such fuel center52. In one embodiment, for example, the set of geofence coordinates of each fuel center521-52K, or some subset thereof, is associated with, e.g., linked to, mapped to, or otherwise identified with, a fuel center identifier (FCID), e.g., in the form of a designation number or code, which identifies the corresponding one of the fuel centers521-52Kto the main server12. In such embodiments, the processor20is illustratively operable at step2118to estimate the identity of the one of the fuel dispensers181-18N,181-18Mmost proximate to the customer's mobile electronic device80,90and from which the customer desires to dispense fuel by first comparing the updated GPS coordinates to the geofence data for the various fuel centers521-52Kto determine a fuel center identifier FCID of a fuel center52having a set of geofence coordinates that define a geofence within which the customer's mobile electronic device80,90is currently located, and to then determine the one or subset of the fuel dispensers181-18N,181-18Mwhich is/are located at the identified fuel center52. In the example illustrated inFIG. 22, such a determination would yield the identities of each of the fuel dispensers181-1812. Illustratively, the processor20is further operable at step2118to estimate the identity of the one of the fuel dispensers181-18N,181-18Mmost proximate to the customer's mobile electronic device80,90and from which the customer desires to dispense fuel by selecting one of the fuel dispensers located at the identified fuel center52based one or more factors which may include, but which are not limited to, the GPS position of the customer's mobile electronic device80,90relative to the identified geofence, the operational state of each of the fuel dispensers located at the identified fuel center52, and/or other factors. In the example illustrated inFIG. 22, such a determination may, for example, yield fuel dispenser184as the estimated identity of the one of the fuel dispensers181-18N,181-18Mmost proximate to the customer's mobile electronic device80,90and from which the customer desires to dispense fuel.

Following step2118, the process2100advances to step2120where the processor20is operable to wirelessly transmit to the customer's mobile electronic device80,90an identifier, e.g., the ID200, IDCODE or other identifier, of the one of the fuel dispensers18located at the identified fuel center52identified by the processor20as the one of the fuel dispensers most proximate to the customer's mobile electronic device80,90and from which the customer desires to dispense fuel. Thereafter at step2122, the processor300,400receives the identifier and at step2124the processor300,400controls the display320,422of the mobile electronic device80,90to display the identifier and prompt the customer to confirm, CN, at step2128or change, CH, at step2130the identifier based on the identity, e.g., ID200, IDCODE or the like, of the fuel dispenser from which the customer wishes to dispense fuel. In the example illustrated inFIG. 22and described with respect to step2126above, the identity estimate made by the processor20of fuel dispenser184is correct, and in this example the customer would enter or select CN to confirm fuel dispenser184as the fuel dispenser from which the customer wishes to dispense fuel. In any case, the processor300,400is operable at step2128or2130to wirelessly transmit the confirmed or changed identifier to the main server12, and the process2100advances to step2132.

In embodiments of the process2100in which step2116includes steps2118-2130, the processor20is in possession of the fuel dispenser identity, FDID, of the fuel dispenser from which the customer wishes to dispense fuel, e.g., in the form of a code such as the fuel dispenser ID200or IDCODE, following execution of step2128or2130. In other embodiments of the process2100, the geographical coordinates of each fuel dispenser181-18N,181-18Mare illustratively associated with, e.g., linked to, mapped to, or otherwise identified in the fuel center/dispenser location database816with, a fuel dispenser identifier (FDID), e.g., in the form of a designation number, address or code, which identifies the corresponding one of the fuel dispensers181-18N,181-18Mto the main server12so that the processor20of the main server12can control operation of thereof in accordance with the customer's pre-established fueling preferences, e.g., via the process1500illustrated inFIG. 15. In such embodiments, step2116includes only step2118at which the processor20of the main server12is operable to determine the identity of the fuel dispenser from which the customer wishes to dispense fuel by comparing the updated GPS coordinates to the geofence data for the various fuel dispensers181-18N,181-18Mto determine a fuel dispenser identifier FDID of a fuel dispenser18having a set of geofence coordinates that define a geofence within which the customer's mobile electronic device80,90is currently located or relative to which the customer's mobile electronic device80,90is located within a predefined error tolerance. In such embodiments, the process advances from step2118to step2132.

At step2132, the processor20is operable to determine whether the CUSTID code transmitted to the main server12by the customer's mobile electronic device80,90matches a CUSTID code stored in one or more databases, i.e., whether the CUSTID code matches a corresponding CUSTID code of one of the customer-members of the EMS program. Illustratively, the processor20is operable to execute step2132as described above with respect to steps1828-1830of the process1800illustrated inFIG. 18and as described above with respect to step2010of the process20illustrated inFIG. 20.

Again, as described hereinabove with respect toFIGS. 16A, 16B and 18, the CUSTID code may include one or more sequences of codes and/or include multiple, separate codes. Moreover, the CUSTID code may be wirelessly transmitted by the customer's mobile electronic device80,90in the form of a single transmission of a single signal code or a single transmission of multiple, separate codes, or in the form of two or more separate transmissions of one or more separate codes. In embodiments in which the CUSTID code is transmitted in the form of multiple, separate transmissions, the customer's mobile electronic device80,90may be operable to transmit such multiple CUSTID codes, or to transmit a single CUSTID code in multiple wireless signal transmissions, without interruption by or data requests by the processor20of the main server12. In some alternative embodiments, the customer's mobile electronic device80,90may be operable to transmit such multiple CUSTID codes, or to transmit a single CUSTID code in multiple wireless signal transmissions, by executing one or more of the multiple signal transmissions in response to one or more requests transmitted by the processor20to the customer's mobile electronic device80,90. In other alternative embodiments, the customer's mobile electronic device80,90may be operable to transmit such multiple CUSTID codes, or to transmit a single CUSTID code in multiple wireless signal transmissions, by executing one or more of the multiple signal transmissions in response to one or more acknowledgements transmitted by the processor20to the customer's mobile electronic device80,90of one or more data transmission notifications previously transmitted by the customer's mobile electronic device80,90.

In any case, following step2132, the process2100is complete and the process step1702illustrated inFIG. 17returns the identity of the customer associated with the CUSTID code transmitted to the main server12by the customer's mobile electronic device80,90, e.g., the EMSID of the customer associated with the mobile electronic device80,90, and also returns the identity of the fuel dispenser181-18N,181-18Mfrom which the identified customer wishes to dispense fuel. If, at step2132, the processor20determines that none of the one or more databases in which CUSTID codes are stored has stored therein a CUSTID code that matches the CUSTID code transmitted to the main server12by the customer's mobile electronic device80,90, the process2100may illustratively terminate without returning any information which would allow the process1700illustrated inFIG. 17to execute its remaining steps, as described above with respect to step1828of the process1800ofFIG. 18.

Referring again toFIG. 17, the process1700advances from step1702, with the customer identity and with the identity of the one of the fuel dispensers181-18N,181-18Mfrom which the identified customer wishes to dispense fuel, to step1708. At step1708, the processor20is operable to access the electronic payment information (EPI) associated with the customer identity, e.g., EMSID, CI, CUSTID or the like. As the customer identification code, CUSTID, has been verified or authenticated as part of the process1702, such verification or authentication need not be repeated at step1708. In some alternative embodiments, such verification or authentication may be carried out alternatively to or in addition to that carried out at step1702. In any case, the processor20is illustratively operable at step1708to access the EPI associated with the customer identity by accessing the default EPI stored in the customer account data402or other database and identified as such during or following execution of the customer fuel purchase preferences process, e.g., the process1500illustrated inFIG. 15. Thereafter at step1710, the processor20is operable to process the default EPI to determine whether the default EPI is an acceptable electronic funds transfer instrument. In some embodiments, the processor20is operable to execute step1710in its entirety, and in other embodiments the processor20is operable to securely transmit the EPI to a third-party server or system for processing thereof. In either case, the process executed at step1710illustratively includes a conventional electronic funds transfer authorization process by which the customer's default EPI is approved, pre-approved or otherwise authorized for the purpose of enabling one of the fuel dispensers181-18N,181-18Mto dispense fuel after which payment for the dispensed fuel will be charged against, drawn from or otherwise processed using the same electronic funds transfer instrument. In some embodiments, the process1700may illustratively include one or more steps which, if the default EPI is not authorized at step1710, allows the customer to identify and submit an alternate electronic funds transfer instrument, e.g., by selecting an alternate EPI previously entered into the customer's account data804, by entering EPI information for the alternate electronic funds transfer instrument into the customer's mobile electronic device80,90and wirelessly transmitting the same to the processor20, or the like.

The process1700advances from step1710to step1712where the processor20is operable to determine the grade and/or type of fuel to be dispensed from the identified fuel dispenser18. In one embodiment, the processor20is operable execute step1712by accessing the fuel grade/type information (FGT) associated in the customer account data802or other database with the identified customer, e.g., associated with the identified EMSID, CI, CUSTID and/or EPI. In some embodiments, the process1700may advance directly from step1712to step1730to transmit control signals to the identified fuel dispenser18to activate the fuel dispenser18for subsequent dispensation of the selected fuel grade/type FGT. In other embodiments, the process1700may illustratively include a step1714which provides the customer with an opportunity to confirm the default fuel grade/type (i.e., that entered by the customer during the customer fuel purchase preference process, e.g., the process1500ofFIG. 15) or select a different fuel grade/type which the processor20will then subsequently control the identified fuel dispenser18to dispense. In such embodiments, the step1714may illustratively include step1716at which the processor20is operable to wirelessly transmit to the identified customer's mobile electronic device80,90the default fuel grade/type FGT. Thereafter at step1718, the processor300,400of the identified customer's mobile electronic device80,90receives the wirelessly transmitted FGT and at steps1720and1722the processor300,400illustratively controls the display320,422to display the default FGT along with a prompt to confirm, CN, or change, CH, FGT. If, at step1722, the customer elects to confirm the default FGT, the customer does so by selecting CN using the keypad322,424or touchscreen320,422, and if the customer instead elects to change the default FGT, the customer does so by selecting CH using the keypad322,424or touchscreen424and then selecting an alternate fuel type and/or grade from a displayed menu of fuel type and/or grade choices or by entering an alternate fuel type and/or grade into a displayed fuel type/grade field. Thereafter at steps and1726, the processor300,400is operable to wirelessly transmit the fuel grade/type confirmation or change to the main server12, which the processor20of the main server12receives at step1728.

In still other alternate embodiments, the process1700may omit steps1712-1728and instead include one or more alternate steps in which no default FGT exists and the customer is instead prompted to select fuel type and/or grade, e.g., from a menu of fuel types and/or grades. Examples of some such918-932are illustrated inFIG. 9Aand described hereinabove. It will be understood that in any of the foregoing embodiments in which fuel type and/or grade is automatically or manually selected, the process1700may be modified to further include one or more steps for determining whether to offer, and offering, fuel grade upgrades such as illustrated and described with respect to steps918-926B ofFIG. 9A. It will be further understood that in any of the foregoing embodiments, the customer fuel purchase preference process, e.g., the process1500illustrated inFIG. 15, may be modified to further include one or more steps which allow the customer to identify and define fuel purchase preferences for more than one vehicle, such as described above with respect to the process1300illustrated inFIG. 13, and the process1700may likewise be modified to further include one or more steps which allow the customer to identify the customer's vehicle, e.g., from a menu of previously identified vehicle choices, for the purposes of the current or pending fuel purchase, and examples of such steps include steps912-920of the process900illustrated inFIG. 9A.

Referring again toFIG. 17, the process1700advances from either of steps1712and1714to step1730where the processor20of the main server12is operable to process the FGT information to determine the corresponding fuel type and/or grade to be dispensed by the identified fuel dispenser18. Illustratively, the products/service and pricing data812includes data relating to various fuel types and/or grades available to be dispensed from the fuel dispensers181-18N,181-18M, and the processor20is operable to execute step1730by comparing FGT to such data to determine a fuel identification code corresponding to, i.e., associated in the database812with, FGT. Thereafter at step1732, the processor20is operable to transmit one or more control signals to the identified fuel dispenser18and to wirelessly transmit one or at least one message to the mobile electronic device80,90associated with the identified customer. The one or more control signals transmitted by the processor20at step1732illustratively define one or more commands to activate the control section204of the identified fuel dispenser18for subsequent dispensation of a fuel type and/or grade identified by the fuel identification code determined at step1730. The at least one message illustratively includes a message and/or graphic informing the customer that the identified fuel dispenser18is activated and ready to dispense fuel of the fuel type and/or grade FGT.

The identified fuel dispenser18receives the one or more control signals at step1738, and thereafter at step1740the processor60of the identified fuel dispenser is responsive to the one or more control signals to activate the control section204thereof for subsequent dispensation of the fuel type and/or grade specified by the fuel identification code carried by the one or more commands transmitted by the processor20of the main server12. The processor300,400of the mobile electronic device associated with the identified customer receives the at least one message at step1734, and thereafter at step1736the processor300,400is responsive to the at least one message to control the display320,422to display the at least one message.

Upon execution of step1740, the identified fuel dispenser18is activated and ready to dispense fuel with the fuel type and/or grade FGT selected. In some embodiments, the one or more commands transmitted by the processor20at step1732may include a command to disable one or more of the fuel type/grade selectors220,222, and the processor60may be responsive to such one or more commands to disable one or more of the fuel type/grade selectors220,222consistently with the command, as illustrated and described above with respect to step908of the process900, although in other embodiments the processor20may not transmit any such fuel type/grade disable commands and the customer may thus have the option to change selection of the fuel type and/or grade following execution of step1740via a graphic user interface (GUI) displayed on the display320,422of the mobile electronic device80,90associated with the identified customer or via conventional manual manipulation of the fuel selector222and/or fuel grade selectors220.

When fuel dispensation is complete, the process1700illustratively advances to step1742where the processor60of the identified fuel dispenser18is operable to transmit one or more fueling complete signals to the main server12indicating that fuel delivery or dispensation for the current fuel transaction is complete. Illustratively, the sensors206may include a sensor which produces a signal when the fuel dispenser nozzle74is replaced or returned to its support receptacle on the identified fuel dispenser18, and the processor60may be responsive to detection of such a signal to transmit the one or more fueling complete signals. Further illustratively, in response to detection of the sensor signal the processor60or the processor20may disable the control section204of the identified fuel dispenser18so that no more fuel can be dispensed as part of the current fuel purchase transaction. In any case, the one or more fueling complete signals transmitted by the identified fuel dispenser18are received by the main server12at step1744, and thereafter at step1746the processor20of the main server12is operable to determine a total purchase cost for the dispensed fuel and process payment for the fuel purchase, e.g., using the authorized or pre-authorized EPI. The processor20may further be operable at step1746to store a virtual or digital receipt of the fuel purchase transaction in the identified customer-member's purchase history contained in the purchase history database808.

Following step1746, the processor20is operable at steps1748and1754to transmit one or more transaction complete commands and messages respectively to the identified fuel dispenser18and to the mobile electronic device80,90associated with the identified customer-member. At step1750, the processor300,400of the mobile electronic device80,90receives the one or more transaction complete messages, and thereafter at step1752the processor300,400is operable to control the display320,422to display the one or more transaction complete messages. At step1756, the processor60of the identified fuel dispenser18receives the one or more transaction complete commands, and thereafter at step1758the processor60is responsive the one or more transaction complete commands to deactivate the control section204if it is not already deactivated. In embodiments in which the processor20or the processor60disabled one or more of the fuel selectors220,222, the processor60is further responsive to the one or more transaction complete commands to enable all fuel selectors220,222.

Following identification of the identified customer at step1702and at any time during or after dispensation of fuel by the identified fuel dispenser18, the process1700may illustratively be modified to include one or more steps by which the processor20of the main server12may determine whether to offer one or more virtual discount coupons for one or more goods and/or services to the identified customer, if so, what goods and/or services to offer, and to provide such one or more offers to the identified customer. Examples of some such steps922-926B,942, are illustrated and described with respect toFIG. 9A.

Examples of such goods and/or services may include any good and/or service offered by the retail enterprise at a brick-and-mortar location and/or fuel center and/or other good/service store or outlet, including but not limited to food, beverages, clothing, tools, electronics, sporting goods, outdoor items, garden-related items, pharmacy items, fuel, convenience items, car wash, photo services, bakery services, or the like. Whether to offer any such virtual discount coupons may be determined randomly, may be based on the purchase histories of customer-members in the purchase history database808, may be determined to be offered as an incentive to attract new customer-members or re-attract inactive customer members of the EMS program, or the like. The processor20may transmit any such virtual discount coupon directly to the mobile electronic device80,90associated with the identified customer, to the identified fuel dispenser18and/or to the identified customer's EMS page. The transmitted virtual coupon(s) may be displayed by the processor300,400on the display320,422of the mobile electronic device associated with the identified customer and/or displayed by the processor60on the display214of the identified fuel dispenser18, where the customer may select or “clip” any such displayed virtual discount coupon using a keypad322,424or touchscreen320,422of the mobile electronic device80,90or keypad216or touchscreen214of the identified fuel dispenser18. Any such clipped virtual coupon may then be transferred by the processor20to the customer-member's rewards repository814. In some alternative embodiments, the processor20may “auto-clip” one or more virtual discount coupons by transmitting any such virtual discount coupon directly to the customer's rewards repository814after or during display thereof.

The process1700may be modified to include any one or more of the features illustrated and described with respect to the process900ofFIGS. 9A-9B, the process1050illustrated ofFIG. 10and/or the process1100illustrated inFIG. 11that have not been specifically described herein with respect to the process1700illustrated inFIG. 17. Examples of some such features have been identified in the foregoing description of the process1700, although it will be understood that any one or combination of features illustrated and described with respect to the process900ofFIGS. 9A-9B, the process1050illustrated ofFIG. 10and/or the process1100illustrated inFIG. 11that have or have not been described and/or identified in the description of the process1700may be included therein in some alternative embodiments. Another example of such a feature may be or include any of the odometer reading capture steps1010-1024illustrated inFIG. 9B. Those skilled in the art will recognize that any such modifications to the process1700would be a mechanical step for a skilled software programmer.

While the invention has been illustrated and described in detail in the foregoing drawings and description, the same is to be considered as illustrative and not restrictive in character, it being understood that only illustrative embodiments thereof have been shown and described and that all changes and modifications that come within the spirit of the invention are desired to be protected. For example, it will be understood that while the various illustrated wireless signal broadcasting devices224,710have been illustrated and described herein as being implemented in the form of radio-frequency beacons, this disclosure contemplates alternate embodiments in which one or more of the wireless signal broadcasting devices224,710may be or include other electronic devices configured and operable to broadcast or otherwise emit or transmit wireless identification signals detectable by any of the mobile communication devices illustrated and described herein. Examples of such other electronic devices may include, but are not limited to, transponders, radio-frequency identification (RFID) devices, near-field communication (NFC) devices, far-field communication devices, telemetry devices, automated identification and data capture (AIDC) devices, and the like.