DESC:TECHNICAL FIELD
The present subject matter is generally related to fuel dispenser unit and more particularly, but not exclusively, to method, system and fuel dispenser unit for secure dispensing of fuel from a fuel dispenser unit.

BACKGROUND
A typical fueling environment includes one or more fuel dispensers/fuel dispenser units in a retail outlet which can be used by a user to dispense fuel into a vehicle. At present, in all fuel dispensers, dispensing of fuel is done by squeezing handle in a nozzle of the fuel dispensers. There exists no option to either validate a personnel dispensing fuel from a fuel dispenser or the consumer in the overall fuel dispensing process.
There is a need to track quantity of the fuel that is dispensed from the fuel dispensers and it should be done by an authorized personnel and the consumption has to be tracked at the consumer level in order to avoid frauds. Authentication of the person dispensing the fuel and the consumer who has consumed the fuel are the two major limitations in the existing system.
The information disclosed in this background of the disclosure section is only for enhancement of understanding of the general background of the invention and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

SUMMARY

Disclosed herein is a method for secure dispensing of fuel from a Fuel Dispenser Unit (FDU). The method comprises receiving, by an authentication system associated with a FDU, identification data of a user through the FDU, wherein the identification data received through the FDU is provided by the user to the FDU for accessing the FDU. Thereafter, the method comprises identifying the user based on the received identification data and pre-stored data of the user. Once the user is identified, the authentication system receives authentication data from the user through the FDU. The method further comprises authenticating user based on the received authentication data and the pre-stored data. Once the user is authenticated, the authentication system activates the FDU for dispensing the fuel.

Further, the present disclosure discloses an authentication system for secure dispensing of fuel from a Fuel Dispenser Unit (FDU). The authentication system comprises a processor and a memory. The memory is communicatively coupled to the processor, wherein the memory stores processor-executable instructions, which, on execution, cause the processor to receive identification data of a user through the FDU, wherein the identification data received through the FDU is provided by the user to the FDU for accessing the FDU. The processor identifies the user based on the received identification data and pre-stored data of the user. Thereafter, the processor receives authentication data from the user through the FDU upon identifying the user. Once the user is identified, the processor receives authentication data and compares the authentication data with pre-stored data of the user. The processor activates the FDU for dispensing the fuel upon authenticating the user.
Furthermore, the present disclosure discloses a Fuel Dispenser Unit (FDU). The FDU comprises an input device for receiving identification data and authentication data from a user. The FDU also comprises a transmitting unit for transmitting the identification data and the authentication data to an authentication system for authenticating the user for accessing the FDU. The FDU also comprises one or more nozzle holders for holding the nozzle used for dispensing the fuel.

The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.

BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS
The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and, together with the description, explain the disclosed principles. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figures to reference like features and components. Some embodiments of system and/or methods in accordance with embodiments of the present subject matter are now described, by way of example only, and regarding the accompanying figures, in which:

Fig.1 shows an exemplary architecture for secure dispensing of fuel in accordance with some embodiments of the present disclosure;

Fig.2a shows block diagram of an authentication system in accordance with some embodiments of the present disclosure;

Fig. 2b shows block diagram of a Fuel Dispenser Unit (FDU) in accordance with some embodiments of the present disclosure;

Fig.3 shows a flowchart illustrating method for secure dispensing of fuel in accordance with some embodiments of the present disclosure; and

Fig.4 illustrates a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.

It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and executed by a computer or processor, whether such computer or processor is explicitly shown.

