Abnormality Detection during Fuel Supply Operation

Abstract

The system detects a fuel supply operation indicating that fuel is being supplied from a fuel supply terminal. The system determines an identifier value associated with the volume of fuel supplied from the fuel supply terminal. The system determines a measured volume parameter per unit time associated with the fuel supplied from the fuel supply terminal by dividing the determined identifier value by a unit parameter. The system compares the measured volume parameter per unit time with a threshold volume parameter per unit time. In response to determining that the measured volume parameter per unit time is less than the threshold volume parameter per unit time, the system communicates to the fuel supply terminal an electronic signal instructing the fuel supply terminal to stop the supply of fuel.

Description

Technical Field

[0001] The present disclosure generally relates to signal processing and control processing, and more specifically, to detecting anomalies during a fuel dispensing operation.

Background Art

[0002] Conventional fuel dispensing terminals are typically configured to facilitate the dispensing of fuel to a user. The user can operate the fuel dispensing terminal to dispense fuel into a vehicle. It is difficult to determine exactly how much fuel is actually dispensed from the fuel dispensing terminal.

Summary of the Invention

[0003] The systems described in the present disclosure provide several practical applications and technical advantages that overcome current technical problems as described herein. The following disclosure is incorporated in particular into practical applications for detecting anomalies in fuel dispensing terminals. This in turn provides additional practical applications for improving the basic operation of fuel dispensing terminals. The disclosed systems are further incorporated into additional practical applications for stopping a fuel dispensing operation if it is determined that the fuel dispensing operation is abnormal or malicious. These practical applications and the technical advantages derived therefrom are described below. Detection of Abnormalities during Fuel Supply Operations

[0004] The disclosed systems contemplate systems and methods for detecting anomalies during a fuel dispensing operation. An anomaly can indicate that there is a discrepancy between the actual fuel dispensed from the fuel dispensing terminal and the measured fuel volume dispensed. In some cases, a bad actor may operate the fuel dispensing terminal to tamper with the fuel flow reading or measurement of the fuel dispensing terminal. Exemplary methods of operating a fuel dispensing terminal are described below.

[0005] The present fuel dispensing terminal has a pulser rod component configured to rotate when fuel is dispensed from the fuel dispensing terminal. When the pulser rod rotates, it rotates a mechanical gear of a meter component configured to determine or measure how much fuel has been dispensed at a given timestamp. When a user initiates pumping fuel from the fuel dispensing terminal into a vehicle, a pulser rod within the fuel dispensing terminal begins to rotate, rotating the gear of the meter component. This fuel amount is shown on the user interface of the fuel dispensing terminal and transmitted to a computing device within a gas station to display how much fuel the user is dispensing from the fuel dispensing terminal. The fuel dispensing system within the fuel dispensing terminal is pressurized at a constant pressure. As a result, the fuel flow rate from the nozzle of the fuel dispensing terminal remains constant regardless of how fast or slow the pulser rod is rotating. A malicious actor may be able to manipulate the pulser rod to rotate slower than a predetermined known speed. For example, a malicious device that rotates the pulser rod slower than a known speed may be installed or positioned adjacent to the pulser rod within the housing of the fuel dispensing terminal. The malicious device can be, for example, a mechanical device. In the same or another example, the malicious device may be an electronic device including a microchip, a processor, and / or a circuit board that is remotely controllable via wireless communication, such as Bluetooth®. For example, a malicious actor may be able to remotely turn on the malicious device from their user device (e.g., smartphone) when within the wireless communication range (e.g., Bluetooth communication range) of the malicious device installed within the fuel dispensing terminal. When the malicious device is turned on (or otherwise made operable), it manipulates the pulser rod to rotate slower than a known speed.

[0006] When the pulsar rod is operated to rotate slower than a predetermined known speed, the meter component is also operated to measure a faulty fuel volume that is less than the actual fuel volume being supplied from the nozzle of the fuel supply terminal. In other words, when the pulsar rod is operated to rotate slower than a predetermined known speed, the actual amount of fuel being supplied from the nozzle of the fuel supply terminal is more than what the meter component measures. The reading of the meter component is displayed on the user interface and is used to measure how much fuel is being supplied at a given time, for example, every second, every 5 seconds, etc. Thus, a malicious actor can operate the fuel supply terminal without causing a warning in the current fuel supply system by changing the fuel flow measurement. This operation degrades the operation and performance of the components of the fuel supply terminal.

[0007] In some cases, a malicious device can damage the pulsar rod, the meter component, and / or other components of the fuel supply terminal. For example, a malicious device can shorten the half-life of the pulsar rod, the meter component, and / or other components of the fuel supply terminal. In some cases, when a malicious device is installed within the housing of the fuel supply terminal, one or more components of the fuel supply terminal can be physically damaged. For example, a malicious actor can damage the access cover and / or other components of the fuel supply terminal in order to access the interior of the fuel supply terminal to install a malicious device. In the same or a different example, during and / or during the operation of the installation of a malicious device, a malicious actor or malicious device can physically and / or operationally damage one or more components of the fuel supply terminal.

[0008] The disclosed system provides some technical solutions to the above-mentioned technical problems by implementing technical solutions for detecting anomalies at the fuel supply terminal. For example, by detecting the case where a malicious device is used to operate the pulsar rod, an abnormal (or malicious) fuel supply operation can be stopped before its completion (or at an early stage of the process). In other words, in response to detecting the case of an abnormal fuel supply operation in which the fuel supply terminal is operated, the disclosed system is configured to automatically stop the fuel supply operation at the operated fuel supply terminal.

[0009] Thus, the system, in contrast to existing fuel supply systems, is incorporated into practical applications that stop, reduce, and / or prevent unauthorized access to fuel while an abnormal fuel supply operation is in progress. This, in turn, provides an additional practical application of protecting and conserving fuel from unauthorized access.

[0010] In one embodiment, the system comprises a memory and a processor. The memory is configured to store a per unit time threshold volume (fuel dispensing operation) parameter associated with the fuel supplied from a fuel supply terminal during a fuel supply operation. The per unit time threshold volume parameter is configurable. The memory is further configured to store a value indicating a threshold wait period. The processor is operably coupled to the memory. The processor detects a first fuel supply operation indicating that fuel is being supplied from the fuel supply terminal. The processor performs the following operations at each predetermined interval from among a plurality of predetermined intervals within the threshold wait period. The processor determines an identifier value associated with the volume of fuel supplied from the fuel supply terminal. The processor determines a measured volume per unit time parameter associated with the fuel supplied from the fuel supply terminal by dividing the determined identifier value by a unit parameter. The processor compares the measured volume per unit time parameter with the per unit time threshold volume parameter. The processor determines that the measured volume per unit time parameter is less than the per unit time threshold volume parameter. In response to determining that the measured volume per unit time parameter is less than the per unit time threshold volume parameter, the processor communicates to the fuel supply terminal an electronic signal instructing the fuel supply terminal to stop the fuel supply. Detection of Positions Associated with Abnormal Fuel Supply Operations within the Network of a Gasoline Station

[0011] The disclosed system contemplates a system and method for detecting locations associated with abnormal fuel supply operations within a network of gas stations. The disclosed system is configured to detect an abnormal fuel supply operation while such an abnormal fuel supply operation is in progress, as described above. The disclosed system is further configured to detect an abnormal fuel supply operation after completion. In response to detecting an abnormal fuel supply operation, the disclosed system may perform the following operations to address the abnormality and reduce such instances of abnormality across the network of gas stations.

[0012] In response to detecting abnormal fuel supply operations across multiple gas stations within a network of gas stations, a marked or tagged "hot spot" gas station is detected where most of the abnormal fuel supply operations that occur are detected. Thus, the disclosed system provides comprehensive and useful information for allocating more computer resources to the marked gas stations to further improve the security, efficiency, and quality of those operations. For example, in response to detecting a gas station that is marked as a target for a malicious actor to perform a malicious fuel supply, the abnormal detection technology of the disclosed system may be implemented in the local controller and / or fuel supply terminal at the marked gas station. Thus, the disclosed system provides additional practical uses for improving the allocation and utilization of computer resources across the network of gas stations.

[0013] In this way, malicious attempts to affect the fuel supply at the marked gas station are detected and can be stopped during operation (or at an early stage of operation, e.g., seconds after an abnormal fuel supply has started). This deters malicious actors from targeting gas stations for future malicious fuel supplies. This improves the security, efficiency, and quality of the operation of such gas stations.

[0014] Accordingly, the disclosed system is incorporated into additional practical applications that improve the underlying operation of the fuel supply system at marked gas stations within a network of gas stations.

[0015] Furthermore, the disclosed system is incorporated into additional practical applications that improve the underlying operation of fuel supply terminals. For example, since the number of abnormal fuel supply operations is reduced (by implementing the disclosed system), there will be fewer malicious devices installed (or attempted to be installed) inside the fuel supply terminal. This results in fewer instances of physical damage and performance degradation of the components of the fuel supply terminal, improving the half-life and underlying operation of the fuel supply terminal.

[0016] In response to detecting an abnormal fuel supply operation, the disclosed system may perform the following operations to address the abnormality to be pursued and investigated. The disclosed system may retrieve a video feed indicating when and where the abnormal fuel supply operation occurred. For example, a gas station may include security cameras installed at different positions facing the fuel supply terminal. The cameras may capture a video feed of the fuel supply terminal. The disclosed system may retrieve the video feed from the camera facing the fuel supply terminal where the abnormal fuel supply operation occurred. The disclosed system may create a file for the abnormal fuel supply operation. The disclosed system may store the video feed in the created file. The disclosed system may store in the created file other information including, inter alia, user information associated with the abnormal fuel supply operation and vehicle information associated with the vehicle involved in the abnormal fuel supply operation. The disclosed system may communicate the created file to authorities, third parties, and law enforcement agencies to investigate the user, vehicle, and abnormal fuel supply operation.

[0017] In one embodiment, the system includes a memory and a processor. The memory is configured to store a threshold volume parameter per unit time associated with the fuel supplied from a fuel supply terminal during a fuel supply operation, and the threshold volume parameter per unit time is configurable. The processor is operably coupled to the memory. The processor determines an interaction period during which a fuel supply operation is performed at the fuel supply terminal. The processor determines the volume of fuel supplied from the fuel supply terminal during the interaction period. The processor determines a measured volume parameter per unit time associated with the fuel supplied from the fuel supply terminal by dividing the determined volume of fuel by the interaction period. The processor compares the measured volume parameter per unit time with the threshold volume parameter per unit time. The processor determines that the measured volume parameter per unit time is less than the threshold volume parameter per unit time. In response to determining that the measured volume parameter per unit time is less than the threshold volume parameter per unit time, the processor determines a timestamp window associated with the fuel supply operation. The processor extracts a video feed showing the fuel supply terminal during the timestamp window, and the video feed is captured by a camera facing the space where the fuel supply terminal is located. The processor creates a file for the fuel supply operation. The processor stores the video feed in the file associated with the fuel supply operation.

[0018] Certain embodiments of the present disclosure may include some, all, or none of these advantages. These advantages and other features will be more clearly understood from the following detailed description in conjunction with the accompanying drawings and the claims.

Brief Description of the Drawings

[0019] For a more complete understanding of the present disclosure, reference is made to the following brief description in conjunction with the accompanying drawings and the mode for carrying out the invention, and like reference numerals represent like parts.

Figure 1A

Figure 1B

Figure 1C

Figure 1D

Figure 2

Figure 3

Figure 4

Figure 5

[0020] As described above, the prior art cannot provide an efficient and reliable solution for detecting anomalies at a fuel supply terminal during and after a fuel supply operation, and for detecting the locations associated with abnormal fuel supply operations within the network of a gas station. Embodiments of the present disclosure and their advantages can be understood by referring to FIGS. 1A - 5. FIGS. 1A - 5 are used to illustrate a system and method for detecting anomalies at a fuel supply terminal during and after a fuel supply operation, and for detecting the locations associated with abnormal fuel supply operations within the network of a gas station. System Overview

[0021] Figures 1A through 1D illustrate an embodiment of a system 100 generally configured to perform anomaly detection at a fuel supply terminal 102 during and / or after a fuel supply operation and to detect a location associated with an abnormal fuel supply operation within a network of a gas station. FIG. 1A shows the components of the system 100. In a particular embodiment, the system 100 includes one or more fuel supply terminals 102, a local controller 140, a remote controller 180, and a third party 190 communicatively coupled to each other via a network 111. The network 111 enables communication between the components of the system 100.

