Oil feed authentication system

Abstract

To provide an oil feed authentication system capable of highly reliable authentication when feeding fuel oil to a container (a portable can, etc.), and when feeding the fuel oil from the container to an oil feeding target (an agricultural implement, a generator, etc.).SOLUTION: An oil feed authentication system 1 comprises: a portable terminal 2 for inputting user information of a customer, information of a container 5 that reserves the fuel oil, and information of oil feeding targets 6, 7 to which the oil is fed from the container 5; and a management server 3 that records and manages various information input from the portable terminal 2. The management server 3 outputs to the portable terminal 2 whether the oil can be fed or not to the container 5 and the oil feeding targets 6, 7 input from the portable terminal 2. The management server 3 authenticates oil feeding to the container 5 when the oil feeding target information associated with the container information input from the portable terminal 2 is registered in the management server 3 and when the container 5 being the target of the container information exists in a prescribed location, and outputs that the authentication has been carried out to the portable terminal 2.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a fuel supply authentication system that can perform highly reliable authentication while eliminating the need for identity verification, which is required when filling a container such as a portable can with fuel, and when filling fuel oil from a container with fuel (agricultural machinery, generators, etc.). [Background technology]

[0002] As a device for supplying fuel oil to a container, the present applicant has proposed in Patent Documents 1 and 2 a fuel supply device that is unlikely to cause oil leakage even after long-term use, and a fuel supply device that can efficiently supply fuel to portable cans, etc.

[0003] Meanwhile, following the explosion and fire that occurred in Fushimi Ward, Kyoto City, Kyoto Prefecture in July 2019, a ministerial ordinance amending part of the regulations on the control of hazardous materials (Ministry of Internal Affairs and Communications Ordinance No. 67 of 2019) was enacted to prevent similar incidents from occurring, making it mandatory to verify the identity of the customer, confirm the purpose of use, and create a sales record when refilling gasoline into containers for sale.However, the current situation is that it is not possible to completely prevent sales and use by suspicious individuals, as seen in the case of a building fire in Kita Ward, Osaka City in December 2021 that resulted in numerous deaths and injuries. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 10-264999 [Patent Document 2] Japanese Patent Application Publication No. 11-91887 Summary of the Invention [Problem to be solved by the invention]

[0005] Therefore, the present invention aims to provide a fuel supply authentication system that can perform highly reliable authentication when fuel oil is supplied to a container (such as a portable can) and when fuel oil is supplied from the container to an object to be refueled (such as agricultural machinery or a generator). [Means for solving the problem]

[0006] In order to achieve the above-mentioned object, the present invention is a refueling authentication system comprising a mobile terminal for inputting customer user information, information on a container for storing fuel oil, and information on an object to be refueled from the container, and a management server for recording and managing the various pieces of information input from the mobile terminal, and the management server outputs to the mobile terminal whether or not refueling is permitted for the container and object to be refueled input from the mobile terminal.

[0007] According to the present invention, highly reliable authentication and refueling can be performed when fuel oil is filled into a container and when it is filled from the container into a refueling object. Furthermore, by using a management server, it is not necessary to input customer identification information (user information) at the gas station, which reduces the workload of staff. Furthermore, by using a cloud server, it is not necessary to record user information at any gas station nationwide that uses the system. Furthermore, by managing customer usage history on the management server, it is possible to determine from past data when and how much fuel oil a customer needs to purchase, encouraging customers to plan their purchases accordingly.

[0008] When refueling object information linked to the container information input from the mobile terminal is registered in the management server and the container that is the subject of the container information is present in a specified location, the management server can authenticate (permit refueling) the supply of fuel to the container and output the authentication to the mobile terminal. As a result, when refueling a container at a gas station or the like, if information on the object to be refueled from the container is not registered in the container, the supply of fuel to the container is not authenticated, making it possible to prevent refueling of suspicious containers.

[0009] The management server can authenticate the refueling if the refueling object information linked to the container information input from the mobile terminal matches the refueling object information input from the mobile terminal, and output the authentication to the mobile terminal. As a result, when refueling an object from a container at home or the like to a refueling object, if the refueling object information registered in advance does not match the refueling object to be refueled, the management server does not authenticate the refueling to the refueling object, making it possible to prevent refueling of suspicious refueling objects.