DETAILED DESCRIPTION
In the present document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.
While the disclosure is susceptible to various modifications and alternative forms, specific embodiment thereof has been shown by way of example in the drawings and will be described in detail below. It should be understood, however that it is not intended to limit the disclosure to the specific forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternative falling within the scope of the disclosure.
The terms “comprises”, “comprising”, “includes”, “including” or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device, or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus proceeded by “comprises… a” does not, without more constraints, preclude the existence of other elements or additional elements in the system or method.
Disclosed herein is method and system for secure dispensing of fuel from a Fuel Dispenser Unit (FDU). At first, a user willing to access the FDU may register with an authentication system 101 associated with the FDU. In an embodiment, the authentication system may be configured in the FDU. In another embodiment, the authentication system may be remotely located in a cloud based environment. The user may be at least one of a personnel dispensing fuel from the FDU and a consumer consuming the fuel. During registration process, the user may provide identification details. The identification details may include, but are not limited to, user ID and password, Quick Response (QR) code and Radio Frequency Identification (RFID) tag, Aadhar number, image of the user, contact less cards, chip based card system, sound wave based user identification system and biometric details of the user. The identification details may be stored as pre-stored data in a database associated with the authentication system. When the user is accessing the FDU, the authentication system may request/prompt the user for providing the identification data. The user may provide the identification data to an input device of the FDU. The FDU provides the identification data to the authentication system. The authentication system may identify the user based on the identification data and pre-stored data. Once the user is identified, the authentication system may prompt the user to provide authentication data. Upon receiving the authentication data, the authentication system may authenticate the user based on the authentication data and the pre-stored data. Once the user is authenticated, the authentication system may activate the FDU for dispensing the fuel. In this manner, the present disclosure provides a secure mechanism for fuel dispensing and hence avoids fraud.
Fig.1 shows an exemplary architecture for secure dispensing of fuel in accordance with some embodiments of the present disclosure.

The architecture 100 may include an authentication system 101, a Fuel Dispenser Unit (FDU) 105 and a user 107. For the purpose of illustration, a single FDU 105 and a single user 107 is depicted in Fig.1. However, there may be one or more FDU’s configured in a retail outlet and each of the one or more FDU’s may be associated with the authentication system 101. Also, there may be one or more users associated with the FDU’s. The user 107 may be at least one of a personnel dispensing fuel from the FDU 105 and a consumer consuming the fuel from the FDU 105. The user 107 may access the FDU 105 for either dispensing the fuel or consuming the fuel. When the FDU 105 is accessed by the user 107, before activating the FDU 105 to dispense the fuel, the user 107 may be authenticated. For this purpose, the user 107 must register with the authentication system 101. The authentication system 101 may include a processor, I/O interface and a memory [not shown in Fig.1]. In an embodiment, the authentication system 101 may be a server configured in a remote location from the FDU 105. In this scenario, the FDU 105 may be connected with the authentication system 101 through a communication network 103. The communication network 103 may be a wired or a wireless communication. In another embodiment, the authentication system 101 may be configured in the FDU 105. In an embodiment, for the purpose of registration, the user 107 may download an application in a mobile device associated with the user 107. The application may be provided/hosted by the authentication system 101. Once the application is downloaded, the user 107 may register with the authentication system 101. During the registration process, the user 107 may provide identification details such as user 107 ID and password, Quick Response (QR) code, contact less cards, chip based card system, sound wave based user identification system and Radio Frequency Identification (RFID) tag, Aadhar number, image of the user 107 and biometric details of the user 107. The biometric details may include, but are not limited to, fingerprint, voice, iris and retina. The identification details may be provided to the authentication system 101 through the application. The identification details of each the one or more users registered with the authentication system 101 is stored in a database associated with the authentication system 101 as pre-stored data.
In an embodiment, once the user 107 is registered, the user 107 may use any of these identification details (also referred as details) to identify and authenticate for accessing the FDU 105. In an embodiment, when the user 107 is accessing the FDU 105, the user 107 may be prompted by the authentication system 101 to provide the identification data. The identification data may include at least one of user 107 ID and password, Quick Response (QR) code, contact less cards, chip based card system, sound wave based user identification system Aadhar number, image of the user 107, biometric details of the user 107 and Radio Frequency Identification (RFID) tag. The user 107 may provide the identification data to an input device [not shown in Fig.1] of the FDU 105. The FDU 105 may provide the received identification data to the authentication system 101. The processor may compare the received identification data through the I/O interface with the pre-stored data of the user 107 in the authentication system 101. If the details match with the received identification data, the processor may identify the user 107. As an example, the received identification data may be user 107 ID and password. The processor may compare the received user 107 ID and password with the pre-stored user ID and password of the user 107. If the user 107 ID and the password matches, the processor may identify the user 107 as the genuine user 107. If the details do not match with the received identification data, the authentication system 101 may prompt the user 107 to provide identification details and the process of identifying the user 107 continues till the user 107 is identified.
In an embodiment, once the user 107 is identified, the processor may prompt the user 107 to provide authentication data. The authentication data may include at least one of Aadhar number, image of the user 107, contact less cards, chip based card system, sound wave based user identification system and biometric data. Upon receiving the authentication data through the I/O interface, the processor may compare the received authentication data with the prestored data of the user 107. If the details match with received authentication data, the user 107 is authenticated. As an example, the user 107 may provide Aadhar number as the authentication data. The processor may compare the received Aadhar number with the pre-stored Aadhar number of the user 107, provided during user registration. If the Aadhar number matches, the user 107 may be authenticated. Once the user 107 is authenticated, the processor may activate the FDU 105 for dispensing the fuel. If the details do not match with received authentication data, the processor may not activate the FDU 105.
Fig.2a shows block diagram of an authentication system in accordance with some embodiments of the present disclosure.
In some implementations, the authentication system 101 may include I/O interface 201, a processor 203, a memory 205, data and modules. As an example, the data is stored in the memory 205 configured in the authentication system 101 as shown in the Fig.2a. In one embodiment, the data may include pre-stored data 207 and other data 209. In the illustrated Fig.2a, modules are described herein in detail.