[0022] The local controller 140 includes a processor 142 that communicates with a memory 146. When executed by the processor 142, the memory 146 stores software instructions 148 that cause the local controller 140 to perform one or more operations described herein. For example, when the software instructions 148 are executed, the local controller 140 may perform the following operations at each of a plurality of predetermined intervals 196 within a threshold waiting period 154 for a fuel supply operation 160. In particular, the local controller 140 may determine an identifier value 194 associated with the volume 156 of fuel supplied from the fuel supply terminal 102 during the interval 196. The local controller 140 may determine a measured fuel volume per unit time parameter 150 associated with the fuel supplied (and / or being supplied) from the fuel supply terminal 102, where the measured fuel volume per unit time parameter 150 may be determined by dividing the determined identifier value 194 of the volume of fuel 156 by a unit parameter 192 (e.g., the cost of fuel per unit volume of fuel). The local controller 140 may compare the measured fuel volume per unit time parameter 150 with a threshold fuel volume per unit time parameter 152. The local controller 140 may determine whether the measured fuel volume per unit time parameter 150 is less than the threshold fuel volume per unit time parameter 152. In response to determining that the measured fuel volume per unit time parameter 150 is less than the threshold fuel volume per unit time parameter 152, the local controller 140 may communicate to the fuel supply terminal 102 an electronic signal 158 instructing the fuel supply terminal 102 to stop the fuel supply. In response thereto, the local controller 140 may determine that the fuel supply operation 160 is associated with an abnormality indicating a discrepancy between the measured fuel volume per unit time parameter 150 and the threshold fuel volume per unit time parameter 152.In other words, an anomaly may indicate that the measured fuel volume parameter 150 per unit time is less than the threshold fuel volume parameter 152 per unit time. In other embodiments, system 100 may not have all of the listed components and / or may have other elements instead of or in addition to those listed above.

[0023] Fuel supply terminal 102 includes a processor 112 that communicates with memory 116 in a signal manner. Memory 116 stores software instructions 118 that, when executed by fuel supply terminal 102, cause fuel supply terminal 102 to perform one or more operations described herein. In certain embodiments, the operations described above in connection with local controller 140 may be performed by fuel supply terminal 102. For example, when software instructions 118 are executed by processor 112, fuel supply terminal 102 may perform the operations described above in connection with local controller 140, and processor 112 may trigger an electronic signal 158 that includes an instruction to stop fuel supply.

[0024] Remote controller 180 includes a processor 182 that communicates with memory 186 in a signal manner. Memory 186 stores software instructions 188 that, when executed by processor 182, cause remote controller 180 to perform one or more operations described herein. In certain embodiments, the operations described above in connection with local controller 140 may be performed by remote controller 180. For example, when software instructions 188 are executed by processor 182, remote controller 180 may perform the operations described above in connection with local controller 140. FIG. 1B shows an exemplary configuration of fuel supply terminal 102. FIG. 1C shows an exemplary configuration of local controller 140. FIG. 1D shows an exemplary configuration of remote controller 180.

[0025] The conventional technology is not configured to detect an anomaly associated with the fuel supply terminal 102, which can indicate a discrepancy between the measured volume parameter 150 per unit time and the threshold volume parameter 152 per unit time. The conventional fuel supply terminal 102 has a pulsar rod component 120 configured to rotate when fuel is supplied from the fuel supply terminal 102. When the pulsar rod 120 rotates, it rotates the mechanical gears of a meter component 122 configured to measure and determine how much fuel is being supplied at a given timestamp.

[0026] When the user starts pumping fuel from the fuel supply terminal 102 into the vehicle, the pulsar rod 120 within the fuel supply terminal 102 begins to rotate, rotating the gears of the meter component 122. This fuel amount is shown on the user interface 108 of the fuel supply terminal 102 and is also transmitted to a computing device within a physical location (e.g., the gas station 104) to display to the user how much fuel is being supplied from the fuel supply terminal 102.

[0027] The fuel supply system 110 within the fuel supply terminal 102 is pressurized at a constant pressure. As a result, the fuel flow rate from the nozzle of the fuel supply terminal 102 remains constant regardless of how fast or slow the pulsar rod 120 is rotating. A malicious actor may manipulate the pulsar rod 120 to rotate slower than a predetermined known speed. For example, a malicious device that rotates the pulsar rod 120 slower than a known speed may be installed adjacent to the pulsar rod 120. The malicious device may be, for example, a mechanical device. In the same or another example, the malicious device may be an electronic device including a microchip, a processor, and / or a circuit board that can be remotely controlled via wireless communication, such as Bluetooth (registered trademark). For example, a malicious actor may be able to remotely turn on the malicious device from their user device (e.g., a smartphone) when within the wireless communication range (e.g., within the Bluetooth communication range) of the malicious device installed within the fuel supply terminal 102. When the malicious device is turned on (or otherwise made operable), the pulsar rod 120 is manipulated to rotate slower than a known speed.

[0028] When the pulsar rod 120 is manipulated to rotate slower than a predetermined known speed, the meter component 122 is also manipulated to determine a fraudulent fuel volume that is less than the actual fuel volume being supplied from the nozzle of the fuel supply terminal 102. In other words, when the pulsar rod 120 is manipulated to rotate slower than a predetermined known speed, the actual fuel amount being supplied from the nozzle of the fuel supply terminal 102 is more than what the meter component 122 determines (i.e., the actual fuel amount being supplied from the nozzle of the fuel supply terminal 102 exceeds the fraudulent fuel amount determined by the meter component 122). Thus, a malicious actor can operate the fuel supply terminal 102 without triggering a warning in the current fuel supply system by altering the fuel flow rate measurement by the meter component. This operation degrades the operation and performance of the components of the fuel supply terminal 102.

[0029] In some cases, a malicious device may damage the pulsar rod 120, the meter component 122, and / or other components of the fuel supply terminal 102. For example, a malicious device may shorten the half-life of the pulsar rod 120, the meter component 122, and / or other components of the fuel supply terminal 102.

[0030] In some cases, when a malicious device is installed within the housing of the fuel supply terminal 102, one or more components of the fuel supply terminal 102 may be damaged. For example, a malicious actor may damage the lid of the inlet to the interior of the fuel supply terminal 102 in order to enable the installation of a malicious device. In the same or another example, during and / or during the operation of the malicious device, the malicious device may physically and / or operationally damage one or more components of the fuel supply terminal 102.

[0031] The system 100 is configured to detect when the pulsar rod 120 is operated to rotate slower than a known or expected speed. The system 100 provides some technical solutions to the above technical problems by implementing technical solutions for detecting anomalies in the fuel supply terminal 102.

[0032] For example, by detecting when a malicious device is used to operate the pulsar rod 120, a malicious fuel supply operation can be stopped before its completion (or at an early stage of the process).

[0033] Accordingly, system 100 can reduce (or prevent) unauthorized access to fuel supply terminal 102 and fuel by communicating an electronic signal 158 to fuel supply terminal 102 that instructs fuel supply terminal 102 to stop fuel supply. Accordingly, system 100 is incorporated into a practical application for stopping, reducing, and / or preventing fuel loss while a malicious fuel supply operation is in progress. This, in turn, provides an additional practical application for protecting and conserving fuel from unauthorized access. In the present disclosure, a malicious fuel supply operation may be interchangeably referred to as an abnormal fuel supply operation.

[0034] System 100 further provides an additional practical application for improving the underlying operation of fuel supply system 110. For example, by detecting malicious fuel supply operations across multiple gas stations 104, a tagged or marked "hot spot" gas station 104 is detected where an abnormal number of malicious fuel supply operations 160 occur. Accordingly, system 100 provides useful information for allocating more computer resources to the marked gas stations 104 to further improve the security of those operations. For example, in response to a malicious actor detecting a gas station 104 that is a mark for a malicious fuel supply, the anomaly detection techniques of system 100 disclosed herein may be implemented in the local controller 140 (and / or remote controller 180 and / or fuel supply terminal 102) at the marked gas station 104. In this way, an attempt at malicious fuel supply at the marked fueling station 104 can be detected and stopped during operation (or at an early stage of operation, e.g., seconds after a malicious fuel supply has started). This can deter malicious actors from targeting gas station 104 for future malicious fuel supply. Accordingly, system 100 is incorporated into an additional practical application for improving the efficiency of allocating computer resources to the gas stations 104 that most require computer resources across the network of gas stations 104.

[0035] Furthermore, system 100 is incorporated into additional practical applications that improve the underlying operation of fuel supply terminal 102. For example, since the number of malicious fuel supply operations is reduced (by implementing system 100), there will be fewer malicious devices installed (or attempted to be installed) inside fuel supply terminal 102. As a result, physical and operational damage to the components of fuel supply terminal 102 is reduced (or minimized).

[0036] In certain embodiments, local controller 140 can be an endpoint device configured to execute an anomaly detection process and determine whether there is a discrepancy between measured fuel volume parameter 150 per unit time and threshold fuel volume parameter 152 per unit time, similar to that briefly described above and more detailed below in relation to operation flow 200 of FIG. 2 and operation flow 300 of FIG. 3.

[0037] In certain embodiments, remote controller 180 can be an endpoint device configured to execute an anomaly detection process and determine whether there is a discrepancy between measured fuel volume parameter 150 per unit time and threshold fuel volume parameter 152 per unit time.

[0038] In certain embodiments, fuel supply terminal 102 can be an endpoint device configured to perform anomaly detection and determine whether there is a discrepancy between measured fuel volume parameter 150 per unit time and threshold fuel volume parameter 152 per unit time. System Components Fuel Supply Terminal

[0039] The fuel supply terminal 102 is in the first position 103. For example, the fuel supply terminal 102 can be located on the premises of a gas station or a fueling station 104. The fuel supply terminal 102 is configured to supply fuel to a user and communicate information between the user and the local controller 140 (or the remote controller 180). Examples of the fuel supply terminal 102 in operation are described in FIGS. 2 and 3. In the present disclosure, the fuel supply terminal 102 may alternatively be referred to as a fuel supply device.

[0040] The fuel supply terminal 102 includes a user interface 108, a fuel supply system 110, a processor 112, a network interface 124, and a memory 116. The components of the fuel supply terminal 102 are operably coupled to each other using any suitable type of wired or wireless connection.

[0041] The user interface 108 is typically located in the upper half of the fuel supply terminal 102 for easy access by user interaction. However, in some cases, the user interface 108 may be in any other suitable location on the fuel supply terminal 102. The user interface 108 has components with which a user can interact. The user interface 108 can include a display screen, a keypad, a touchpad, buttons, a card reader, a card scanner, any suitable component, or any number and combination of suitable components. A user can initiate a request for fuel to be supplied from the fuel supply terminal 102 by presenting a document (e.g., a card) to the user interface 108. The document is scanned by the user interface 108. Information from the document can be transmitted to the local controller 140, a computing device monitored by personnel at the gas station 104, and / or the remote controller 180 for validation. When the information is verified, the user's request is granted.

[0042] The user interface 108 is configured to send a control signal to the fuel supply system 110 to control how fuel is supplied to the user. For example, the user interface 108 may be configured to send a service request 172 to request a fuel service from the user. For example, the user may request a fuel service by swiping or inserting their card into the fuel supply terminal 102 to provide their card information to the fuel supply terminal 102. In response to the transmission of the service request 172, the user may receive an authorization token indicating that the user has been approved for the fuel service. In other words, receiving the authorization token indicates that the fuel supply terminal 102 is authorized to supply fuel to the user. The user interface 108 is further configured to send a control signal to the fuel supply system 110 to control the flow of fuel to the user in response to receiving the authentication token.

[0043] The user interface 108 is further configured to exchange information between the user and the local controller 140. The user interface 108 signal communicates with the local controller 140 using any suitable type of wired or wireless connection. For example, the user interface 108 and the local controller 140 may signal communicate with each other using an Ethernet (registered trademark) cable or a WiFi connection, for example via the network 111. The user interface 108 is configured to send a service request 172 to the remote controller 180 to request information and present the requested information to the user.

[0044] When the flow of fuel starts from the nozzle of the fuel supply terminal 102, the fuel flow rate and the cost of the fuel service are determined by the meter component 122 within the housing of the fuel supply terminal 102 (either alone or in combination with other components) at specific intervals (e.g., every 5 seconds, every 6 seconds, etc.). This information may be communicated from the fuel supply terminal 102 to the local controller 140.

[0045] The local controller 140 can use this information to determine the measured fuel volume parameter 150 per unit time and the threshold fuel volume parameter 152 per unit time, and determine whether there is a discrepancy between these parameters 150 and 152. This operation will be described in more detail below in relation to the operation flow 200 of FIG. 2 and the operation flow 300 of FIG. 3.

[0046] The user interface 108 is further configured to exchange information between the user and the remote controller 180. The user interface 108 signal communicates with the remote controller 180 using the network 111. The user interface 108 is further configured to exchange information between the user and the third party 190. The user interface 108 signal communicates with the third party 190 using the network 111. The third party 190 may include authorities, law enforcement agencies, etc.

[0047] The user interface 108 may include a display, a speaker, a printer, buttons, switches, a keypad, a touch screen, a touch pad, a card reader, a microphone, a camera (e.g., camera 106), a network interface (e.g., network interface 114), or any other suitable type of hardware.

