WO2021084461A1

WO2021084461A1 - A system and method for fuel delivery at a client location

Info

Publication number: WO2021084461A1
Application number: PCT/IB2020/060144
Authority: WO
Inventors: Chetan Rajendra Walunj
Original assignee: Chetan Rajendra Walunj
Priority date: 2019-10-31
Filing date: 2020-10-29
Publication date: 2021-05-06

Abstract

Disclosed is a system 101 and method 300 for fuel delivery at a client location. The system 101 is a vendor user interface for receiving the fuel refill request and client location information from a client user interface, wherein the vendor user interface generates an alphanumeric code along with client location information. The vendor user interface also transmits the alphanumeric code along with client location information to a drive device 103-2 enabled with a fuel bowser interface at a fuel bowser 105. The fuel bowser interface compares a current location of the fuel bowser 105 with the client location information and accepts the alphanumeric code to unlock a fuel dispensing unit of the fuel bowser 105 only if the current location of the fuel bowser 105 matches with the client location information.

Description

TITLE OF INVENTION:

A SYSTEM AND METHOD FOR FUEL DELIVERY AT A CLIENT LOCATION

CROSS-REFERENCE TO RELATED APPLICATIONS AND PRIORITY

The present application claims priority from Indian Patent Application number 201921044225 filed on 31^st October 2019, incorporated herein by reference.

TECHNICAL FIELD

The present subject matter described herein, in general, relates to a system for fuel delivery. More particularly, the present subject matter relates to a system and method for fuel ordering and delivery at a client location.

BACKGROUND

Automobiles such as trucks and commercial electricity generators and other heavy vehicle diesel engines require fuel in large quantities. Liquid fuels such as diesel is in great demand since automobiles as well as industrial generators consume it on a larger extent. A fuel filling station (fuel pump) sells fuel and engine lubricants for automobiles as well as commercial diesel electric generators. An automobile is filled with required amount of fuel by purchasing the fuel from the fuel filling station. However, it is not always possible to bring each and every vehicle to the fuel pump. For instance, in case of diesel electricity generators, diesel is carried in barrels from the fuel pump to the diesel electricity generator. This leads to a lot of adulteration and mismanagement of fuel. Currently, a large number of fuel filling stations are available, but the fuel delivery at a client location is not done in time. There is a delay in fuel delivery at the fuel filling stations due to lack of fuel availability, communication hurdles, fuel theft, and such like problems. To address this problem, now a days, the concept of mobile fuel pump has evolved which can deliver fuel directly at the client location. However, this new system also suffers from mismanagement and fuel theft due to inadequate security checks during fuel delivery. Thus, there is a long-standing need of a system and method for fuel delivery at a client location wherein the system provides an authentic, theft free, on-time and on-demand fuel delivery.

SUMMARY

This summary is provided to introduce the concepts related to a system and method for fuel delivery at a client location and the concepts are further described in the detail description. This summary is not intended to identify essential features of the claimed subject matter nor it is intended to use in determining or limiting the scope of claimed subject matter.

In one implementation, the present subject matter describes a system for fuel delivery at a client location. The system may comprise a vendor user interface for receiving the fuel refill request and client location information from a client user interface. The vendor user interface may generate an alphanumeric code along with client location information upon receipt of the fuel refill request. The vendor user interface may be configured for transmitting the alphanumeric code along with client location information to a drive device at a fuel bowser (mobile fuel pump). The drive device may be enabled with a fuel bowser interface configured for comparing, a current location of the fuel bowser with the client location information. The drive device may also be configured for accepting, the alphanumeric code to unlock a fuel dispensing unit of the fuel bowser only if the current location of the fuel bowser matches with the client location information.