[0010] When refueling is authenticated, the mobile terminal outputs an unlock signal to the container, and the container unlocks the fuel filler port in response to the unlock signal from the mobile terminal.This allows for highly reliable refueling because the container will not be unlocked unless refueling is authenticated.

[0011] The management server can authenticate the supply of fuel from the container to the object to be refueled if the object to be refueled is located at a registered location, thereby preventing the object to be refueled from being supplied with fuel at locations other than those registered in advance, thereby preventing refueling at suspicious locations.

[0012] The management server can authenticate the supply of fuel from the container to the object to be refueled when the container is located at a registered location, which prevents the object to be refueled from being refueled at locations other than those registered in advance, thereby preventing refueling at suspicious locations. Furthermore, since the management server checks both the location information of the object to be refueled and the location information of the container before authenticating the supply of fuel, safer refueling is possible. [Effects of the Invention]

[0013] As described above, according to the present invention, it is possible to provide a fuel supply authentication system that can perform highly reliable authentication when fuel oil is supplied from a container to an object to be refueled. [Brief explanation of the drawings]

[0014] [Figure 1]1 is an overall configuration diagram showing an embodiment of a fuel supply authentication system according to the present invention; [Figure 2] 1 is a perspective view showing an example of a container (portable can) used in a fuel supply authentication system according to the present invention. [Figure 3] 10 is a flowchart for explaining a container registration operation in the fuel supply authentication system according to the present invention. [Figure 4] 10 is a flowchart for explaining the refueling object registration operation in the refueling authentication system according to the present invention. [Figure 5] 10 is a flowchart for explaining the operation of the fuel supply authentication system according to the present invention when fueling a container. [Figure 6] 10 is a flowchart for explaining the operation of the fuel supply authentication system according to the present invention when fueling from a container to a fuel supply object. DETAILED DESCRIPTION OF THE INVENTION

[0015] Next, embodiments of the present invention will be described in detail with reference to the drawings.

[0016] FIG. 1 shows an embodiment of a fuel supply authentication system according to the present invention, and this fuel supply authentication system 1 is made up of a mobile terminal 2 carried by a customer and a management server 3 that constitutes a cloud.

[0017] An application software (hereinafter referred to as "app") for this refueling authentication system is installed on the mobile terminal 2, and using the installed app, the customer inputs various information such as user information, information about the container that stores fuel oil such as gasoline, and information about the object to be refueled from the container.