[0048] The fuel supply system 110 is typically located in the lower half of the fuel supply terminal 102 for connection to a fuel pipe and / or an underground fuel storage tank. However, in some cases, the fuel supply system 110 may be at any other suitable location on the fuel supply terminal 102. The fuel supply system 110 may include hydraulic pressure, pumps, motors, piping, ventilation systems, switches, electronics, any other suitable components, or any suitable number and combination of components. The fuel supply system 110 is configured to control how fuel is supplied from the nozzle of the fuel supply terminal 102 to the user based on control signals from the user interface 108. For example, the fuel supply system 110 may be configured to receive a first control signal that triggers the fuel supply system 110 to initiate the flow of fuel to the user and a second control signal that triggers the fuel supply system 110 to terminate the flow of fuel to the user. The fuel supply system 110 may be configured to implement any suitable protocol for supplying fuel.

[0049] Processor 112 comprises one or more processors operably coupled to memory 116. Processor 112 can be any electronic circuit including, but not limited to, a state machine, one or more central processing unit (CPU) chips, logic units, cores (e.g., multi-core processors), field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), or digital signal processors (DSPs). For example, the one or more processors may be implemented in a cloud device, a server, a virtual machine, etc. Processor 112 may be a programmable logic device, a microcontroller, a microprocessor, or any suitable number of the foregoing and combinations thereof. The one or more processors are configured to process data and may be implemented in hardware or software. For example, processor 112 may be 8-bit, 16-bit, 32-bit, 64-bit, or any other suitable architecture. Processor 112 may include an arithmetic logic unit (ALU) for performing arithmetic and logical operations, registers for supplying operands to the ALU and storing the results of ALU operations, and a control unit for fetching instructions from memory and executing them by directing the coordinated operation of the ALU, registers, and other components. The one or more processors are configured to implement various instructions. For example, the one or more processors are configured to execute instructions (e.g., software instructions 118) for implementing processor 112. Thus, processor 112 can be a dedicated computer designed to implement the functions disclosed herein. In one embodiment, processor 112 is implemented using a logic unit, FPGA, ASIC, DSP, or any other suitable hardware. Processor 112 is configured to operate as described in FIGS. 1A-5. For example, processor 112 can be configured to perform one or more operations of method 400 as described in FIG. 4, and one or more operations of method 500 as described in FIG. 5.

[0050] The network interface 114 is configured to enable wired and / or wireless communication. The network interface 114 may be configured to communicate data between the fuel supply terminal 102 and other devices, systems, or domains such as the local controller 140, the remote controller 180, and the third party 190. For example, the network interface 114 may include an NFC interface, a Bluetooth® interface, a Zigbee® interface, a Z-Wave interface, a radio frequency identification (RFID) interface, a WIFI interface, a local area network (LAN) interface, a wide area network (WAN) interface, a metropolitan area network (MAN) interface, a personal area network (PAN) interface, a wireless PAN (WPAN) interface, a modem, a switch, and / or a router. The processor 112 may be configured to transmit and receive data using the network interface 114. The network interface 114 may be configured to use any suitable type of communication protocol.

[0051] Memory 116 can be volatile or non-volatile and can include read-only memory (ROM), random access memory (RAM), ternary content-addressable memory (TCAM), dynamic random access memory (DRAM), and static random access memory (SRAM). Memory 116 can include one or more of a local database, a cloud database, network-attached storage (NAS), etc. Memory 116 includes one or more disks, tape drives, or solid state drives and is used as an overflow data storage device to store such programs when a program is selected for execution and to store instructions and data read during program execution. Memory 116 can store any of the information described in FIGS. 1A-5 along with any other data, instructions, logic, rules, or code operable to implement the functions (s) described herein when executed by processor 112. Referring to FIG. 1B, memory 116 can store software instructions 118, measured volume parameter 150 per unit time, threshold volume parameter 152 per unit time, threshold waiting period 154, volume of fuel 156, electronic signal 158, fuel supply operation 160, video feed 162, timestamp window 164, user information 166, vehicle information 168, file 170, service request 172, user profile 174, average volume per unit time parameter 176, event log 178, unit parameter 192, identifier value 194, machine learning algorithm 195, interaction period 302, amount of fuel supplied 304, and / or any other data or instructions. Software instructions 118 can include any suitable set of instructions, logic, rules, or code operable to cause processor 112 to execute functions described herein, such as some or all of those described in FIGS. 1A-5. The measured fuel volume parameter 150 per unit time can represent the measured amount of fuel pumped per unit time (e.g., per minute, per second, per five seconds, etc.) by meter 122.The threshold volume parameter 152 per unit time is configurable and can indicate the minimum fuel volume per unit time (e.g., per minute, per second, per five seconds, etc.), so that when the measured fuel volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, it is determined that the fuel supply operation 160 is abnormal. The threshold waiting period 154 can be configurable. The threshold waiting period 154 can depend on past fuel supply operations and the past period taken to determine whether past fuel supply operations were abnormal. The fuel volume 156 indicates the amount of fuel supplied from the fuel supply terminal 102. The fuel volume 156 can be in units such as gallons, liters, etc. The electronic signal 158 can include instructions to turn off the fuel supply terminal 102 and / or close the valve of the fuel supply terminal 102. The unit parameter 192 can represent the fuel cost per unit fuel volume (e.g., fuel cost per gallon, fuel cost per liter, etc.). The identifier value 194 can represent the cost for the volume of fuel supplied from the fuel supply terminal 102. Camera

[0052] Referring back to FIG. 1A, the gas station 104 can include one or more cameras 106 and / or can be associated with one or more cameras 106. For example, one or more cameras 106 can be installed at different locations of the gas station 104 to monitor the fuel supply terminals 102 and their operations. The camera 106 can face the space where the fuel supply terminal 102 is located. In certain embodiments, each fuel supply terminal 102 can include a camera 106, and the camera 106 is configured to capture a video feed 162 of the environment in front of (and around) the fuel supply terminal 102 to record the fuel supply operation 160.

[0053] Camera 106 can be, or can include, any camera configured to capture video and images of its previous field of view. Examples of camera 106 can include a charge-coupled device (CCD) camera and a complementary metal-oxide semiconductor (CMOS) camera. Camera 106 can be configured to capture a video feed 162 (and / or an image feed 162) of the space where fuel supply terminal 102 is located. Camera 106 is a hardware device configured to capture video and images continuously, at predetermined intervals, or on demand. Camera 106 is communicatively coupled via network 111 to components of system 100 including local controller 140, remote controller 180, and fuel supply terminal 102.

[0054] Camera 106 is configured to communicate the captured video feed 162 to local controller 140. Local controller 140 may use the captured video feed 162 when detecting users and vehicles involved in malicious fuel supply operations that operate the pusher rod 120 to rotate slower than a known speed, creating an unauthorized fuel supply flow rate lower than the actual fuel flow rate exiting the nozzle of fuel supply terminal 102. Camera 106 is configured to communicate the captured video feed 162 to any other component of system 100 including remote controller 180. For example, remote controller 180 may use the captured video feed 162 when detecting users and vehicles involved in malicious fuel supply operations. Camera 106 is configured to communicate the captured video feed 162 to fuel supply terminal 102. For example, fuel supply terminal 102 may use the captured video feed 162 when detecting users and vehicles involved in malicious fuel supply operations. The operations of leveraging the captured video feed 162 are described in more detail in FIG. 2 in relation to operation flow 200 and in FIG. 3 in relation to operation flow 300. Network

[0055] Network 111 can be any suitable type of wireless and / or wired network. Network 111 is not connected to the Internet or a public network. Network 111 can include all or part of an intranet, a peer-to-peer network, a switched telephone network, a LAN, a WAN, a MAN, a PAN, a WPAN, an overlay network, a software-defined network (SDN), a virtual private network (VPN), a cellular phone network (e.g., a cellular network such as 4G or 5G), a plain old telephone (POT) network, a wireless data network (e.g., WiFi, WiGig, WiMAX, etc.), a long-term evolution (LTE) network, a universal mobile telecommunications system (UMTS) network, a peer-to-peer (P2P) network, a Bluetooth® network, a near field communication (NFC) network, and / or any other suitable network not connected to the Internet. Network 111 can be configured to support any suitable type of communication protocol, as would be understood by one of ordinary skill in the art. Local Controller

[0056] Local controller 140 is at the first location 103. Local controller 140 can be any suitable network device or server (e.g., a client or proxy server) configured to communicate data with fuel supply terminal 102, remote controller 180, and third party 190. Local controller 140 can be formed by one or more physical devices configured to provide services and resources (e.g., data and / or hardware resources) to fuel terminal device 102 at the first location 103.

[0057] In certain embodiments, the local controller 140 may communicate data received from the fuel supply terminal 102 to the remote controller 180. In other words, the local controller 140 may communicate data between the fuel supply terminal 102 and the remote controller 180. For example, the local controller 140 may be a proxy server that functions as an intermediary for exchanging data between the fuel supply terminal 102 and the remote controller 180. Examples of the local controller 140 in operation are described in FIGS. 2 and 3. The local controller 140 and the remote controller 180 may signal communicate with each other via the network 111.

[0058] The local controller 140 includes a processor 142 operably coupled to a network interface 144 and a memory 146. The processor 142 includes one or more processors operably coupled to the memory 146. The processor 142 can be any electronic circuit including, but not limited to, a state machine, one or more CPU chips, a logic unit, a core (e.g., a multi-core processor), an FPGA, an ASIC, or a DSP. For example, one or more processors may be implemented in a cloud device, a server, a virtual machine, etc. The processor 142 may be a programmable logic device, a microcontroller, a microprocessor, or any suitable combination thereof. One or more processors are configured to process data and can be implemented in hardware or software. For example, the processor 142 can be an 8-bit, 16-bit, 32-bit, 64-bit, or any other suitable architecture. The processor 142 may include an ALU for performing arithmetic and logical operations, registers for supplying operands to the ALU and storing the results of ALU operations, and a control unit for fetching instructions from memory and executing them by directing the coordinated operation of the ALU, registers, and other components. One or more processors are configured to implement various instructions. For example, one or more processors are configured to execute instructions (e.g., software instructions 148) for implementing the processor 142. Thus, the processor 142 can be a dedicated computer designed to implement the functions disclosed herein. In one embodiment, the processor 142 is implemented using a logic unit, an FPGA, an ASIC, a DSP, or any other suitable hardware. The processor 142 is configured to operate as described in FIGS. 1A-5. For example, the processor 142 can be configured to execute one or more operations of method 400 as described in FIG. 4 and one or more operations of method 500 as described in FIG. 5.

[0059] The network interface 144 is configured to enable wired and / or wireless communication. The network interface 144 may be configured to communicate data between the local controller 140 and other devices, systems, or domains such as the remote controller 180, the fuel supply terminal 102, and the third party 190. For example, the network interface 144 may include an NFC interface, a Bluetooth® interface, a Zigbee interface, a Z-Wave interface, an RFID interface, a WIFI interface, a LAN interface, a WAN interface, a MAN interface, a PAN interface, a WPAN interface, a modem, a switch, and / or a router. The processor 142 may be configured to transmit and receive data using the network interface 144. The network interface 144 may be configured to use any suitable type of communication protocol.

[0060] Memory 146 can be volatile or non - volatile and can include ROM, RAM, TCAM, DRAM, and SRAM. Memory 146 can include one or more of a local database, a cloud database, a NAS, etc. Memory 146 includes one or more disks, tape drives, or solid - state drives and is used as an overflow data storage device to store such programs when a program is selected for execution and to store the instructions and data read during program execution. Memory 146 can store any of the information described in FIGS. 1A - 5 along with any other data, instructions, logic, rules, or code operable to implement the functions (s) described herein when executed by processor 142. Referring to FIG. 1C, memory 146 can store software instructions 148, measurement volume parameter 150 per unit time, threshold volume parameter 152 per unit time, threshold waiting period 154, volume of fuel 156, electronic signal 158, fuel supply operation 160, video feed 162, timestamp window 164, user information 166, vehicle information 168, file 170, service request 172, user profile 174, average volume parameter 176 per unit time, event log 178, unit parameter 192, identifier value 194, machine - learning algorithm 195, interaction period 302, supplied fuel quantity 304, and / or any other data or instructions. Software instructions 148 can include any suitable set of instructions, logic, rules, or code operable to cause processor 142 to execute functions described herein, such as some or all of those described in FIGS. 1A - 5. Other elements are described with respect to FIGS. 1A, 1B, and 2 - 5. Remote Controller

[0061] Remote controller 180 is at a second location 105 that is remote from (e.g., geographically different from) the first location 103. Remote controller 180 can be any suitable network device or server.

[0062] In certain embodiments, remote controller 180 may be implemented by a cluster of computing devices located in a remote server farm. For example, remote controller 180 may be implemented by a plurality of computing devices using a distributed computing system and / or a cloud computing system. Remote controller 180 may be implemented by a plurality of computing devices within one or more data centers. Remote controller 180 may be formed by one or more physical devices configured to provide services and resources (e.g., data and / or hardware resources) to system 100.