In some embodiments, the data may be stored in the memory in form of various data structures. Additionally, the data can be organized using data models, such as relational or hierarchical data models. The other data 209 may store data, including temporary data and temporary files, generated by the modules for performing the various functions of the authentication system 101.
In some embodiments, the data stored in the memory may be processed by the modules of the authentication system 101. The modules may be stored within the memory. In an example, the modules communicatively coupled to the processor 203 configured in the authentication system 101 may also be present outside the memory as shown in Fig.2a and implemented as hardware. As used herein, the term modules may refer to an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.
In some embodiments, the modules may include, for example, a receiving module 211, a registration module 212, an identification module 213, an authentication module 215, an activation module 217 and other modules 221. The other modules 221 may be used to perform various miscellaneous functionalities of the authentication system 101. It will be appreciated that such aforementioned modules may be represented as a single module or a combination of different modules.
As used herein, the term module refers to an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality. In an embodiment, the other modules 221 may be used to perform various miscellaneous functionalities of the authentication system 101. It will be appreciated that such modules may be represented as a single module or a combination of different modules. Furthermore, a person of ordinary skill in the art will appreciate that in an implementation, the one or more modules may be stored in the memory, without limiting the scope of the disclosure. The said modules when configured with the functionality defined in the present disclosure will result in a novel hardware.

In an embodiment, the receiving module 211 may be configured to receive the identification data and the authentication data of the user 107 from an input device of the FDU 105.

In an embodiment, the registration module 212 may be configured to register user 107 with the authentication system 101. In order to register, the user 107 may download an application in a mobile device associated with the user 107. The application may be provided/hosted by the authentication system 101. During the registration process, the user 107 may provide identification details such as user 107 ID and password, Quick Response (QR) code, contact less cards, chip based card system, sound wave based user identification system and Radio Frequency Identification (RFID) tag, Aadhar number, image of the user 107 and biometric details of the user 107. The biometric details may include, but are not limited to, fingerprint, voice, iris and retina. The identification details may be provided to the authentication system 101 through the application. The identification details of each of the one or more users registered with the authentication system 101 is stored in a database associated with the authentication system 101 as pre-stored data 207. Once the user 107 is registered, the user 107 may use any of these identification details to identify and authenticate for accessing the FDU 105.

In an embodiment, the identification module 213 may be configured to identify the user 107 accessing the FDU 105. The identification module 213 may compare the received identification data with the pre-stored data 207. If the identification data matches with pre-stored data 207 of the user 107, the identification module 213 identifies the user 107 as the genuine user 107. If the details do not match, the authentication system 101 may prompt the user 107 to provide details and the process of identifying continues till the user 107 is identified. In another embodiment, the authentication system 101 may prompt the user 107 to register with the authentication system 101 by providing the identification details if the identification details are not registered previously with the authentication system 101. The pre-stored data 207 is captured during registration process of the user 107 and stored in a database associated with the authentication system 101. The pre-stored data 207, may include, but is not limited to, name of the user 107, image of the user 107, Aadhar number of the user 107, user 107 ID and password generated for the user 107, QR code generated for the user 107, RFID tag for the user 107, amount available with user 107 for consuming the fuel, contact less cards, chip based card system, sound wave based user identification system and biometric details of the user 107.