[0018] The portable terminal 2 is configured to be able to read RFID information of a container 5 that stores fuel oil and the objects 6 and 7 to be refueled from the container 5, and the container 5 and the objects 6 and 7 to be refueled form a virtual pairing on the portable terminal 2, and the container 5 forms a virtual pairing with each of the objects 6 and 7 to be refueled via tags (TAG#1 to 3). In this embodiment, an example is shown in which there is one container 5 and two objects 6 and 7 to be refueled, but there may be two or more containers 5 and three or more objects 6 and 7 to be refueled.

[0019] The management server 3 can communicate with the mobile terminal 2 and the authentication authority 4 via the Internet, and as shown in Table 1, the management server 3 records user information such as name, address, telephone number, email address, personal identification data (driver's license data, My Number card information, passport information), and refueling history, and as container information, it records RFID information (tag number, serial number), location of use, usability information, linked refueling object information (RFID tag number), and owner information, and as refueling object information, it records RFID information (tag number), image data with RFID tag attached, location of use, usability, linked container information (RFID tag number), owner information, etc.

[0020] [Table 1]

[0021] The certification authority 4 is a fire or police agency that issues registration permits for containers 5 and objects to be refueled 6, 7, and is configured to be able to communicate with the management server 3 via the Internet, so that the certification authority 4 can access the management server 3 at any time and view usage status.

[0022] 2, the container 5 is a portable canister having a main body 5a, a lid (knob) 5b, an RFID tag 5c, and a sight glass 5d with a scale, and the lid 5b is automatically locked when closed, and is unlocked and the lid 5b opens when an unlock signal is input from the mobile terminal 2. Note that a locking mechanism may be provided on the cap of the container 5 instead of on the container 5 itself.

[0023] The objects to be refueled 6, 7 are objects to which fuel oil is to be supplied from the container 5, and are, for example, agricultural machinery, generators, and the like.

[0024] Next, the operation of the fuel supply authentication system 1 having the above configuration will be described with reference mainly to Figures 3 to 6. In each figure, at steps where the route branches, the downward direction corresponds to Yes and the horizontal direction corresponds to No.

[0025] First, the operation of registering the container 5 will be described with reference to FIG.

[0026] The customer registers in advance as a user using the mobile terminal 2. The user information includes name, address, telephone number, email address, and personal identification data (driver's license data, My Number card information, passport information, etc.).

[0027] The customer reads the RFID tag 5c of the container 5 that he or she will use with the mobile terminal 2, and when the RFID information of the container 5 is entered in step S1 on the customer's mobile terminal 2 (step S1; Yes), the customer selects the location where the container 5 will be used (the location where the fuel will be supplied to the fuel supply target) (step S2). Next, the customer outputs the user information and container information (RFID information, usage location information) from the mobile terminal 2 to the management server 3 (step S3).

[0028] In step S9 of the management server 3, when user information and container information are input from the mobile terminal 2 (step S9; Yes), the management server 3 determines whether this user information exists in the database (step S10), and if this user information exists (step S10; Yes), it outputs the user information and container information to the authentication authority 4 (step S12).

[0029] On the other hand, in step S10, if the user information does not exist in the database of the management server 3 (step S10; No), the management server 3 outputs a registration request to the mobile terminal 2 for the application (step S11) and terminates the operation. The mobile terminal 2 to which the registration request has been input (step S4; Yes) notifies the customer of this fact (step S5) and terminates the operation.

[0030] In step S17 of the authentication authority 4, when user information and container information are input from the management server 3 (step S17; Yes), the authentication authority 4 checks whether the input RFID information (such as the manufacturing number of the container) is certified, and if there is no problem (step S18; Yes), it outputs a registration permission (signal) to the management server 3 (step S19) and terminates the operation. On the other hand, if the RFID information is not certified and there is a problem (step S18; No), it outputs a registration denial (signal) to the management server 3 (step S20) and terminates the operation.

[0031] When the management server 3 receives input of registration permission from the authentication authority 4 (step S13; Yes), it registers the container information and the fact that the container 5 is available in the database (step S14), outputs a registration completion (signal) to the mobile terminal 2 (step S15), and terminates operation. On the other hand, when the management server 3 receives input of registration denial (signal) from the authentication authority 4 (step S13; No), it outputs registration denial to the mobile terminal 2 (step S16), and terminates operation.

[0032] When the mobile terminal 2 receives an input from the management server 3 indicating that registration is complete (step S6; Yes), it displays registration completion information (step S7) and terminates operation. On the other hand, when the mobile terminal 2 receives an input from the management server 3 indicating that registration is not permitted (step S6; No), it notifies that registration is not complete (authentication error) (step S8) and terminates operation.

[0033] Next, the operation of registering the refueling objects 6 and 7 will be described with reference mainly to Fig. 4. In the following description, the case of registering the refueling object 6 will be exemplified.

[0034] The customer attaches an RFID tag to the refueling object 6 and takes a photo of it with the mobile terminal 2. In step S21 of the customer's mobile terminal 2, when the data of the photo with the RFID tag attached is input into the mobile terminal 2 (step S21; Yes), the customer reads the RFID tag of the refueling object 6 with the mobile terminal 2. In step S22, when RFID information is input into the mobile terminal 2 (step S22; Yes), the customer selects a container 5 to be linked to the refueling object 6 (step S23), and further selects the location where the refueling object 6 will be used (step S24).

[0035] Next, the customer outputs user information and refueling object information (photo data, RFID information of the associated container, RFID information of the refueling object, and usage location information) from the mobile terminal 2 to the management server 3 (step S25).

[0036] In step S31 of the management server 3, when user information and refueling object information are input from the mobile terminal 2 (step S31; Yes), the management server 3 determines whether this user information exists in the database (step S32), and if this user information exists (step S32; Yes), it outputs the user information and refueling object information to the authentication agency 4 (step S33).

[0037] On the other hand, if the user information does not exist in the database of the management server 3 in step S32 (step S32; No), the management server 3 outputs a registration request to the mobile terminal 2 for the application (step S37) and terminates the operation. The mobile terminal 2 to which the registration request has been input (step S26; Yes) notifies the customer of this (step S27) and terminates the operation.

[0038] In step S41 of the authentication agency 4, when user information and refueling object information are input from the management server 3 (step S41; Yes), the authentication agency 4 checks whether the tag number or authentication number of the refueling object derived from the photo data (photographs of the refueling object and the RFID tag affixed to the refueling object) matches the tag number or authentication number of the refueling object derived from the RFID information read by the mobile terminal this time, and if there is no problem (step S42; Yes), it outputs registration permission to the management server 3 (step S43) and terminates the operation. On the other hand, if there is a problem (step S42; No), it outputs registration denial to the management server 3 (step S44) and terminates the operation. The authentication number is assigned by the authentication agency 4 when issuing an RFID tag for the refueling object.

[0039] When the management server 3 receives input from the authentication authority 4 permitting registration (step S34; Yes), it registers the refueling object information and the fact that the refueling object 6 is available for use, as well as the pairing information between the container 5 and the refueling object 6, in the database (step S35), outputs a registration completion notice to the mobile terminal 2 (step S36), and terminates operation. On the other hand, when the management server 3 receives input from the authentication authority 4 prohibiting registration (step S34; No), it outputs a registration denial notice to the mobile terminal 2 (step S38), and terminates operation.

[0040] When the mobile terminal 2 receives an input from the management server 3 indicating that registration is complete (step S28; Yes), it displays registration completion information (step S29) and terminates operation. On the other hand, when the mobile terminal 2 receives an input from the management server 3 indicating that registration is not permitted (step S28; No), it notifies that registration is not complete (authentication error) (step S30) and terminates operation.

[0041] Next, the operation of supplying fuel to the container 5 will be described with reference to FIG.

[0042] When the customer reads the RFID tag on the container 5 with the mobile terminal 2, and in step S51 on the customer's mobile terminal 2, the RFID information is entered into the mobile terminal 2 (step S51; Yes), the customer selects the use of the container 5 (step S52), and the mobile terminal 2 outputs an authentication request to the management server 3 (step S53).

[0043] In step S71 of the management server 3, when an authentication request is input from the mobile terminal 2 (step S71; Yes), the management server 3 determines whether user information exists in the database (step S72), and if user information exists (step S72; Yes), it extracts container information from the RFID information (step S73).

[0044] On the other hand, in step S72, if the user information does not exist in the database of the management server 3 (step S72; No), the management server 3 outputs a registration request to the mobile terminal 2 for the application (step S78) and terminates the operation. The mobile terminal 2 to which the registration request has been input (step S54; Yes) notifies the customer of this (step S55) and terminates the operation.

[0045] Next, the management server 3 checks whether a refueling object is registered in the container 5 to which the user is attempting to refuel, and detects the location information of the container 5 (step S74). As a result, if a refueling object is registered in the container 5 to which the user is attempting to refuel, and the container 5 is located at a gas station (step S74; Yes), an authentication signal (authentication OK) is output to the portable terminal 2 (step S75). On the other hand, if a refueling object is not registered in the container 5 to which the user is attempting to refuel, or / and the container 5 is not located at a gas station (step S74; No), the management server 3 outputs a non-authentication signal (authentication NG) to the portable terminal 2 (step S79), and ends the operation. If the non-authentication signal (authentication NG) is input from the management server 3 (step S56; No), the portable terminal 2 notifies the user of an authentication error (step S67), and ends the operation.

[0046] In step S56 of the portable terminal 2, when an authentication signal (authentication OK) is input from the management server 3 (step S56; Yes), the portable terminal 2 displays authentication OK and the purpose of the container 5 on the display unit (step S57). When the gas station staff member checks the content displayed on the display unit and the gas station staff member or the customer presses the container unlock button (step S58; Yes), an unlock signal is sent from the portable terminal 2 to the container 5 (step S59).

[0047] In step S81, when an unlock signal is input from the mobile terminal 2 (step S81; Yes), the container 5 is unlocked (step S82).

[0048] After an unlock signal is sent from the mobile terminal 2 to the container 5, the customer takes a photo of the scale on the container 5 (step S60), the gas station staff starts filling the container 5 (step S61), and when the gas station staff or the customer presses the refueling completion button (step S62; Yes), the refueling operation is completed (step S63).

[0049] After refueling is complete, the customer photographs the scale on the container 5 (step S64), and the mobile terminal 2 calculates the amount of fuel refueled this time from the photographed data of the container scale at the start and end of refueling (step S65), outputs the information on the amount of fuel refueled this time to the management server 3 (step S66), and ends the operation.

[0050] When the management server 3 receives the current fuel amount information from the mobile terminal 2 (step S76; Yes), it updates the fuel supply history (step S77) and terminates the operation. Also, when the gas station staff or the customer closes the lid of the container 5 (step S83; Yes), the container 5 is automatically locked (step S84).

[0051] Next, the operation of supplying fuel from the container 5 to the object 6 to be supplied with fuel will be described with reference mainly to FIG.

[0052] When the customer reads the RFID tag of the container 5 with the portable terminal 2 and inputs RFID information into the portable terminal 2 in step S91 (step S91; Yes), a timer starts (step S92). This timer is for confirming that the container 5 and the object 6 to be refueled are close to each other.

[0053] Next, the customer reads the RFID tag of the object 6 to be refueled with the portable terminal 2, and in step S93 of the customer's portable terminal 2, RFID information is input to the portable terminal 2 (step S93; Yes), and if the timer has not yet reached the predetermined time t (step S94; Yes), the portable terminal 2 outputs an authentication request to the management server 3 (step S95). On the other hand, if the timer has reached the predetermined time t (step S94; No), the portable terminal 2 notifies the customer of the timeout (step S96) and ends the operation.

[0054] In step S111 of the management server 3, when an authentication request is input from the mobile terminal 2 (step S111; Yes), the management server 3 determines whether user information exists in the database, and if the user information exists (step S112; Yes), it extracts container information and refueling object information from the RFID information (step S113).

[0055] On the other hand, in step S112, if the user information does not exist in the database of the management server 3 (step S112; No), the management server 3 outputs a registration request to the mobile terminal 2 for the application (step S120) and terminates the operation. The mobile terminal 2 to which the registration request has been input (step S97; Yes) notifies the customer of this (step S98) and terminates the operation.

[0056] Next, the management server 3 checks whether the refueling object 6 linked to the container 5 to be refueled matches the extracted refueling object 6 (step S114), and if they match (step S114; Yes), it determines whether the user is at a location to be registered as a location for using the refueling object (step S115).On the other hand, if the refueling object 6 linked to the container 5 to be refueled does not match the extracted refueling object 6 (step S114; No), the management server 3 outputs a non-authentication signal (authentication NG) to the mobile terminal 2 (step S121) and ends the operation.

[0057] In step S115, if the user is in a location registered as a location where the refueling object 6 is used (step S115; Yes), the management server 3 determines whether the user is in a location registered as a location where the container 5 is used (step S116), and if the user is in the registered location (step S116; Yes), the management server 3 outputs an authentication signal (authentication OK) to the portable terminal 2 (step S117). On the other hand, if the user is not in a location registered as a location where the refueling object 6 is used in step S115 (step S115; No), or if the user is not in a location registered as a location where the container 5 is used in step S116 (step S116; No), the management server 3 outputs a non-authentication signal (authentication NG) to the portable terminal 2 (step S121), and ends the operation. If the non-authentication signal (authentication NG) is input from the management server 3 (step S99; No), the portable terminal 2 notifies the user of an authentication error (step S110), and ends the operation.

[0058] In step S99 of the mobile terminal 2, when an authentication signal (authentication OK) is input from the management server 3 (step S99; Yes), the mobile terminal 2 displays "authentication OK" on the display unit (step S100). When the customer checks the content displayed on the display unit and presses the container unlock button (step S101; Yes), an unlock signal is sent from the mobile terminal 2 to the container 5 (step S102).

[0059] When an unlock signal is input from the mobile terminal 2 in step S122 (step S122; Yes), the container 5 is unlocked (step S123).

[0060] After an unlock signal is sent from the mobile terminal 2 to the container 5, the customer photographs the scale on the container 5 (step S103), starts supplying fuel to the object 6 to be supplied with fuel (step S104), and presses the fuel supply completion button (step S105; Yes), completing the fuel supply operation (step S106).

[0061] After refueling is complete, the customer photographs the scale on the container 5 (step S107), and the mobile terminal 2 calculates the amount of fuel refueled this time from the photographed data of the container scale at the start and end of refueling (step S108), outputs the information on the amount of fuel refueled this time to the management server 3 (step S109), and ends the operation.

[0062] When the management server 3 receives the current fuel amount information from the mobile terminal 2 (step S118; Yes), it updates the fuel supply history (step S119) and ends the operation. Also, when the customer closes the lid of the container 5 (step S124; Yes), the container 5 is automatically locked (step S125).

[0063] In the above embodiment, various authentication signals were output from the management server 3 to the mobile terminal 2, but data may be downloaded from the management server 3 into the customer's mobile terminal 2, and authentication may be performed at the gas station including the mobile terminal 2.

[0064] Furthermore, in the above embodiment, the container 5 is locked and unlocked, but it is also possible to perform authentication and record only the purchase without locking the container 5.

[0065] Furthermore, when fuel oil is filled into container 5 at a gas station, an authentication QR code (registered trademark) showing the authentication result from management server 3 may be displayed on mobile terminal 2, and this authentication QR code may be read by a fueling permission device carried by a gas station employee, and once authentication has been obtained by the fueling permission device, fuel may be filled from the metering machine. This allows the fueling authentication system to be linked to the metering machine, preventing unauthorized fueling without authentication and further improving safety.

[0066] Furthermore, in the above embodiments, the case of handling gasoline has been exemplified, but the present invention can also be applied to fuel oils such as kerosene, and when handling kerosene, a plastic container is used as the container 5. The illustrated embodiments are merely examples and are not intended to limit the technical scope of the present invention. [Explanation of symbols]

[0067] 1. Fueling authentication system 2. Mobile devices 3 Management Server 4. Certification Bodies 5 containers 6, 7 Refueling objects

Claims

1. a mobile terminal for inputting customer user information, information on a container for storing fuel oil, and information on an object to be refueled from the container; a management server that records and manages the various information input from the mobile terminal; The management server outputs to the mobile terminal whether or not fuel can be supplied to the container and the object to be supplied with fuel, which are input from the mobile terminal.

2. The refueling authentication system described in claim 1, characterized in that the management server authenticates the refueling of the container when refueling object information linked to the container information input from the mobile terminal is registered in the management server and the container that is the subject of the container information is present at a specified location, and outputs the authentication to the mobile terminal.

3. The refueling authentication system described in claim 1, characterized in that the management server authenticates the refueling when the refueling object information linked to the container information input from the mobile terminal matches the refueling object information input from the mobile terminal, and outputs the authentication to the mobile terminal.

4. When the fuel supply is authenticated, the mobile terminal outputs an unlock signal to the container; 4. The fuel supply authentication system according to claim 1, wherein the fuel filler opening of the container is unlocked in response to an unlock signal from the mobile terminal.

5. 4. The refueling authentication system according to claim 1, wherein the management server authenticates refueling from the container to the refueling object when the refueling object is present at a registered location.

6. 4. The refueling authentication system according to claim 1, wherein the management server authenticates refueling from the container to the object to be refueled when the container is present at a registered location.

Images