[0063] The remote controller 180 includes a processor 182 operably coupled to a network interface 184 and a memory 186. The processor 182 includes one or more processors operably coupled to the memory 186. The processor 182 is any electronic circuit including, but not limited to, a state machine, one or more CPU chips, a logic unit, a core (e.g., a multi-core processor), an FPGA, an ASIC, or a DSP. For example, the one or more processors may be implemented in a cloud device, a server, a virtual machine, or the like. The processor 182 may be a programmable logic device, a microcontroller, a microprocessor, or any suitable combination thereof. The one or more processors are configured to process data and may be implemented in hardware or software. For example, the processor 182 may be 8-bit, 16-bit, 32-bit, 64-bit, or any other suitable architecture. The processor 182 may include an ALU for performing arithmetic and logical operations, registers for supplying operands to the ALU and storing the results of ALU operations, and a control unit for fetching instructions from memory and executing them by directing the coordinated operation of the ALU, registers, and other components. The one or more processors are configured to implement various instructions. For example, the one or more processors are configured to execute instructions (e.g., software instructions 188) for implementing the processor 182. Thus, the processor 182 may be a dedicated computer designed to implement the functions disclosed herein. In one embodiment, the processor 182 is implemented using a logic unit, an FPGA, an ASIC, a DSP, or any other suitable hardware. The processor 182 is configured to operate as described with reference to FIGS. 1A-5. For example, the processor 182 may be configured to execute one or more operations of method 400 as described in FIG. 4 and one or more operations of method 500 as described in FIG. 5.

[0064] The network interface 184 is configured to enable wired and / or wireless communication. The network interface 184 can be configured to communicate data between the remote controller 180 and other devices, systems, or domains such as the local controller 140, the fuel supply terminal 102, and the third party 190. For example, the network interface 184 can include an NFC interface, a Bluetooth® interface, a Zigbee interface, a Z-Wave interface, an RFID interface, a WIFI interface, a LAN interface, a WAN interface, a MAN interface, a PAN interface, a WPAN interface, a modem, a switch, and / or a router. The processor 182 can be configured to transmit and receive data using the network interface 184. The network interface 184 can be configured to use any suitable type of communication protocol.

[0065] Memory 186 can be volatile or non-volatile and can include ROM, RAM, TCAM, DRAM, and SRAM. Memory 186 can include one or more of a local database, a cloud database, a NAS, etc. Memory 186 includes one or more disks, tape drives, or solid state drives and is used as an overflow data storage device to store such programs when a program is selected for execution and to store instructions and data read during program execution. Memory 186 can store any of the information described in FIGS. 1A-5, along with any other data, instructions, logic, rules, or code operable to implement the function(s) described herein when executed by processor 182. Referring to FIG. 1D, memory 186 can store software instructions 188, measured volume parameter 150 per unit time, threshold volume parameter 152 per unit time, threshold waiting period 154, volume of fuel 156, electronic signal 158, fuel supply operation 160, video feed 162, timestamp window 164, user information 166, vehicle information 168, file 170, service request 172, user profile 174, average volume parameter 176 per unit time, event log 178, unit parameter 192, identifier value 194, machine learning algorithm 195, interaction period 302, amount of fuel supplied 304, and / or any other data or instructions. Software instructions 188 can include any suitable set of instructions, logic, rules, or code operable to cause processor 182 to execute and perform the function(s) described herein, such as some or all of those described in FIGS. 1A-5. Other elements are described with respect to FIGS. 1A, 1B, and 2-5.

[0066] The remote controller 180 is configured to provide instructions for operating and managing the fuel supply terminal 102. For example, the remote controller 180 may be configured to store software instructions 118 (e.g., included in a configuration file) and upload them to the fuel supply terminal 102. The software instructions 118 include instructions for configuring the hardware and / or software of the fuel supply terminal 102. Examples of the software instructions 118 include, but are not limited to, firmware updates, BIOS updates, and software updates. The remote controller 180 may be configured to upload the software instructions 118 to one or more fuel supply terminals 102 periodically or on demand. The remote controller 180 may be configured to upload updated software instructions 118 to the fuel supply terminal 102 in response to detecting an abnormal fuel supply operation at the same or different fuel supply terminals 102 of the gas station 104.

[0067] For example, the remote controller 180 may provide updated software instructions 118 installed in the processor 112 of the fuel supply terminal 102, which, when executed by the processor 112, cause the processor 112 to implement the anomaly detection techniques described herein, i.e., for a given fuel supply operation 160, determine whether there is a discrepancy between the measured fuel volume parameter 150 per unit time and the threshold fuel volume parameter 152 per unit time, and in response to detecting a discrepancy indicating that the measured fuel volume parameter 150 per unit time is less than the threshold fuel volume parameter 152 per unit time, instruct the fuel supply terminal 102 to perform one or more operations. For example, the one or more operations may include communicating an electronic signal 158 instructing the fuel supply terminal 102 to stop fuel supply, retrieving a video feed 162 indicating the space in which the fuel supply terminal 102 is located during the time stamp window of the fuel supply operation 160, retrieving user information 166 from card data provided by the user, retrieving vehicle information 168 from the video feed 162, generating a file 170 including the video feed 162, user information 166, vehicle information 168, and / or any other appropriate information within the file 170, and communicating the file 170 to a third party 190 to investigate the malicious fuel supply operation 160. The third party 190 may include authorities, law enforcement agencies, etc. These operations are described in more detail in relation to the operation flow 200 of FIG. 2 and the operation flow 300 of FIG. 3.

[0068] The remote controller 180 may be configured to download and store the event log 178 from the fuel supply terminal 102. The event log 178 includes information regarding the operation history of the fuel supply terminal 102. For example, the event log 178 may include information such as the amount of fuel supplied, the volume of fuel supplied per interval 196, the card data used in connection with starting the service request 172, the timestamp duration of the fuel supply operation 160 in the fuel supply terminal 102, the fuel flow rate, the video feed 162, and / or any other type of information associated with the fuel supply terminal 102. The remote controller 180 may be configured to periodically request and / or receive the event log information. For example, the remote controller 180 may be configured to receive the event log information every 30 seconds, every minute, every 30 minutes, every hour, or at any suitable time interval.

[0069] The remote controller 180 may be configured to receive the request 172 when the user operates the fuel supply terminal 102 to start fuel supply. The user may provide their card data to the personnel of the fuel supply terminal 102 or the gas station 104. The user may provide their card data physically or from their mobile device. The user's request 172 may include user information 166 associated with the user. The user information 166 may include the name, address, and number (e.g., card number) associated with the user.

[0070] The user request 172 is transmitted to the local controller 140 to request a fuel service for the user. The local controller 140 is configured to identify the user information 166 associated with the user in the user request 172 from the card data.

[0071] The local controller 140 is configured to determine the identity of the user using the user information 166. For example, the local controller 140 may use the user information 166 to identify a user profile 174 associated with the user. The local controller 140 may search for a user profile 174 that includes matching user information 166 using the user information 166. The user profile 174 may further include other information associated with the user. For example, the user profile 174 may include personal information, card information, interaction history information, alternative identifiers, or any other suitable type of information associated with the user. In response to verifying the identity of the user, the user request 172 may be permitted, and the user may be able to initiate a fuel supply operation 160 at the fuel supply terminal 102.

[0072] In certain embodiments, the operation of verifying the identity of the user may be performed by any suitable number and combination of the fuel supply terminal 102, the local controller 140, and the remote controller 180. In particular, while the above operation has been described as being performed by the local controller 140, it should be understood that alternatively or additionally, it may be performed by the remote controller 180, the fuel supply terminal 102, or any suitable number and combination of these components. Exemplary Operation Flow for Detecting Abnormalities during Fuel Supply Operations

[0073] FIG. 2 shows an exemplary operation flow 200 of the system 100 of FIG. 1A for detecting anomalies during the fuel supply operation 160 at the fuel supply terminal 102. An anomaly may indicate a malicious attempt to manipulate a component of the fuel supply terminal 102 (e.g., the pulsar rod 120) to create an unauthorized fuel supply flow that is lower than the actual fuel flow rate exiting the nozzle of the fuel supply terminal 102.

[0074] The operation flow 200 can start when the user starts the fuel supply operation 160. For example, the user parks the vehicle at the fuel supply terminal 102. The user can start the request 172, for example, by presenting the user's card data to the fuel supply terminal 102. The user can be verified by the local controller 140, the fuel supply terminal 102, and / or the remote controller 180 in the same manner as described in FIG. 1A. The local controller 140 can detect that the fuel supply operation 160 has started. For example, when the user is approved (verified), the user can start the operation of the fuel supply terminal 102. In response to this, fuel begins to flow from the nozzle of the fuel supply terminal 102. This fuel flow rate is communicated from the fuel supply terminal 102 to the local controller 140. This indicates that the fuel supply operation 160 has started. Determination of the Measured Volume Parameter per Unit Time

[0075] The local controller 140 is configured to determine the measured fuel volume parameter 150 per unit time. In a particular embodiment, to determine the measured fuel volume parameter 150 per unit time, the local controller 140 can perform specific measurements and calculations within the threshold waiting period 154. The threshold waiting period 154 can be settable by an operator, for example. The threshold waiting period 154 can be 10 minutes, 8 minutes, 9 minutes, or any other suitable period.

[0076] In response to detecting the fuel supply operation 160, the local controller 140 can perform the following operations at each predetermined interval 196 from among a plurality of predetermined intervals 196 within the threshold waiting period 154. The predetermined interval 196 can be 5 seconds, 10 seconds, or any other suitable interval.

[0077] The local controller 140 may determine the volume 156 of fuel supplied from the fuel supply terminal 102. By the end of the threshold waiting period 154, the local controller 140 has determined an aggregate value of the volume of fuel pumped (i.e., supplied) from the fuel supply terminal 102. This aggregate value of the supplied fuel 156 can be created and manipulated as a result of a malicious actor manipulating the pusher rod 120 of the fuel supply terminal 102, similar to that described in FIG. 1A. In other words, this aggregate value of the supplied fuel 156 may be incorrect (i.e., manipulated) if a malicious actor manipulates the pusher rod component 120 to rotate more slowly and may not represent the expected amount of fuel pumped over the duration of the threshold waiting period 154. The local controller 140 may determine a measured volume parameter 150 per unit time associated with the fuel supplied from the fuel supply terminal 102 by dividing an identifier value 194 associated with the determined fuel volume 156 by a unit parameter 192.

[0078] In certain embodiments, the local controller 140 may wait for a specific period (e.g., 10 seconds, 15 seconds, or any other suitable period) from when the fuel begins to flow and determine the volume 156 of fuel per interval 196 and the measured volume parameter 150 per unit time. This is because, in some cases, when the fuel begins to flow out of the fuel supply terminal 102, it may take some time for the fuel flow rate to reach a steady state of flow through a transition state. By waiting for a specific period and then performing the operations described above, the accuracy of the measured volume parameter 150 per unit time may be improved.

[0079] In certain embodiments, the operations for determining the measured volume parameter 150 per unit time described herein may be performed by the remote controller 180. The remote controller 180 may be configured to determine the measured fuel volume parameter 150 per unit time. When the fuel supply operation 160 starts, the fuel supply terminal 102 and / or the local controller 140 may communicate a message indicating that the fuel supply operation 160 has started to the remote controller 180. The fuel supply terminal 102 and / or the local controller 140 may communicate the volume 156 of fuel supplied per interval 196 to the remote controller 180. The remote controller 180 may perform certain measurements and calculations within the threshold waiting period 154 to determine the measured volume parameter 150 per unit time, similar to what is described above. In certain embodiments, the remote controller 180 may wait for a specific period (e.g., 10 seconds, 15 seconds, or any other suitable period) starting when the fuel begins to flow to determine the volume 156 of fuel per interval 196 and the measured volume parameter 150 per unit time.

[0080] In certain embodiments, the operations for determining the measured volume parameter 150 per unit time described herein may be performed by the fuel supply terminal 102. The fuel supply terminal 102 may be configured to determine the measured fuel volume parameter 150 per unit time. When the fuel supply operation 160 starts, the fuel supply terminal 102 may determine the volume 156 of fuel supplied per interval 196, for example, via one or more sensors. The fuel supply terminal 102 may perform certain measurements and calculations within the threshold waiting period 154 to determine the measured volume parameter 150 per unit time, similar to what is described above. In certain embodiments, the fuel supply terminal 102 may wait for a specific period (e.g., 10 seconds, 15 seconds, or any other suitable period) starting when the fuel begins to flow to determine the volume 156 of fuel per interval 196 and the measured volume parameter 150 per unit time. Determination of Whether the Fuel Supply Operation is Malicious

[0081] The local controller 140 can determine whether the fuel supply operation 160 is malicious. To determine whether the fuel supply operation 160 is malicious (i.e., the determined fuel volume 156 is being manipulated), the local controller 140 can compare the measured fuel volume parameter 150 per unit time with the threshold volume parameter 152 per unit time.