In an embodiment, the authentication module 215 may be configured to authenticate the user 107 accessing the FDU 105. The authentication module 215 may compare the received authentication data with the pre-stored data 207. If the authentication data matches with the pre-stored data 207 of the user 107, the authentication module 215 authenticates the user 107. If the authentication data does not match with the pre-stored data 207 of the user 107, the authentication system 101 may prompt the user 107 to provide the authentication data and the process of authenticating the user 107 continues till the user 107 is authenticated.

In an embodiment, the activation module 217 may be configured to activate the FDU 105. Once the user 107 is authenticated, the authentication module 215 may activate the FDU 105 to dispense the fuel.

Fig. 2b shows block diagram of a Fuel Dispenser Unit in accordance with some embodiments of the present disclosure.

As shown in Fig.2b, the FDU 105 comprises a display unit 231, a transmitting unit 233, an input device 235 and one or more nozzle holders 237. The input device 235 may be configured to receive identification data and the authentication data from the user 107 accessing the FDU 105. The transmitting unit 233 may be configured to transmit the received identification data and the authentication data to the authentication system 101. The display unit 231may be configured to indicate quantity of fuel dispensed and the amount for the fuel being dispensed. The display unit 231 may also indicate about successful or unsuccessful identification and authentication of the user 107. The one or more nozzle holders 237 may be provided to hold the nozzle configured for dispensing the fuel. Once the FDU 105 is activated by the authentication system 101, the user 107 may use the nozzle to dispense the fuel from the FDU 105.

Fig.3 shows a flowchart illustrating a method for secure dispensing of fuel in accordance with some embodiments of the present disclosure.

As illustrated in Fig.3, the method 300 includes one or more blocks illustrating a method for secure dispensing of fuel from a fuel dispenser unit. The method 300 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform specific functions or implement specific abstract data types.

The order in which the method 300 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the spirit and scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.

In an embodiment, a user 107 wishing to access the FDU 105 may register with the authentication system 101. To register, the user 107 may download an application in a mobile device associated with the user 107. The application may be hosted by the authentication system 101. Once the application is downloaded, the user 107 may register with the authentication system 101. During the registration process, the user 107 may provide identification details such as user 107 ID and password, Quick Response (QR) code, contact less cards, chip based card system, sound wave based user identification system and Radio Frequency Identification (RFID) tag, Aadhar number, image of the user 107 and biometric details of the user 107. The biometric details may include, but are not limited to, fingerprint, voice, iris and retina. The identification details may be provided to the authentication system 101. The identification details are stored in a database associated with the authentication system 101. Once the user 107 is registered, the registered user 107 may access the FDU 105. However, each time user 107 tries to access the FDU 105, the authentication system 101 may validate authenticity of the user 107 accessing the FDU 105 which is explained in the below method steps.
At block 301, the method 300 may include receiving identification data from a user 107 accessing the FDU 105. The user 107 may be at least one of personnel dispensing fuel from the FDU 105 and consumer consuming the fuel from the FDU 105. The identification data may include at least one of user 107 ID and password, Quick Response (QR) code, contact less cards, chip based card system, sound wave based user identification system and Radio Frequency Identification (RFID) tag.

At block 303, the method 300 may include identifying the user 107 based on the received identification data and pre-stored data 207 of the user 107. The pre-stored data 207 is the identification details received from the user 107 during the registration process and stored in the database. The authentication system 101 may compare the received identification data with the pre-stored data 207. If the received identification data matches with the pre-stored data 207, the authentication system 101 may identify the user 107 at block 305. If the user is identified, the method may proceed to block 307 via “Yes”. If the user 107 is not identified, a display unit 231 of the FDU 105 may display about unsuccessful identification of the user 107 and the method may proceed to block 301 via “no” wherein the authentication system 101 may prompt the user 107 to provide the identification data and the identifying process continues until the user 107 is identified.