In another implementation, the present subject matter describes a method for fuel delivery at a client location. The method may comprise receiving, via a vendor user interface, the fuel refill request and client location information from the client interface. The vendor user interface may generate an alphanumeric code along with client location information. The method may comprise transmitting, via the vendor user interface, the alphanumeric code along with client location information to a drive device at a fuel bowser (mobile fuel pump). The drive device may be enabled with a fuel bowser interface. The method may comprise comparing, via the fuel bowser interface, a current location of the fuel bowser with the client location information. The method may comprise accepting, via the fuel bowser interface, the alphanumeric code to unlock a fuel dispensing unit of the fuel bowser only if the current location of the fuel bowser matches with the client location information.

BRIEF DESCRIPTION OF DRAWINGS

The detailed description is described with reference to the accompanying figures. 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 drawings to refer like features and components.

Figure 1 illustrates a system 100 for fuel delivery at a client location, in accordance with an embodiment of a present subject matter. Figure 2 illustrates components 200 of the system 100, in accordance with an embodiment of a present subject matter.

Figure 3 illustrates a method 300 for fuel delivery at a client location, in accordance with an embodiment of a present subject matter.

DETAILED DESCRIPTION

Reference throughout the specification to “various embodiments,” “some embodiments,” “one embodiment,” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in various embodiments,” “in some embodiments,” “in one embodiment,” or “in an embodiment” in places throughout the specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments.

Figure 1 illustrates an implementation 100 of a system 101 for fuel delivery at a client location, in accordance with an embodiment of a present subject matter. In one implementation, the system 101 may be connected to a user device 103 through a network 102. It will be understood that the system 101 may be accessed by multiple users through one or more user devices 103-1, 103-2,103- 3, collectively referred as user device 103 hereinafter, or user 103, or applications residing on the user device 103.

In an embodiment, as illustrated in figure 1, the system 101 may accept information provided by multiple users using the corresponding user devices 103-1,103-2,... 103-n, to register the respective user with the system 101.

In an embodiment, though the present subject matter is explained considering that the system 101 is implemented as a server, it may be understood that the system 101 may also be implemented in a variety of user devices, such as a but are not limited to, a portable computer, a personal digital assistant, a handheld device, a mobile, a laptop computer, a desktop computer, a notebook, a workstation, a mainframe computer, and the like. In one implementation, the network 102 may be a wireless network, a wired network or a combination thereof. The network 102 can be accessed by the device using wired or wireless network connectivity means including updated communications technology.

In one implementation, the network 102 may be a wireless network, a wired network or a combination thereof. The network 102 can be implemented as one of the different types of networks, cellular communication network, local area network (LAN), wide area network (WAN), the internet, and the like. The network 102 may either be a dedicated network or a shared network. The shared network represents an association of the different 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), and the like, to communicate with one another. Further, the network 102 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like.

In one embodiment, the implementation 100 comprises the system 101 may be enabled with a vendor user interface. In one embodiment, the system 101 may interchangeably be a vendor user interface associated with a vendor. The user device 103-1 may be enabled with a client user interface at a client location, wherein the client user interface is associated with a fuel storage unit 104 at the client location. The user device 103-2 may be a drive device which may be enabled with a fuel bowser interface, wherein the drive device 103-2 is with a driver of a fuel bowser 105.

In a preferred embodiment, the vendor may be a fuel vendor for petrol, diesel, gasoline and such like. The vendor user interface is configured to register and authenticate the users associated with user device 103-1. In one embodiment, a client may be a person who requires fuel, wherein the client location may be at a larger distance from the normally available fuel stations in the vicinity. In one embodiment, the client may require fuel to be preserved at the fuel storage unit 104, wherein the fuel storage unit 104 comprises, but may not be limited to, a fuel filing station at a remote location from the urban area wherein fuel is readily available, vehicles, fuel storage stations at a factory, diesel generators and such like. The fuel storage unit 104 of the client may be equipped with a short range communication system such as Bluetooth transmitter, infrared system, RFID system and such like. The Bluetooth connectivity may be enabled by HC05.