[0082] The threshold volume parameter 152 per unit time can be determined based on past fuel supply operations at the fuel supply terminal 102 when it is known that the pulsar rod 120, the meter component 122, and other components of the fuel supply terminal 102 are operating as expected, i.e., when the fuel supply terminal 102 is not being operated by a malicious actor to cause the pulsar rod 120 to rotate slower than a known speed. For example, the threshold volume parameter 152 per unit time can be determined under safe and monitored conditions when the fuel supply terminal 102 is not being operated. If the local controller 140 determines that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, the local controller 140 can determine that the fuel supply operation 160 is malicious (or abnormal) and that the fuel supply terminal 102 is being operated by a malicious actor. For example, this can be the result of a malicious actor installing a malicious device inside the housing of the fuel supply terminal 102 to manipulate the pulsar rod 120 to rotate slower than a known speed, thereby causing the measured fuel flow rate calculated by the meter of the fuel supply terminal 102 to be less than the expected fuel flow rate over the duration of the threshold waiting period 154.

[0083] In response to determining that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, the local controller 140 may determine that the fuel supply operation 160 is associated with an abnormality indicating that the measured fuel volume parameter 150 per unit time is less than the threshold fuel volume parameter 152 per unit time. In another example, the abnormality may indicate unauthorized access to the fuel.

[0084] In certain embodiments, in response to determining that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, the local controller 140 may communicate a warning message indicating that the fuel supply operation 160 is associated with an abnormality and is malicious. For example, the local controller 140 may communicate the warning message to, among other things, the computing device of the gas station 104, the remote controller 180, and / or a third party 190 (e.g., a law enforcement agency). For example, an operator of the gas station 104 may receive the warning message and come to the fuel supply terminal 102 to investigate.

[0085] If the local controller 140 determines that the measured volume parameter 150 per unit time is greater than (or equal to) the threshold volume parameter 152 per unit time, the local controller 140 may determine that the fuel supply operation 160 is not malicious and not abnormal.

[0086] The following corresponding description describes a specific example of determining the measured volume parameter 150 per unit time. In certain embodiments, the volume of fuel 156 may be measured in gallons, the measured volume parameter 150 per unit time may be the actual gallon measurement per minute, the threshold volume parameter 152 per unit time may be measured in gallons per minute, the unit parameter 192 may be the cost of fuel per gallon, and the identifier value 194 may represent the cost of the fuel for the amount of fuel supplied. An example of a plurality of identifier values 194 associated with the amount of fuel 156 pumped per interval 196 is shown in Table 1.

Table 1

[0087] The numbers in Table 1 are exemplary and are not meant to limit the scope of the present disclosure. For illustration purposes, only rows 1 to 11 are shown in Table 1. As can be seen from the exemplary Table 1, the aggregated identifier value 194 at the end of the threshold waiting period 154 is 1.09. The measured volume parameter 150 per unit time can be determined by Equation (1).

Number

[0088] X is the measured volume parameter 150 per unit time, ∂ is the identifier value 194, and θ is the unit parameter 192.

[0089] In this specific example, assume that the fuel cost per gallon is 1.299, the interval 196 is 5 seconds, and the threshold gallons per minute is 1.0. In this specific example, X can be calculated as follows:

Number

[0090] In certain embodiments, the operations for determining whether the fuel supply operation 160 described herein is malicious may be performed by the remote controller 180. For example, the remote controller 180 may compare the measured fuel volume parameter 150 per unit time with the threshold volume parameter 152 per unit time. If the remote controller 180 determines that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, the remote controller 180 may determine that the fuel supply operation 160 is malicious (or abnormal) and that the fuel supply terminal 102 is being operated by a malicious actor. Otherwise, the remote controller 180 may determine that the fuel supply operation 160 is not malicious and not abnormal.

[0091] In certain embodiments, in response to determining that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, the remote controller 180 may communicate a warning message indicating that the fuel supply operation 160 is abnormally associated and is malicious. For example, the remote controller 180 may communicate the warning message to, among other things, the computing device of the gas station 104, the local controller 140, and / or a third party 190 (e.g., a law enforcement agency).

[0092] In certain embodiments, the operations for determining whether the fuel supply operation 160 described herein is malicious may be performed by the fuel supply terminal 102. For example, the fuel supply terminal 102 may compare the measured fuel volume parameter 150 per unit time with the threshold volume parameter 152 per unit time. If the fuel supply terminal 102 determines that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, the fuel supply terminal 102 may determine that the fuel supply operation 160 is malicious (or abnormal) and that the fuel supply terminal 102 is being operated by a malicious actor. Otherwise, the fuel supply terminal 102 may determine that the fuel supply operation 160 is not malicious and not abnormal.

[0093] In certain embodiments, in response to determining that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, the fuel supply terminal 102 may communicate a warning message indicating that the fuel supply operation 160 is abnormally associated and is malicious. For example, the fuel supply terminal 102 may communicate the warning message to, among other things, the computing device of the gas station 104, the local controller 140, the remote controller 180, and / or a third party 190 (e.g., a law enforcement agency). Instruct the Fuel Supply Terminal to Stop Fuel Supply

[0094] If the local controller 140 determines that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, the local controller 140 may communicate to the fuel supply terminal 102 an electronic signal 158 instructing the fuel supply terminal 102 to stop the fuel supply. This operation may be performed during a malicious fuel supply operation 160. Thus, in this way, the local controller 140 is configured to reduce, minimize (or prevent) unauthorized access to the fuel while a malicious fuel supply operation 160 is in progress.

[0095] In certain embodiments, the electronic signal 158 may turn off the fuel supply terminal 102. For example, when executed by the processor 112 (see FIG. 1A), the electronic signal 158 may include a fuel end command that shuts down one or more associated components of the fuel supply terminal 102 (see FIG. 1A) such that the fuel supply terminal 102 stops fuel supply. In such embodiments, a technician may inspect the fuel supply terminal 102 and remove any malicious devices (if any remain inside the fuel supply terminal 102 by a malicious actor) from inside the fuel supply terminal 102 and repair the fuel supply terminal 102 as needed.

[0096] In certain embodiments, the electronic signal 158 may close one or more valves used to control the flow of fuel exiting the nozzle of the fuel supply terminal 102. This stops the fuel pump. In such embodiments, after ending and stopping a malicious fuel supply operation 160 and deterring a malicious actor from performing another malicious fuel supply, the fuel supply terminal 102 may operate as expected when a subsequent user approaches and attempts to perform a legitimate fuel supply operation 160.

[0097] In certain embodiments, the electronic signal 158 may include a command to take the fuel supply terminal 102 out of service for future operations. For example, the fuel supply terminal 102 may be taken out of service until further notice after repair or until the investigation and / or inspection by a technician is complete. In the same or another example, an existing code may be triggered to take the fuel supply terminal 102 out of service until a technician comes to the site and enters a code indicating, for example, that the fuel supply terminal 102 has been inspected.

[0098] In certain embodiments, the operation for instructing the fuel supply terminal 102 to stop the fuel supply, as described herein, may be performed by the remote controller 180. When the remote controller 180 determines that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, the remote controller 180 may communicate an electronic signal 158 to the fuel supply terminal 102 instructing the fuel supply terminal 102 to stop the fuel supply. This operation may be performed during the malicious fuel supply operation 160. Thus, in this way, the remote controller 180 is configured to reduce, minimize (or prevent) unauthorized access to the fuel while the malicious fuel supply operation 160 is in progress.

[0099] In certain embodiments, the operation for instructing the fuel supply terminal 102 to stop the fuel supply, as described herein, may be performed by the fuel supply terminal 102 itself. In other words, the fuel supply terminal 102 may be configured to execute software instructions 118 that, when executed by the processor 112, trigger or cause the processor 112 to communicate an electronic signal 158 to the fuel supply system 110 instructing the fuel supply system 110 to stop the fuel supply. For example, when the fuel supply terminal 102 determines that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, the processor 112 may communicate an electronic signal 158 to the fuel supply system 110 instructing the fuel supply system 110 to stop the fuel supply. This operation may be performed during the malicious fuel supply operation 160. Thus, in this way, the fuel supply terminal 102 is configured to reduce, minimize (or prevent) unauthorized access to the fuel while the malicious fuel supply operation 160 is in progress. Generation of Files for Investigating Malicious Fuel Supply Operations

[0100] The local controller 140 may be configured to generate a file 170 and include information in the file 170 that can be used to investigate the malicious fuel supply operation 160.

[0101] In certain embodiments, in response to determining that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, the local controller 140 may retrieve a video feed 162 showing the fuel supply terminal 102 during a malicious fuel supply operation 160. In this process, the local controller 140 may determine a timestamp window 164 associated with the malicious or abnormal fuel supply operation 160. The timestamp window 164 indicates the start time and stop time of the fuel supply operation 160. The local controller 140 may retrieve the video feed 162 showing the fuel supply terminal 102 within the timestamp window 164. The local controller 140 may retrieve the video feed 162 from the camera 106 facing the space where the fuel supply terminal 102 is located. For example, the video feed 162 may be communicated from the camera 106 to the local controller 140 in response to the local controller 140 sending a retrieval request to the camera 106. In another example, the camera 106 may communicate the video feed 162 to the local controller 140 in real time, periodically, or on demand.

[0102] The local controller 140 may generate a file 170 and store it in the memory 146. The file 170 may be associated with the fuel supply operation 160. The local controller 140 stores the video feed 162 in the generated file 170.

[0103] The local controller 140 may include any other appropriate information in the file 170. For example, the local controller 140 may retrieve user information 166 associated with the fuel supply operation 160. The local controller 140 may determine the user information 166 from the request 172 in the same manner as described above in FIG. 1A. The user information 166 may be retrieved from a data card (presented by the user) used in relation to starting the fuel supply operation 160 and verifying the identity of the user. The local controller 140 may store the user information 166 in the generated file 170.

[0104] In another example, the local controller 140 may include vehicle information 168 in the file 170. The vehicle information 168 may include the type, model number, model name, and license plate number associated with the vehicle involved in the fuel supply operation 160.

[0105] For example, the local controller 140 may supply the video feed 162 to a machine learning algorithm 195 configured to identify the vehicle information 168 from the video feed 162. The machine learning algorithm 195 may be implemented by a processor 142 that executes software instructions 148. The machine learning algorithm 195 may include, among other things, image processing, text processing, and object recognition. The machine learning algorithm 195 may be implemented by a plurality of neural network layers, convolutional neural network layers, long short-term memory (LSTM) layers, bidirectional LSTM layers, recurrent neural network layers, and the like.

[0106] The local controller 140 may store the vehicle information 168 in the generated file 170. In certain embodiments, the local controller 140 may also include in the file 170 the measured volume parameter 150 per unit time, the threshold volume parameter 152 per unit time, and any other data / information. The local controller 140 may transmit the file 170 used to investigate the user, the vehicle, and the fuel supply operation 160 to a third party 190 (e.g., among others, the authorities, law enforcement agencies).

[0107] In certain embodiments, the operations for generating file 170 described herein may be performed by remote controller 180. For example, in response to determining that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, remote controller 180 may extract video feed 162 and determine user information 166 and vehicle information 168, similar to that described above with respect to local controller 140. Remote controller 180 may include video feed 162, user information 166, and vehicle information 168, and / or any other data associated with fuel supply operation 160 within file 170. Remote controller 180 may send file 170, which is used to investigate the user, vehicle, and fuel supply operation 160, to third party 190.

[0108] In certain embodiments, the operations for generating file 170 described herein may be performed by fuel supply terminal 102. For example, in response to determining that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, fuel supply terminal 102 may extract video feed 162 and determine user information 166 and vehicle information 168, similar to that described above with respect to local controller 140. Fuel supply terminal 102 may include video feed 162, user information 166, and vehicle information 168, and / or any other data associated with fuel supply operation 160 within file 170. Fuel supply terminal 102 may send file 170, which is used to investigate the user, vehicle, and fuel supply operation 160, to third party 190. Detection of Subsequent Malicious Fuel Supply Operations

[0109] The local controller 140 may perform further operations that can escalate the situation when a subsequent abnormal fuel supply operation 160 is detected within a specific threshold period from the first or initial abnormal fuel supply operation 160. For example, after determining that the first fuel supply operation 160 is malicious or abnormal and the fuel pump is stopped (similar to what was described above), a malicious actor may try again and attempt to request a second fuel supply operation 160.

[0110] The local controller 140 may perform the operations described above regarding the first fuel supply operation 160 to determine whether the second fuel supply operation 160 is malicious or abnormal. For example, assume that the local controller 140 detects a second fuel supply operation 160 indicating that fuel is being supplied from the fuel supply terminal 102, where the second fuel supply operation 160 is detected within a specific threshold period (e.g., within 1 minute, 2 minutes, 10 minutes, 12 minutes, etc.) after the first fuel supply operation 160 is detected.