At block 307, the method 300 may include receiving authentication data from the user 107. The authentication data may include at least one of Aadhar number, image of the user 107, contact less cards, chip based card system, sound wave based user identification system and biometric data.

At block 309, the method 300 may include authenticating the user 107 based on the authentication data and the pre-stored data 207. The authentication system 101 may compare the received authentication data with the pre-stored data 207. If the received authentication data matches with the pre-stored data 207, the authentication system 101 may authenticate the user 107 at block 311. If the user is authenticated, the method may proceed to block 313 via “Yes”. If the user 107 is not authenticated, the display unit 231 may display about unsuccessful authentication of the user 107 and the method may proceed to block 301 via “no” wherein the authentication system 101 may prompt the user 107 to provide the authentication data and the authentication process continues until the user 107 is authenticated.

At block 313, the method 300 may include activating the FDU 105 to dispense the fuel. Once the user 107 is authenticated, the authentication system 101 may activate the FDU 105 to dispense the fuel.

In this manner, the present disclosure provides a secure mechanism for fuel dispensing at Retail Outlet (RO). The user 107 wishing to access the FDU 105 is authenticated prior to dispensing the fuel from the FDU 105 thereby avoiding fraud.

Computer System
Fig.4 illustrates a block diagram of an exemplary computer system 400 for implementing embodiments consistent with the present disclosure. In an embodiment, the computer system 400 may be authentication system 101, which is used for providing a secure mechanism for fuel dispensing. The computer system 400 may include a central processing unit (“CPU” or “processor”) 402. The processor 402 may comprise at least one data processor for executing program components for executing user or system-generated business processes. The processor 402 may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.
The processor 402 may be disposed in communication with one or more input/output (I/O) devices (411 and 412) via I/O interface 401. The I/O interface 401 may employ communication protocols/methods such as, without limitation, audio, analog, digital, stereo, IEEE-1394, serial bus, Universal Serial Bus (USB), infrared, PS/2, BNC, coaxial, component, composite, Digital Visual Interface (DVI), high-definition multimedia interface (HDMI), Radio Frequency (RF) antennas, S-Video, Video Graphics Array (VGA), IEEE 802.n /b/g/n/x, Bluetooth, cellular (e.g., Code-Division Multiple Access (CDMA), High-Speed Packet Access (HSPA+), Global System For Mobile Communications (GSM), Long-Term Evolution (LTE) or the like), etc. Using the I/O interface 401, the computer system 400 may communicate with one or more I/O devices 411 and 412. In some implementations, the I/O interface 401 may be used to receive identification data and the authentication data from the FDU 105.
In some embodiments, the processor 402 may be disposed in communication with a communication network 409 via a network interface 403. The network interface 403 may communicate with the communication network 409. The network interface 403 may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10/100/1000 Base T), Transmission Control Protocol/Internet Protocol (TCP/IP), token ring, IEEE 802.11a/b/g/n/x, etc.
The communication network 409 can be implemented as one of the several types of networks, such as intranet or Local Area Network (LAN) and such within the organization. The communication network 409 may either be a dedicated network or a shared network, which represents an association of several types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), etc., to communicate with each other. Further, the communication network 409 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, etc.
In some embodiments, the processor 402 may be disposed in communication with a memory 405 (e.g., RAM 413, ROM 414, etc. as shown in FIG. 4) via a storage interface 404. The storage interface 404 may connect to memory 405 including, without limitation, memory drives, removable disc drives, etc., employing connection protocols such as Serial Advanced Technology Attachment (SATA), Integrated Drive Electronics (IDE), IEEE-1394, Universal Serial Bus (USB), fiber channel, Small Computer Systems Interface (SCSI), etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, Redundant Array of Independent Discs (RAID), solid-state memory devices, solid-state drives, etc.
The memory 405 may store a collection of program or database components, including, without limitation, user /application 406, an operating system 407, a web browser 408, mail client 415, mail server 416, web server 417 and the like. In some embodiments, computer system 400 may store user /application data 406, such as the data, variables, records, etc. as described in this invention. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases such as OracleR or SybaseR.
The operating system 407 may facilitate resource management and operation of the computer system 400. Examples of operating systems include, without limitation, APPLE MACINTOSHR OS X, UNIXR, UNIX-like system distributions (E.G., BERKELEY SOFTWARE DISTRIBUTIONTM (BSD), FREEBSDTM, NETBSDTM, OPENBSDTM, etc.), LINUX DISTRIBUTIONSTM (E.G., RED HATTM, UBUNTUTM, KUBUNTUTM, etc.), IBMTM OS/2, MICROSOFTTM WINDOWSTM (XPTM, VISTATM/7/8, 10 etc.), APPLER IOSTM, GOOGLER ANDROIDTM, BLACKBERRYR OS, or the like. A user interface may facilitate display, execution, interaction, manipulation, or operation of program components through textual or graphical facilities. For example, user interfaces may provide computer interaction interface elements on a display system operatively connected to the computer system 500, such as cursors, icons, check boxes, menus, windows, widgets, etc. Graphical User Interfaces (GUIs) may be employed, including, without limitation, APPLE MACINTOSHR operating systems, IBMTM OS/2, MICROSOFTTM WINDOWSTM (XPTM, VISTATM/7/8, 10 etc.), UnixR X-Windows, web interface libraries (e.g., AJAXTM, DHTMLTM, ADOBE® FLASHTM, JAVASCRIPTTM, JAVATM, etc.), or the like.

Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present invention. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term “computer-readable medium” should be understood to include tangible items and exclude carrier waves and transient signals, i.e., non-transitory. Examples include Random Access Memory (RAM), Read-Only Memory (ROM), volatile memory, nonvolatile memory, hard drives, Compact Disc (CD) ROMs, Digital Video Disc (DVDs), flash drives, disks, and any other known physical storage media.
Advantages of the embodiment of the present disclosure are illustrated herein.
In an embodiment, the present disclosure provides method, system and FDU for secure dispensing of fuel from FDU.