In one embodiment, when the client requires fuel to be refilled in the fuel storage unit 104, the client requests the vendor for refilling fuel. Thus, the vendor user interface receives the fuel refill request and client location information from the client user interface of the user device 103-1. The vendor user interface generates an alphanumeric code along with client location information. In one embodiment, the location information corresponds to at least one of a geo-location, geographical co-ordinates, latitude, longitude and combination thereof. In one embodiment, the alphanumeric code is at least one of a QR code, a unique identifier, and a one-time password. The vendor user interface is further configured for transmitting the alphanumeric code along with client location information to a drive device 103-2 at the fuel bowser 105. The drive device 103-2 is enabled with a fuel bowser interface. In one embodiment, the driver of the fuel bowser 105 after receiving the alphanumeric code along with client location information on the fuel bowser interface, the driver may accept or reject to travel for the fuel refill request through the fuel bowser interface. If the driver rejects to travel, the vendor user interface may be configured to search for another fuel bowser driver at a nearest and convenient location. The vendor user interface is always configured to transmit the alphanumeric code along with client location information to the driver of the fuel bowser 105 on the corresponding fuel bowser interface who is nearest to the vendor location and does not have any urgent trip. If the driver accepts to travel, the driver then travels to the client location based on the client location information. The vendor user interface and fuel bowser interface comprise a processor and a memory coupled with the processor, wherein the processor is configured to execute programmed instructions stored in the memory. The vendor user interface is configured to track the fuel bowser 105 through a GPS system of the fuel bowser interface 103-2 which is with the driver of the bowser 105 during travelling. In one embodiment, the fuel bowser interface is configured to communicate with the client user interface and the system 101 via a network 102. In one embodiment, the fuel bowser interface is configured to communicate with the client user interface and the vendor user interface via a network 102. Once the fuel bowser 105 reaches the client location, the fuel bowser interface is configured for comparing, a current location of the fuel bowser 105 with the client location information. In one embodiment, the fuel bowser interface is further configured for accepting, the alphanumeric code from the client to unlock a fuel dispensing unit of the fuel bowser 105 only if the current location of the fuel bowser 105 matches with the client location information, wherein the client receives the alphanumeric code on the client user interface from the vendor user interface.

In one embodiment, the driver via the fuel bowser interface may input the current location of the fuel bowser 105. The vendor user interface is configured for monitoring the current location of the fuel bowser 105 and the client location information. If both the locations match, the fuel dispensing unit of the fuel bowser 105 is unlocked and the driver then inserts the fuel dispensing unit into the inlet of the fuel storage unit 104 for dispensing the fuel from the fuel bowser 105 to the fuel storage unit 104. In another embodiment, when the fuel bowser 105 reaches the client location, the vendor user interface immediately matches the current location of the fuel bowser 105 and the client location information, by taking inputs from the GPS system of the fuel bowser interface. In one embodiment, once the fuel bowser 105 reaches the client location, the fuel storage unit 104 enabled with a short-range communication means such as Bluetooth transmits a Bluetooth signal to the fuel bowser interface. If the fuel bowser 105 is in the vicinity of the Bluetooth signal, the fuel bowser interface receives a unique identifier name of the fuel storage unit 104. The driver of the fuel bowser 105, via the fuel bowser interface accepts the Bluetooth signal by clicking the unique identifier name, thereby unlocking the fuel dispenser of the fuel bowser 105 by matching Bluetooth signal. In other words, as the Bluetooth signal prevails in a short communication range, the signal from the fuel storage unit 104 is received by the fuel bowser interface only if they are in a same location, thus validating that the fuel bowser 105 is at the correct client location. Such validation provides dual location matching and verification, thereby assuring fuel delivery at accurate location. Fuel thefts are not possible due to such dual location matching and verification.