[0111] If the local controller 140 determines that the second fuel supply operation 160 is also malicious or abnormal (i.e., the measured volume parameter 150 per second unit is less than the threshold volume parameter 152 per second unit), the local controller 140 may communicate a second electronic signal 158 to the fuel supply terminal 102 instructing it to stop the fuel supply. The local controller 140 may also communicate a warning message indicating that the first and second fuel supply operations 160 are malicious and / or abnormal. For example, the local controller 140 may communicate the warning message to the remote controller 180, a third party 190, and / or any other entity. For example, in response to receiving the warning message, law enforcement may arrive at the fuel supply terminal 102 and question the user about the malicious fuel supply operation 160.

[0112] In certain embodiments, the operations for detecting subsequent malicious fuel supply operations 160, as described herein, may be performed by remote controller 180. Remote controller 180 may be configured to perform further operations that escalate the situation when a subsequent abnormal fuel supply operation 160 is detected within a specific threshold period from the first or initial abnormal fuel supply operation 160.

[0113] Remote controller 180 may perform the operations described above with respect to the first fuel supply operation 160 to determine whether the second fuel supply operation 160 is malicious or abnormal. Assume that remote controller 180 detects a second fuel supply operation 160 indicating that fuel is being supplied from fuel supply terminal 102, where the second fuel supply operation 160 is detected within a specific threshold period (e.g., within 1 minute, 2 minutes, 10 minutes, 12 minutes, etc.) after the first fuel supply operation 160 is detected.

[0114] If remote controller 180 determines that the second fuel supply operation 160 is also malicious or abnormal (i.e., the measured volume parameter 150 per unit time of the second is less than the threshold volume parameter 152 per unit time), remote controller 180 may communicate a second electronic signal 158 to fuel supply terminal 102 instructing it to stop the fuel supply. Remote controller 180 may also communicate a warning message indicating that the first and second fuel supply operations 160 are malicious and / or abnormal. For example, remote controller 180 may communicate the warning message to local controller 140, third party 190, and / or any other entity. For example, in response to receiving the warning message, law enforcement may arrive at fuel supply terminal 102 and question the user about the malicious fuel supply operation 160.

[0115] In certain embodiments, the operations for detecting subsequent malicious fuel supply operations 160 described herein may be performed by the fuel supply terminal 102. The fuel supply terminal 102 may be configured to perform further operations that escalate the situation when a subsequent abnormal fuel supply operation 160 is detected within a specific threshold period from the first or initial abnormal fuel supply operation 160.

[0116] The fuel supply terminal 102 may perform the operations described above with respect to the first fuel supply operation 160 to determine whether the second fuel supply operation 160 is malicious or abnormal. Assume that the fuel supply terminal 102 detects a second fuel supply operation 160 indicating that fuel is being supplied from the fuel supply terminal 102, where the second fuel supply operation 160 is detected within a specific threshold period (e.g., within 1 minute, 2 minutes, 10 minutes, 12 minutes, etc.) after the first fuel supply operation 160 is detected.

[0117] If the fuel supply terminal 102 determines that the second fuel supply operation 160 is also malicious or abnormal (i.e., the measured volume parameter 150 per unit time of the second fuel supply operation 160 is less than the threshold volume parameter 152 per unit time), the fuel supply terminal 102 may implement a second electronic signal 158 to instruct the fuel supply system 110 to stop the fuel supply. The fuel supply terminal 102 may also communicate a warning message indicating that the first and second fuel supply operations 160 are malicious and / or abnormal. For example, the fuel supply terminal 102 may communicate the warning message to the local controller 140, the remote controller 180, a third party 190, and / or any other entity. For example, in response to receiving the warning message, law enforcement agencies may arrive at the fuel supply terminal 102 and question the user about the malicious fuel supply operation 160. Reduction of False Detection of Malicious Fuel Supply Operations

[0118] The local controller 140 can be configured to reduce false detection of malicious (i.e., abnormal) fuel supply operations 160. In certain embodiments, the local controller 140 can use the average fuel volume parameter 176 per unit time from a previous (e.g., most recent) fuel supply operation 160.

[0119] The local controller 140 can determine a plurality of measured fuel volume parameters 150 per unit time from a plurality of previous fuel supply operations 160 (e.g., the previous 5 fuel supply operations 160, the previous 10 fuel supply operations 160, etc.). The plurality of measured fuel volume parameters 150 per unit time can be stored in the event log 178.

[0120] The local controller 140 can determine the average fuel volume parameter 176 per unit time by averaging the plurality of measured fuel volume parameters 150 per unit time. The local controller 140 can compare the average volume parameter 176 per unit time with the measured volume parameter 150 per unit time.

[0121] If the local controller 140 determines that the average volume parameter 176 per unit time exceeds the measured volume parameter 150 per unit time by a threshold (e.g., one-third, 1, 2, 5, 10, or any other suitable value), the local controller 140 can determine that the fuel supply operation 160 is abnormally associated and is malicious. In other words, if the local controller 140 determines that the measured volume parameter 150 per unit time is significantly reduced compared to the average volume parameter 176 per unit time, it determines that the fuel supply operation 160 is abnormal and / or malicious. In this way, the local controller 140 can use the average volume parameter 176 per unit time as additional information for verifying and evaluating the fuel supply operation 160. Thereby, the accuracy of the abnormal detection process for the fuel supply operation 160 is improved.

[0122] In certain embodiments, the local controller 140 can change the duration of the threshold waiting period 154 and determine whether the measured volume parameter 150 per unit time determined at the end of various threshold waiting periods 154 is greater than or less than the threshold volume parameter 152 per unit time. In this way, a more comprehensive and accurate result of evaluating the determined measured volume parameter 150 per unit time can be obtained.

[0123] In certain embodiments, the local controller 140 can be configured not to stop the fuel flow until two or more low-speed fuel flows (e.g., flows less than the threshold volume parameter 152 per unit time) occur within X minutes, where X can be 1, 2, 3, etc.

[0124] In certain embodiments, after detecting a first low-speed fuel flow and stopping the fuel flow, a warning message can be displayed on the user interface 108 of the fuel supply terminal 102 (see FIG. 1A). The warning message can indicate that the fuel flow is unexpectedly low. After seeing the warning message, a legitimate user can inform the operator of the gas station 104 (see FIG. 1A) and / or use another fuel supply terminal 102. A malicious actor may continue another malicious fuel supply operation 160 even after seeing the warning message. Therefore, if multiple low-speed fuel flows are detected within X minutes, it can be further confirmed that the fuel supply operation 160 is abnormal and not just a failure of the fuel supply terminal 102 that requires regular repair.

[0125] The operation flow 200 is described as being executed by the local controller 140. However, those skilled in the art will understand other embodiments in light of the present disclosure. For example, the operation flow 200 may be executed by the fuel supply terminal 102 performing some or all of the fuel supply operation 160. In this example, the fuel supply terminal 102 determines the measured volume parameter 150 per unit time, compares it with the threshold volume parameter 152 per unit time, determines whether the fuel supply operation 160 is abnormal, stops the fuel supply if the fuel supply operation 160 is abnormal, extracts the video feed 162, creates the file 170, includes the video feed 162, user information 166, and vehicle information 168 in the file 170, and may communicate it to the third party 190.

[0126] In another example, the operation flow 200 may be executed by the remote controller 180. In this example, the remote controller 180 determines the measured volume parameter 150 per unit time, compares it with the threshold volume parameter 152 per unit time, determines whether the fuel supply operation 160 is abnormal, stops the fuel supply if the fuel supply operation 160 is abnormal, extracts the video feed 162, creates the file 170, includes the video feed 162, user information 166, and vehicle information 168 in the file 170, and may communicate it to the third party 190.

[0127] In certain embodiments, the anomaly detection process (i.e., detecting malicious fuel supply operation 160) may be executed by the remote controller 180 from data transferred from the fuel supply terminal 102 and / or the local controller 140, where the data includes, but is not limited to, the volume of fuel 156 per interval 196.

[0128] In certain embodiments, an electronic signal (e.g., electronic signal 158) that stops the flow of fuel to fuel supply terminal 102 can be transmitted from local controller 140. In certain embodiments, an electronic signal (e.g., electronic signal 158) that stops the flow of fuel to fuel supply terminal 102 can be transmitted from remote controller 180 to local controller 140 and then from local controller 140 to fuel supply terminal 102. In certain embodiments, an electronic signal (e.g., electronic signal 158) that stops the flow of fuel to fuel supply terminal 102 can be transmitted from remote controller 180 to fuel supply terminal 102. In certain embodiments, an electronic signal (e.g., electronic signal 158) that stops the flow of fuel to fuel supply terminal 102 can be transmitted from a computing device at gas station 104 (see FIG. 1A) to fuel supply terminal 102. In certain embodiments, the transmission of an electronic signal that stops the flow of fuel (e.g., in electronic signal 158) can be performed by processor 112 present inside fuel supply terminal 102.

[0129] In certain embodiments, operation 160 for reducing false detection of malicious fuel supply operations, as described herein, can be performed by remote controller 180. For example, remote controller 180 can determine an average fuel volume parameter 150 per unit time from a plurality of previous fuel supply operations 160.

[0130] Remote controller 180 can compare average volume parameter 176 per unit time with measured volume parameter 150 per unit time. If remote controller 180 determines that average volume parameter 176 per unit time exceeds measured volume parameter 150 per unit time by a threshold (e.g., one third, 1, 2, 5, 10, or any other suitable value), remote controller 180 can determine that fuel supply operation 160 is abnormally associated and is malicious.

[0131] In certain embodiments, the remote controller 180 can change the duration of the threshold waiting period 154 and determine whether the measured volume parameter 150 per unit time determined at the end of various threshold waiting periods 154 is greater than or less than the threshold volume parameter 152 per unit time.

[0132] In certain embodiments, the remote controller 180 can be configured not to stop the fuel flow until two or more low-speed fuel flows (e.g., flows less than the threshold volume parameter 152 per unit time) occur within X minutes, where X can be 1, 2, 3, etc.

[0133] In certain embodiments, the operation 160 for reducing false detection of malicious fuel supply operations described herein can be performed by the fuel supply terminal 102. For example, the fuel supply terminal 102 can determine the average fuel volume parameter 150 per unit time from a plurality of previous fuel supply operations 160.

[0134] The fuel supply terminal 102 can compare the average volume parameter 176 per unit time with the measured volume parameter 150 per unit time. If the fuel supply terminal 102 determines that the average volume parameter 176 per unit time exceeds the measured volume parameter 150 per unit time by a threshold (e.g., one-third, 1, 2, 5, 10, or any other appropriate value), the fuel supply terminal 102 can determine that the fuel supply operation 160 is abnormally associated and is malicious.

[0135] In certain embodiments, the fuel supply terminal 102 can change the duration of the threshold waiting period 154 and determine whether the measured volume parameter 150 per unit time determined at the end of various threshold waiting periods 154 is greater than or less than the threshold volume parameter 152 per unit time.

[0136] In certain embodiments, the fuel supply terminal 102 may be configured not to stop the fuel flow until two or more low fuel flow rates (e.g., flow rates less than the threshold volume parameter 152 per unit time) occur within X minutes, where X can be 1, 2, 3, etc.

[0137] In certain embodiments, the fuel supply terminals 102 may form a mesh network of devices that communicate with each other, e.g., via the network 111 (see FIGURE 1). For example, a malicious actor may attempt to perform a first malicious fuel supply operation 160 at a first fuel supply terminal 102, and the first fuel supply terminal 102, the local controller 140, and / or the remote controller 180 may detect the first malicious fuel supply operation 160 and communicate a first electronic signal 158 to the first fuel supply terminal 102 instructing it to stop fuel supply. In some cases, the malicious actor may attempt a second fuel supply terminal 102. The second fuel supply terminal 102, the local controller 140, and / or the remote controller 180 may determine, based on user information 166, vehicle information 168, and / or other data associated with the user and vehicle, that the same user associated with the first malicious fuel supply operation 160 is attempting to perform a second fuel supply operation 160 at the second fuel supply terminal 102. If the second fuel supply terminal 102, the local controller 140, and / or the remote controller 180 determines that the second fuel supply operation 160 is also abnormal, a second electronic signal 168 may be implemented to instruct the second fuel supply terminal 102 to stop fuel supply. The second fuel supply terminal 102, the local controller 140, and / or the remote controller 180 may communicate a warning message regarding the malicious fuel supply operation 160 by the user to a third party. Exemplary Operation Flow for Detecting Abnormalities after Fuel Supply Operations

[0138] FIG. 3 shows an exemplary operation flow 300 of the system 100 of FIG. 1A for detecting anomalies after a fuel supply operation 160 at the fuel supply terminal 102, where the anomaly can indicate a malicious attempt to manipulate a component of the fuel supply terminal 102 (e.g., the pulsar rod 120) to create an unauthorized fuel supply flow rate lower than the actual fuel flow rate exiting the nozzle of the fuel supply terminal 102.