The present disclosure authenticates user accessing the FDU for dispensing fuel from FDU and hence avoids fraud.

The terms "an embodiment", "embodiment", "embodiments", "the embodiment", "the embodiments", "one or more embodiments", "some embodiments", and "one embodiment" mean "one or more (but not all) embodiments of the invention(s)" unless expressly specified otherwise.

The terms "including", "comprising", “having” and variations thereof mean "including but not limited to", unless expressly specified otherwise. The enumerated listing of items does not imply that any or all the items are mutually exclusive, unless expressly specified otherwise.

The terms "a", "an" and "the" mean "one or more", unless expressly specified otherwise.

A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary, a variety of optional components are described to illustrate the wide variety of possible embodiments of the invention.

When a single device or article is described herein, it will be clear that more than one device/article (whether they cooperate) may be used in place of a single device/article. Similarly, where more than one device or article is described herein (whether they cooperate), it will be clear that a single device/article may be used in place of the more than one device or article or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the invention need not include the device itself.

Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based here on. Accordingly, the embodiments of the present invention are intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.

While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.

Referral Numerals:

Reference Number Description
100 Architecture
101 Authentication System
103 Communication Network
105 FDU
107 User
201 I/O Interface
203 Processor
205 Memory
207 Pre-stored data
209 Other data
211 Receiving Module
212 Registration Module
213 Identification Module
215 Authentication Module
217 Activation Module
221 Other Modules
231 Display Unit
233 Transmitting unit
235 Input Device
237 One or more nozzle holders
400 Exemplary computer system
401 I/O Interface of the exemplary computer system
402 Processor of the exemplary computer system
403 Network interface
404 Storage interface
405 Memory of the exemplary computer system
406 User /Application
407 Operating system
408 Web browser
409 Communication network
411 Input devices
412 Output devices
413 RAM
414 ROM
415 Mail Client
416 Mail Server
417 Web Server
,CLAIMS:We claim:
1. A method for secure dispensing of fuel from a Fuel Dispenser Unit (FDU) 105, the method comprising:
receiving, by an authentication system (101) associated with a FDU (105), identification data of a user (107) through the FDU, wherein the identification data received through the FDU is provided by the user (107) to the FDU (105) for accessing the FDU (105);
identifying, by the authentication system (101), the user (107) based on the received identification data and pre-stored data of the user (107);
receiving, by the authentication system (101), authentication data from the user (107) through the FDU (105) upon identifying the user (107);
authenticating, by the authentication system (101), the user (107) based on the received authentication data and the pre-stored data (207); and
activating, by the authentication system (101), the FDU (105) for dispensing the fuel upon authenticating the user (107).
2. The method as claimed in claim 1, wherein the user (107) is at least one of fuel dispenser personnel of the FDU (105) and consumer of the fuel.