In one embodiment, if the system switches to offline mode temporarily, the fuel bowser interface may accumulate the data which is to be transferred in a buffer memory. As soon as the system switches to online mode, the fuel bowser interface immediately transmits the accumulated data to the vendor user interface. In one embodiment, the vendor user interface, the client user interface, and the fuel bowser interface comprise GPS and Bluetooth systems.

Referring to figure 2, illustrates components 200 of the system 101, in accordance with an embodiment of a present subject matter. The components 200 of the system 101 comprise at least one processor 201, an input/output (PO) interface 202, a memory 203, modules 204 and data 209. In one embodiment, the at least one processor 201 is configured to fetch and execute computer- readable instructions stored in the memory 203.

In one embodiment, the PO interface 202 implemented as a mobile application or a web-based application may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. The PO interface 202 may allow the system 101 to interact with the user devices 103. Further, the I/O interface 202 may enable the user device 103 to communicate with other computing devices, such as web servers and external data servers (not shown). The I/O interface 202 can facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as WLAN, cellular, or satellite. The I/O interface 202 may include one or more ports for connecting to another server.

In an exemplary embodiment, the I/O interface 202 is an interaction platform which may provide a connection between users and system 101.

In an implementation, the memory 203 may include any computer-readable medium known in the art including, for example, volatile memory, such as static random-access memory (SRAM) and dynamic random-access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and memory cards. The memory 203 may include modules 204 and data 209. The data 209 further comprises a data store 210 and other data 211.

In one embodiment, the modules 204 include routines, programs, objects, components, data structures, etc., which perform particular tasks, functions or implement particular abstract data types. In one implementation, the modules 204 may include a data receiving module 205, a data transmission module 206, a comparison module 207, and an unlocking module 208.

In one embodiment, the data receiving module 205 is configured for receiving the fuel refill request and client location information via a vendor user interface from the client user interface, wherein the vendor user interface generates an alphanumeric code along with client location information. The data transmission module 206 is configured for transmitting the alphanumeric code along with client location information via the vendor user interface to a drive device at a fuel bowser 105, wherein the drive device 103-2 is enabled with a fuel bowser interface. The comparison module 207 is configured for comparing, a current location of the fuel bowser 105 with the client location information via the fuel bowser interface. The unlocking module 208 is configured for accepting the alphanumeric code via the fuel bowser interface to unlock a fuel dispensing unit of the fuel bowser 105 only if the current location of the fuel bowser 105 matches with the client location information.

Figure 3 illustrates a method 300 for fuel delivery at a client location, in accordance with the embodiment of the present subject matter.

At step 301, a vendor user interface receives the fuel refill request. In one embodiment, the vendor user interface 101 is configured for receiving the fuel refill request and client location information from the client user interface. The vendor user interface generates an alphanumeric code along with client location information.

At step 302, the vendor user interface transmits the alphanumeric code to a drive device. In one embodiment, the vendor user interface is configured for transmitting the alphanumeric code along with client location information to a drive device 103-2 at a fuel bowser 105, wherein the drive device 103-2 is enabled with a fuel bowser interface.

At step 303, the fuel bowser interface is configured for comparing a current location of the fuel bowser 105 with the client location information.

At step 304, the fuel bowser interface is further configured for accepting the alphanumeric code to unlock a fuel dispensing unit of the fuel bowser 105 only if the current location of the fuel bowser 105 matches with the client location information.

The embodiments, examples and alternatives of the preceding paragraphs or the description and drawings, including any of their various aspects or respective individual features, may be taken independently or in any combination. Features described in connection with one embodiment are applicable to all embodiments, unless such features are incompatible.

Although implementations for the computer implemented a system 101 and method 300 for fuel delivery at a client location have been described in language specific to structural features and/or methods, it is to be understood that the appended claims are not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as examples of implementations for a system 101 and method 300 for fuel delivery at a client location.

Claims

WE CLAIM:

1. A system 101 for fuel delivery at a client location, the system 101 configured for: receiving the fuel refill request and client location information from a client user interface, wherein the system 101 generates an alphanumeric code along with client location information; and transmitting the alphanumeric code along with client location information to a drive device 103-2 at a fuel bowser 105, wherein the drive device 103-2 is enabled with a fuel bowser interface configured for: comparing, a current location of the fuel bowser 105 with the client location information; and accepting, the alphanumeric code to unlock a fuel dispensing unit of the fuel bowser 105 only if the current location of the fuel bowser 105 matches with the client location information.

2. The system 101 as claimed in claim 1, wherein the system 101 is enabled with a vendor user interface.

3. The system 101 as claimed in claim 1, wherein the system 101 and fuel bowser interface comprise a processor and a memory coupled with the processor, wherein the processor is configured to execute programmed instructions stored in the memory.

4. The system 101 as claimed in claim 1, wherein the fuel bowser interface is configured to communicate with the client user interface and the system 101 via a network 102.

5. The system 101 as claimed in claim 1, wherein the client user interface is associated with a fuel storage unit 104 at the client location, the system 101 is associated with a fuel supplier and the fuel bowser interface is associated with the driver of the fuel bowser 105.

6. The system 101 as claimed in claim 1, wherein the alphanumeric code is at least one of a QR code, a unique identifier, and a one-time password.

7. The system 101 as claimed in claim 1, wherein the location information corresponds to at least one of a geo-location, geographical co-ordinates, latitude, longitude and combination thereof.

8. The system 101 as claimed in claim 1, wherein the system 101, the client user interface, and the fuel bowser interface comprise GPS and Bluetooth systems.

9. The system as claimed in claim 4, wherein the fuel storage unit 104 at the client location is enabled with a bluetooth communication means, wherein the Bluetooth communication means transmits a Bluetooth signal to the fuel bowser interface, wherein, the fuel bowser interface receives a unique identifier name of the fuel storage unit 104, when the fuel bowser 105 is in the vicinity of the Bluetooth signal, wherein the driver of the fuel bowser 105 accepts the Bluetooth signal via the fuel bowser interface by clicking the unique identifier name, thereby enabling unlocking the fuel dispenser of the fuel bowser 105 by matching Bluetooth signal.

10. A method 300 for fuel delivery at a client location comprising: receiving, via a system 101, the fuel refill request and client location information from the client user interface, wherein the system 101 generates an alphanumeric code along with client location information; transmitting, via the system 101, the alphanumeric code along with client location information to a drive device 103-2 at a fuel bowser 105, wherein the drive device 103-2 is enabled with a fuel bowser interface; comparing, via the fuel bowser interface, a current location of the fuel bowser 105 with the client location information; and accepting, via the fuel bowser interface, the alphanumeric code to unlock a fuel dispensing unit of the fuel bowser 105 only if the current location of the fuel bowser matches with the client location information.

11. The method as claimed in claim 10, wherein a data receiving module 205 is configured for receiving the fuel refill request and client location information via a vendor user interface from the client user interface, wherein the vendor user interface generates an alphanumeric code along with client location information.

12. The method as claimed in claim 10, wherein a data transmission module 206 is configured for transmitting the alphanumeric code along with client location information via the vendor user interface to a drive device 103-2 at a fuel bowser 105, wherein the drive device 103-2 is enabled with a fuel bowser interface.

13. The method as claimed in claim 10, wherein a comparison module 207 is configured for comparing, a current location of the fuel bowser 105 with the client location information via the fuel bowser interface.

14. The method as claimed in claim 10, wherein an unlocking module 208 is configured for accepting the alphanumeric code via the fuel bowser interface to unlock a fuel dispensing unit of the fuel bowser 105 only if the current location of the fuel bowser 105 matches with the client location information.

15. The method as claimed in claim 10, wherein the vendor user interface is configured to search for another fuel bowser driver at a nearest location from the vendor if the allotted fuel bowser driver of the drive device 103-4 rejects to travel to the client location.