[0139] In certain embodiments, in the gas station 104 where the operation flow 300 described in FIG. 2 is not deployed to detect an abnormal fuel supply operation 160, the operation flow 200 can be implemented to detect an abnormal fuel supply operation 160 after completion. The results of the operation flow 300 across multiple gas stations 104 within the network of the gas station 104 can be evaluated. In this way, marked gas stations 104 often used by malicious actors to perform malicious fuel supply operations 160 are detected. Accordingly, the system 100 (see FIG. 1A) allocates computer resources and provides useful information for deploying the operation flow 200 at the marked gas stations 104. This improves the security, efficiency, and quality of operations at those gas stations 104.

[0140] The operation flow 300 can start when the user executes the fuel supply operation 160 after being authorized by the components of the system 100, similar to what was described above in FIG. 2. The fuel supply terminal 102 communicates the fuel quantity 156 to the local controller 140 at intervals 196.

[0141] The local controller 140 determines the duration of the interaction period 302 during which the user executes the fuel supply operation 160. The interaction period 302 is the duration during which the fuel supply operation 160 is executed at the fuel supply terminal 102. To determine the interaction period 302, the local controller 140 determines the start time when the fuel begins to flow from the fuel supply terminal 102, the stop time when the fuel flow stops, and determines the difference between the start time and the stop time.

[0142] The local controller 140 determines the volume 156 of fuel supplied from the fuel supply terminal 102 during the interaction period 302. The volume 156 of fuel supplied from the fuel supply terminal 102 may correspond to the total amount of fuel exiting the fuel supply terminal 102.

[0143] The local controller 140 may determine a measured volume parameter 150 per unit time associated with the fuel supplied from the fuel supply terminal 102 by dividing the determined volume 156 of fuel (over the duration of the interaction period 302) by the interaction period 302. To convert the determined measured volume parameter 150 per unit time to a fuel volume per minute, the local controller 140 may divide the determined measured volume parameter 150 per unit time by 60, assuming that the interaction period 302 is in seconds.

[0144] The local controller 140 compares the actual volume parameters 192, 150 per unit with a threshold volume parameter 152 per unit time. If the local controller 140 determines that the measured volume parameter 150 per unit time is greater than the threshold volume parameter 152 per unit time, the local controller 140 determines that the fuel supply operation 160 is not abnormal (i.e., not malicious).

[0145] If the local controller 140 determines that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, the local controller 140 determines that the fuel supply operation 160 is abnormal (i.e., malicious). In this case, the local controller 140 may perform the following operations. For example, the local controller 140 may fetch a video feed 162 indicating the fuel supply terminal 102 in the timestamp window 164 when the fuel supply operation 160 occurred. For this purpose, the local controller 140 may determine the timestamp window 164 in which the fuel supply operation 160 occurred.

[0146] The local controller 140 extracts a video feed 162 that shows the fuel supply terminal 102 within the timestamp window 164. The local controller 140 may extract the video feed 162 from the camera 106 facing the space where the fuel supply terminal 102 is located. For example, the video feed 162 may be communicated from the camera 106 to the local controller 140 in response to the local controller 140 sending an extraction request to the camera 106. In another example, the camera 106 may communicate the video feed 162 to the local controller 140 in real time, periodically, or on demand.

[0147] The local controller 140 may create a file 170 for the fuel supply operation 160 and store it in the memory 146. The local controller 140 stores the video feed 162 in the generated file 170. The local controller 140 may include any other information in the file 170. For example, the local controller 140 may store the user information 166 and the vehicle information 168 in the file 170. The local controller 140 may retrieve and / or determine the user information 166 and the vehicle information 168 in the same manner as described in FIG. 2. Determination of the Actual Amount of Fuel Supplied during a Malicious Fuel Supply Operation

[0148] As described above, during the malicious fuel supply operation 160, the malicious actor operates the fuel supply terminal 102 to tamper with or change the amount of fuel supplied from the fuel supply terminal 102 as measured by the fuel supply terminal 102. The local controller 140 can determine the actual amount of fuel supplied during the malicious fuel supply operation, as described below. The local controller 140 determines the volume of the first fuel available at the fuel supply terminal 102 before the interaction period 302 begins. The volume of the first fuel may represent the total available fuel amount at the gas station 104 before the interaction period 302 is initiated. After the interaction period 302 is completed, the local controller 140 determines the volume of the second fuel available at the fuel supply terminal 102. The volume of the second fuel may represent the total fuel available at the fuel supply terminal 102 after the interaction period 302 is completed. The local controller 140 can determine the amount of fuel before and after the interaction period 302 by checking the fuel tank of the gas station 104 (see FIG. 1A). The local controller 140 determines the difference between the volume of the first fuel and the volume of the second fuel, and the difference between the volume of the first fuel and the volume of the second fuel indicates the actual fuel amount 304 supplied during the fuel supply operation 160 at the fuel supply terminal 102.

[0149] The local controller 140 may store the amount of fuel supplied during the abnormal fuel supply operation 160 in a file 170 associated with the fuel supply operation 160. The local controller 140 may send the file 170 used to investigate the user, vehicle, and fuel supply operation 160 to a third party 190.

[0150] In certain embodiments, the local controller 140 may use the average fuel volume parameter 176 per unit time from previous (e.g., most recent) fuel supply operations 160 as additional information when determining whether the fuel supply operation 160 is abnormal, similar to that described in FIG. 2.

[0151] In certain embodiments, the local controller 140 may wait for a specific time period (e.g., 10 seconds, 15 seconds, or any other suitable period), similar to that described in FIG. 2, to determine the measured volume parameter 150 per unit time.

[0152] In certain embodiments, in response to determining that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, the local controller 140 may communicate a warning message indicating that the fuel supply operation 160 is associated with an anomaly indicating a discrepancy between the measured volume parameter 150 per unit time and the threshold volume parameter 152 per unit time. For example, the local controller 140 may communicate the warning message to the computing device of the gas station 104, the remote controller 180, and / or the third party 190.

[0153] In certain embodiments, in response to determining that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, the local controller 140 may communicate an electronic signal 158 to the fuel supply terminal 102. In one example, the electronic signal 158 may instruct the fuel supply terminal 102 to turn off. In this case, the electronic signal 158 may include an order to put the fuel supply terminal 102 out of service for future operations. For example, the fuel supply terminal 102 may be put out of service until further notice after repair or until the investigation and / or inspection by the technician is completed. In the same or another example, an existing code may be triggered to put the fuel supply terminal 102 out of service until the technician comes to the site and enters a code indicating that the fuel supply terminal 102 has been inspected. In another example, the electronic signal 158 may instruct the fuel supply terminal 102 to close the valve of the fuel supply terminal 102 that controls the fuel flow.

[0154] In certain embodiments, in response to determining that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, the remote controller 180 may communicate an electronic signal 158 to the fuel supply terminal 102.

[0155] In certain embodiments, in response to determining that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, the fuel supply terminal 102 may trigger an electronic signal 158. For example, the processor 112 may trigger the electronic signal 158. The electronic signal 158 may function as a kill switch or turn-off signal to shut down the fuel supply terminal 102, similar to that described above.

[0156] The operation flow 300 is described as being executed by the local controller 140. However, those skilled in the art will understand other embodiments in light of the present disclosure. For example, the operation flow 300 may be executed by the fuel supply terminal 102. In another example, the operation flow 300 may be executed by the remote controller 180. Exemplary Method for Detecting Abnormalities during Fuel Supply Operations

[0157] FIG. 4 shows an exemplary flowchart of method 400 for detecting an anomaly during fuel supply operation 160. Modifications, additions, or omissions may be made to method 400. Method 400 may include more, fewer, or other operations. For example, the operations may be performed in parallel or in any suitable order. Although system 100, local controller 140, remote controller 180, fuel supply terminal 102, or any of their components that perform the operations may be described, any suitable system or system component may perform one or more of the operations of method 400. For example, when one or more of the operations of method 400 are performed at least in part by one or more processors (e.g., processors 112, 142, and 182 of FIG. 1A), they may be implemented in the form of software instructions 118, 148, and 188 of FIG. 1A stored on a non-transitory tangible machine-readable medium (e.g., memories 116, 146, and 186 of FIG. 1A) that cause the one or more processors to execute operations 402-418.

[0158] In operation 402, local controller 140 detects fuel supply operation 160 indicating that fuel is being supplied from fuel supply terminal 102. For example, local controller 140 may detect that fuel supply operation 160 has started when a sensor of the fuel supply terminal indicates that fuel has started flowing from the nozzle of fuel supply terminal 102, similar to that described in FIG. 2.

[0159] In operation 404, local controller 140 selects an interval 196 from among a plurality of intervals 196 within threshold waiting period 154. Local controller 140 may select from interval 196 iteratively and incrementally. For example, assuming that interval 196 is 5 seconds, local controller 140 may select the first 5 seconds of threshold waiting period 154. Local controller 140 may select interval 196 iteratively and incrementally until the end of threshold waiting period 154.

[0160] In operation 406, the local controller 140 determines an identifier value 194 associated with the volume 156 of fuel supplied from the fuel supply terminal 102. In this process, the local controller 140 determines the identifier value 194 supplied since the start of the threshold waiting period 154. For example, in the second iteration where the local controller 140 selects the second interval 196 in operation 404, the local controller 140 may determine an aggregated identifier value 194 associated with the volume 156 of fuel supplied since the start of the threshold waiting period 154.

[0161] In operation 408, the local controller 140 determines a measured volume parameter 150 per unit time associated with the fuel supplied from the fuel supply terminal 102 by dividing the determined identifier value 194 associated with the volume 156 of fuel by the unit parameter 192. An exemplary operation for determining the measured volume parameter 150 per unit time is described in FIG. 2.

[0162] In operation 410, the local controller 140 compares the measured volume parameter 150 per unit time with the threshold volume parameter 152 per unit time. In operation 412, the local controller 140 determines whether the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time. If the local controller 140 determines that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, method 400 proceeds to operation 418. If the local controller 140 determines that the measured volume parameter 150 per unit time is greater than or equal to the threshold volume parameter 152 per unit time, method 400 proceeds to operation 414.

[0163] In operation 414, the local controller 140 determines whether to select another interval 196. If there is another interval 196 remaining until the end of the threshold waiting period 154, the local controller 140 determines to select another interval 196. If the local controller 140 determines to select another interval 196, method 400 returns to operation 404. Otherwise, method 400 proceeds to operation 416.

[0164] In operation 416, the local controller 140 determines that the fuel supply operation 160 is not abnormal. The local controller 140 may analyze the fuel supply operation 160 until the end of the threshold waiting period 154. If the local controller 140 determines that the measured volume parameter 150 per unit time is greater than or equal to the threshold volume parameter 152 per unit time by the end of the threshold waiting period 154, the local controller 140 determines that the fuel supply operation 160 is not abnormal. The local controller 140 is also configured to determine whether it is an abnormal fuel supply operation 160 at any interval 196 within the threshold waiting period 154.

[0165] In operation 418, the local controller 140 communicates an electronic signal 158 to the fuel supply terminal 102 instructing the fuel supply terminal 102 to stop the fuel supply. For example, the local controller 140 may communicate an electronic signal 158 instructing the fuel supply terminal 102 to turn off. In another example, the local controller 140 may communicate an electronic signal 158 to close one or more valves controlling the fuel flow.

[0166] Method 400 is described as being executed by the local controller 140. Those skilled in the art will understand other embodiments in light of the present disclosure. For example, one or more operations of method 400 may be executed by the remote controller 180. In the same or another example, one or more operations of method 400 may be executed by the fuel supply terminal 102. Exemplary Method for Detecting Abnormalities after Fuel Supply Operations

[0167] FIG. 5 shows an exemplary flowchart of a method 500 for anomaly detection after a fuel supply operation 160. Modifications, additions, or omissions may be made to method 500. Method 500 may include more, fewer, or other operations. For example, the operations may be performed in parallel or in any suitable order. Although described as being performed by system 100, local controller 140, remote controller 180, fuel supply terminal 102, or any of their components that perform the operations, any suitable system or system component may perform one or more operations of method 500. For example, one or more operations of method 500 may be implemented in the form of software instructions 118, 148, and 188 of FIG. 1A stored on a non-transitory tangible machine-readable medium (e.g., memories 116, 146, and 186 of FIG. 1A) such that when executed by one or more processors (e.g., processors 112, 142, and 182 of FIG. 1A), the one or more processors may be caused to perform operations 502-522.

[0168] In operation 502, local controller 140 determines that the fuel supply operation 160 at fuel supply terminal 102 has been completed. For example, local controller 140 may determine that the fuel supply operation 160 has been completed when the flow of fuel stops at fuel supply terminal 102 and / or when a sensor of fuel supply terminal 102 indicates that the nozzle has been returned to a predetermined position and the flow has stopped.

[0169] In operation 504, local controller 140 determines an interaction period 302 during which the fuel supply operation 160 is performed at fuel supply terminal 102. Local controller 140 determines the duration of interaction period 302 by determining the difference between the start time and the end time of fuel supply operation 160.