3. The method as claimed in claim 1, wherein the identification data comprises at least one of user (107) ID and password, Quick Response (QR) code, contact less cards, chip based card system, sound wave based user identification system and Radio Frequency Identification (RFID) tag.

4. The method as claimed in claim 1, wherein the pre-stored data (207) is recorded during registration of the user (107) with the authentication system (101).

5. The method as claimed in claim 4, wherein the pre-stored data (207) comprises name of the user (107) , image of the user (107), Aadhar number of the user (107) , user (107) ID and password generated for the user (107), QR code generated for the user (107) , RFID tag for the user (107), amount available with user (107) for consuming the fuel, contact less cards, chip based card system, sound wave based user identification system and biometric details of the user (107) .

6. The method as claimed in claim 1, wherein the authentication data comprises at least one of Aadhar number, image of the user (107), contact less cards, chip based card system, sound wave based user identification system and biometric data.

7. An authentication system (101) for secure dispensing of fuel from a Fuel Dispenser Unit (FDU) (105), the authentication system (101) comprising:
a processor (203); and
a memory (205) communicatively coupled to the processor (203), wherein the memory (205) stores processor-executable instructions, which, on execution, cause the processor (203) to:
receive identification data of a user (107) through the FDU (105), wherein the identification data received through the FDU (105) is provided by the user (107) to the FDU for accessing the FDU (105);
identify the user (107) based on the received identification data and pre-stored data (207) of the user (107);
receive authentication data from the user (107) through the FDU (105) upon identifying the user (107);
authenticate the user (107) based on the received authentication data and the pre-stored data; and
activate the FDU (105) for dispensing the fuel upon authenticating the user (107).
8. The authentication system (101) as claimed in claim 7, wherein the user (107) is at least one of fuel dispenser personnel of the FDU (105) and consumer of the fuel.

9. The authentication system (101) as claimed in claim 7, wherein the identification data comprises at least one of user (107) ID and password, Quick Response (QR) code, contact less cards, chip based card system, sound wave based user identification system and Radio Frequency Identification (RFID) tag.

10. The authentication system (101) as claimed in claim 7, wherein the processor (203) records the pre-stored data (207) during registration of the user (107) with the authentication system (101).

11. The authentication system (101) as claimed in claim 10, wherein the pre-stored data (207) comprises name of the user (107), image of the user (107) , Aadhar number of the user (107) , user (107) ID and password generated for the user (107) , QR code generated for the user (107) , RFID tag for the user (107), amount available with user (107) for consuming the fuel, contact less cards, chip based card system, sound wave based user identification system and biometric details of the user (107).

12. The authentication system (101) as claimed in claim 7, wherein the authentication data comprises at least one of Aadhar number, image of the user (107), contact less cards, chip based card system, sound wave based user identification system and biometric data.

13. A Fuel Dispenser Unit (FDU) (105) comprising:
one or more nozzle holders (237) for holding nozzle used to dispense the fuel;
an input device (235) for receiving identification data and authentication data from a user (107); and
a transmitting unit (233) for transmitting the identification data and the authentication data to an authentication system for authenticating the user (107) accessing the FDU.
14. The FDU (105) as claimed in claim 13, wherein the identification data comprises at least one of user (107) ID and password, Quick Response (QR) code, contact less cards, chip based card system, sound wave based user identification system and Radio Frequency Identification (RFID) tag and the authentication data comprises at least one of Aadhar number, image of the user (107) , contact less cards, chip based card system, sound wave based user identification system and biometric data.

15. The FDU (105) as claimed in claim 13 further comprises a display unit (231) for indicating quantity fuel being dispensed, amount for the fuel being dispensed and successful and unsuccessful identification and authentication of the user (107).