[0170] In operation 506, the local controller 140 determines the volume 156 of fuel supplied from the fuel supply terminal 102 during the interaction period 302. In 508, the local controller 140 divides the determined fuel volume 156 by the interaction period 302 to determine a measured volume parameter 150 per unit time associated with the fuel supplied from the fuel supply terminal 102. Exemplary operations for determining the measured volume parameter 150 per unit time are described in FIG. 3.

[0171] In operation 510, the local controller 140 compares the measured volume parameter 150 per unit time with a threshold volume parameter 152 per unit time. In operation 512, the local controller 140 determines whether the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time. If the local controller 140 determines that the measured volume parameter 150 per unit time is less than the threshold volume parameter 152 per unit time, method 500 proceeds to operation 516. Otherwise, method 500 proceeds to operation 514.

[0172] In operation 514, the local controller 140 determines that the fuel supply operation 160 is not abnormal. In other words, the local controller 140 determines that the fuel supply operation 160 is not malicious, i.e., the fuel supply terminal 102 is not being operated by a malicious actor.

[0173] In operation 516, the local controller 140 determines a time stamp window 164 associated with the fuel supply operation 160. The time stamp window 164 may have the same duration as the interaction period 302. For example, the time stamp window 164 may be included in the event log 178. The time stamp window 164 may indicate the time and calendar date when the fuel supply operation 160 occurred. The local controller 140 may determine the time stamp window 164 from the event log 178.

[0174] In operation 518, the local controller 140 extracts a video feed 162 showing the fuel supply terminal 102 in the time stamp window 164. The local controller 140 may extract the video feed 162 from the camera 106 facing the space where the fuel supply terminal 102 is located.

[0175] In certain embodiments, the video feed 162 among other video recordings by the camera 106 may be stored in the event log 178, and the local controller 140 may extract the video feed 162 from the event log 178. For example, the local controller 140 may search for the video feed 162 based on the metadata associated with the fuel supply operation 160. For example, each fuel supply operation 160 is associated with, among other things, its respective fuel supply terminal 102, time stamp window 164, fuel volume 156, measured volume parameter 150 per unit time, interaction period 302, video feed 162, and may be stored in the event log 178. If the local controller 140 determines that the fuel supply operation 160 is abnormal, the local controller 140 may search the event log 178 to find the video feed 162 showing the fuel supply operation 160 in a specific time stamp window 164 linked to the fuel supply operation 160.

[0176] In operation 520, the local controller 140 creates a file 170 for the fuel supply operation 160. In operation 522, the local controller 140 stores the video feed 162 in the created file 170. The local controller 140 may store other data / information, including user information 166, vehicle information 168, supplied fuel quantity 304, and / or any other appropriate data / information, in the file 170.

[0177] Method 500 is described as being executed by local controller 140. Those skilled in the art will understand other embodiments in light of the present disclosure. For example, one or more operations of method 500 may be executed by remote controller 180. In the same or another example, one or more operations of method 500 may be executed by fuel supply terminal 102.

[0178] Although several embodiments have been provided in the present disclosure, it should be understood that the disclosed systems and methods may be embodied in many other specific forms without departing from the spirit or scope of the present disclosure. This example should be considered illustrative rather than limiting, and its intention should not be limited to the details given herein. For example, various elements or components may be combined or integrated in another system, or certain features may be omitted or not implemented.

[0179] In addition, techniques, systems, subsystems, and methods described and illustrated as discrete or separate in various embodiments may be combined with or integrated into other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items illustrated or described as being coupled or directly coupled or communicating with each other may be indirectly coupled or communicating through some interface, device, or intermediate component in an electrical, mechanical, or other manner. Other examples of changes, substitutions, and modifications will be recognizable by those skilled in the art and may be made without departing from the spirit and scope disclosed herein.

[0180] To assist the Patent Office and any reader of any patent issued on this application in interpreting the claims appended hereto, the applicant hereby states that it is not intended to apply 35 U.S.C. § 112(f) to any of the appended claims, unless the words "means for" or "step for" are expressly used in a particular claim.

Claims

1. A system comprising: a memory configured to store: a threshold volume parameter per unit time associated with fuel supplied from a fuel supply terminal during a fuel supply operation, which is configurable; and a value indicating a threshold waiting period; a processor operably coupled to the memory, the processor configured to: detect a first fuel supply operation indicating that fuel is being supplied from the fuel supply terminal; determine, at each of a plurality of predetermined intervals within the threshold waiting period, an identifier value associated with the volume of fuel supplied from the fuel supply terminal; determine a measured volume parameter per unit time associated with the fuel supplied from the fuel supply terminal by dividing the determined identifier value by the unit parameter; compare the measured volume parameter per unit time with the threshold volume parameter per unit time; determine that the measured volume parameter per unit time is less than the threshold volume parameter per unit time; and in response to determining that the measured volume parameter per unit time is less than the threshold volume parameter per unit time, communicate to the fuel supply terminal an electronic signal instructing the fuel supply terminal to stop fuel supply. A system comprising: A system according to claim 1, wherein the processor is further configured to determine, in response to determining that the measured volume parameter per unit time is less than the threshold volume parameter per unit time, that the first fuel supply operation is associated with an anomaly indicating a discrepancy between the measured volume parameter per unit time and the threshold volume parameter per unit time.

3. The processor is configured to, in response to determining that the measured volume parameter per unit time is less than the threshold volume parameter per unit time: determine a timestamp window associated with the first fuel supply operation; and retrieve a video feed of the fuel supply terminal within the timestamp window, the video feed being captured by a camera facing the space where the fuel supply terminal is located. ​ ​ ​ ​ Create a file for the first fuel supply operation, Store the video feed in the created file The system according to claim 1, further configured to perform.

4. The processor is Retrieve user information associated with the first fuel supply operation, The user information is retrieved from a data card used in connection with the start of the first fuel supply operation, The user information includes at least one of a name, address, or number associated with the user, Retrieve, Store the user information in the created file The system according to claim 3, further configured to perform.

5. The processor is further configured to communicate a warning message indicating that the first fuel supply operation is associated with an abnormality indicating a discrepancy between the measured volume parameter per unit time and the threshold volume parameter per unit time. The system according to claim 1.

6. The processor is Detect a second fuel supply operation indicating that fuel is being supplied from the fuel supply terminal, the second fuel supply operation being detected within a specific threshold period after the first fuel supply operation, Detect, Among the plurality of predetermined intervals within the threshold waiting period, at each predetermined interval, Determine a second identifier value associated with the volume of the second fuel supplied from the fuel supply terminal, By dividing the determined second identifier value by the unit parameter, determine a second measured volume parameter per unit time associated with the fuel supplied from the fuel supply terminal, Compare the second measured volume parameter per unit time with the threshold volume parameter per unit time, Determine that the second measured volume parameter per unit time is less than the threshold volume parameter per unit time, In response to determining that the second measured volume parameter per unit time is less than the threshold volume parameter per unit time, Communicate a second electronic signal to the fuel supply terminal instructing the fuel supply terminal to stop the fuel supply, Communicate a warning message indicating that the first fuel supply operation and the second fuel supply operation are abnormally associated The system according to claim 1, further configured to perform

7. The processor is determining an average volume parameter per unit time associated with the fuel supplied from the fuel supply terminal in a plurality of previous fuel supply operations; comparing the average volume parameter per unit time with the measured volume parameter per unit time; determining that the average volume parameter per unit time exceeds the measured volume parameter per unit time by at least a threshold value; in response to determining that the average volume parameter per unit time exceeds the measured volume parameter per unit time by at least the threshold value, determining that the first fuel supply operation is associated with an abnormality indicating a discrepancy between the measured volume parameter per unit time and the threshold volume parameter per unit time The system according to claim 1, further configured to perform

8. A method comprising: detecting a first fuel supply operation indicating that fuel is being supplied from a fuel supply terminal; from among a plurality of predetermined intervals within a threshold waiting period, at each predetermined interval determining an identifier value associated with the volume of fuel supplied from the fuel supply terminal; determining a measured volume parameter per unit time associated with the fuel supplied from the fuel supply terminal by dividing the determined identifier value by a unit parameter; comparing the measured volume parameter per unit time with a threshold volume parameter per unit time, wherein the threshold volume parameter per unit time is associated with the fuel supplied from the fuel supply terminal during a fuel supply operation, and the threshold volume parameter per unit time is configurable, step; determining that the measured volume parameter per unit time is less than the threshold volume parameter per unit time; communicating to the fuel supply terminal an electronic signal instructing the fuel supply terminal to stop fuel supply in response to determining that the measured volume parameter per unit time is less than the threshold volume parameter per unit time A method comprising.

9. In response to determining that the measured volume parameter per unit time is less than the threshold volume parameter per unit time, the method according to claim 8 further includes the step of determining that the first fuel supply operation is associated with an abnormality indicating a discrepancy between the measured volume parameter per unit time and the threshold volume parameter per unit time.

10. In response to determining that the measured volume parameter per unit time is less than the threshold volume parameter per unit time, the step of determining a time stamp window associated with the first fuel supply operation; the step of extracting a video feed indicating the fuel supply terminal from within the time stamp window, wherein the video feed is captured by a camera facing the space where the fuel supply terminal is located; the step of creating a file for the first fuel supply operation; the step of storing the video feed in the created file and further includes the method according to claim 8.

11. the step of extracting user information associated with the first fuel supply operation, wherein the user information is extracted from a data card used in relation to the start of the first fuel supply operation, and the user information includes at least one of a name, address, or number associated with the user, the step; the step of storing the user information in the created file and further includes the method according to claim 10.

12. The method according to claim 8 further includes the step of communicating a warning message indicating that the first fuel supply operation is associated with an abnormality indicating a discrepancy between the measured volume parameter per unit time and the threshold volume parameter per unit time.

13. The step of instructing the fuel supply terminal to stop fuel supply includes at least one of the step of communicating a first signal to turn off the fuel supply terminal to the fuel supply terminal, or the step of communicating a second signal to close a valve through which fuel is supplied to the fuel supply terminal and further includes the method according to claim 8.

14. The method according to claim 8 further includes the step of waiting for a specific period before determining the measured volume parameter per unit time.

15. A non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to detect a first fuel supply operation indicating that fuel is being supplied from a fuel supply terminal; at each of a plurality of predetermined intervals within a threshold waiting period, determine an identifier value associated with the volume of fuel supplied from the fuel supply terminal; determine a measured volume parameter per unit time associated with the fuel supplied from the fuel supply terminal by dividing the determined identifier value by a unit parameter; compare the measured volume parameter per unit time with a threshold volume parameter per unit time, wherein the threshold volume parameter per unit time is associated with the fuel supplied from the fuel supply terminal during a fuel supply operation, and the threshold volume parameter per unit time is configurable, the comparing; determine that the measured volume parameter per unit time is less than the threshold volume parameter per unit time; in response to determining that the measured volume parameter per unit time is less than the threshold volume parameter per unit time, communicate to the fuel supply terminal an electronic signal instructing the fuel supply terminal to stop the supply of fuel A non-transitory computer-readable medium that causes the above to be performed. **Claim 16** The instructions, when executed by the one or more processors, further cause the one or more processors to determine that the first fuel supply operation is associated with an abnormality indicating a discrepancy between the measured volume parameter per unit time and the threshold volume parameter per unit time, in response to determining that the measured volume parameter per unit time is less than the threshold volume parameter per unit time. The non-transitory computer-readable medium according to claim 15. **Claim 17** The instructions, when executed by the one or more processors, further cause the one or more processors to, in response to determining that the measured volume parameter per unit time is less than the threshold volume parameter per unit time, determine a time stamp window associated with the first fuel supply operation. Retrieving a video feed showing the fuel supply terminal within the timestamp window, wherein the video feed is captured by a camera facing the space where the fuel supply terminal is located; Creating a file for the first fuel supply operation; Storing the video feed in the created file; The non - transitory computer - readable medium according to claim 15, which causes the above to be performed.

18. When the instructions are executed by the one or more processors, the one or more processors are further caused to: Retrieve user information associated with the first fuel supply operation, wherein the user information is retrieved from a data card used in relation to the start of the first fuel supply operation, and the user information includes at least one of a name, address, or number associated with the user; Retrieve; Store the user information in the created file; The non - transitory computer - readable medium according to claim 17, which causes the above to be performed.

19. When the instructions are executed by the one or more processors, the one or more processors are further caused to communicate a warning message indicating that the first fuel supply operation is associated with an anomaly indicating a discrepancy between the measured volume parameter per unit time and the threshold volume parameter per unit time, according to claim 15.

20. Instructing the fuel supply terminal to stop fuel supply includes: Communicating a first signal to turn off the fuel supply terminal to the fuel supply terminal, or Communicating a second signal to close a valve through which fuel is supplied to the fuel supply terminal; The non - transitory computer - readable medium according to claim 15, which includes at least one of the above.

Images