Fueling 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 fueling authentication system that can perform highly reliable authentication while saving the trouble of personal identification and the like required when fueling a container such as a portable can and when fueling a fuel object (agricultural machinery, generator, etc.) from the container.

Background Art

[0002] As a device for fueling a container with fuel oil, the applicant has proposed in Patent Documents 1 and 2 a fueling device that is less likely to cause oil leakage even after long-term use and a fueling device that can efficiently fuel a portable can or the like.

[0003] On the other hand, in response to the explosion and fire that occurred in Fushimi Ward, Kyoto City, Kyoto Prefecture in July 2019, in order to prevent the occurrence of similar incidents, a cabinet order (Cabinet Order No. 67 of the Ministry of Internal Affairs and Communications in 2019) that amended part of the regulations on dangerous goods stipulated that when refilling a container for selling gasoline, it is obligatory to confirm the identity of the customer, confirm the purpose of use, and create a sales record. However, as of December 2021, in Kita Ward, Osaka City, a building fire occurred with a large number of casualties, etc., and the current situation is that the sale and use to suspicious persons cannot be completely prevented.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

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

[0006] To achieve the above objective, 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 the object to be refueled from the container, and a management server for recording and managing the various information input from the mobile terminal, wherein the management server outputs to the mobile terminal whether or not refueling is permitted for the container and the object to be refueled, as input from the mobile terminal.

[0007] According to the present invention, highly reliable authentication and refueling can be performed when refueling a container with fuel oil and when refueling from the container to the object to be refueled. Furthermore, by using a management server, it becomes unnecessary to input customer identity verification information (user information) at gas stations, reducing the workload on staff. In addition, by using a cloud server, it becomes unnecessary to record user information at any gas station nationwide that is using the system. Moreover, by managing customer usage history on the management server, it is possible to deduce from past data when and how much fuel oil a customer needs to purchase, encouraging customers to make planned purchases.

[0008] The management server can authenticate (authorize refueling) the refueling of a container if the refueling target information linked to the container information entered from the mobile terminal is registered on the management server and the container to which the container information pertains is located at the designated location, and can output the authentication confirmation to the mobile terminal. As a result, when refueling a container at a gas station, etc., if the information of the object to be refueled from that container is not registered for the container being refueled, the refueling of the container will not be authenticated, thus preventing refueling of suspicious containers.

[0009] The management server can authenticate refueling if the information of the object to be refueled, which is linked to the container information entered from the mobile terminal, matches the information of the object to be refueled, and can output the authentication confirmation to the mobile terminal. As a result, when refueling an object from a container at home or elsewhere, if the information of the object to be refueled does not match the pre-registered information of the object to be refueled, the server will not authenticate refueling to the object, thereby preventing refueling of suspicious objects.

[0010] The mobile terminal outputs an unlock signal to the container when refueling is authenticated, and the container's fuel filler opening is unlocked by the unlock signal from the mobile terminal. As a result, the container's lock is not released unless refueling is authenticated, enabling highly reliable refueling.

[0011] The management server can authenticate refueling from the container to the object to be refueled if the object is located at a registered location. This prevents refueling of the object to be refueled at locations other than those previously registered, thus preventing refueling at suspicious locations.

[0012] The management server can authenticate refueling from the container to the fuel target if the container is located at a registered location. This prevents refueling of fuel target locations other than those previously registered, thus preventing refueling at suspicious locations. Furthermore, since both the location information of the fuel target and the location information of the container are checked before refueling is authenticated, a higher level of security is achieved for refueling. [Effects of the Invention]

[0013] As described above, the present invention provides a refueling authentication system that can perform highly reliable authentication when refueling fuel oil from a container to a target object. [Brief explanation of the drawing]

[0014] [Figure 1]This is an overall configuration diagram showing one embodiment of the fueling authentication system according to the present invention. [Figure 2] This is a perspective view showing an example of a container (portable container) used in the fueling authentication system according to the present invention. [Figure 3] This is a flowchart illustrating the container registration operation in the fueling authentication system according to the present invention. [Figure 4] This is a flowchart illustrating the registration operation for refueling targets in the refueling authentication system according to the present invention. [Figure 5] This is a flowchart illustrating the operation during refueling of a container in the refueling authentication system according to the present invention. [Figure 6] This is a flowchart illustrating the operation of the refueling authentication system according to the present invention when refueling is performed from a container to the object to be refueled. [Modes for carrying out the invention]

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

[0016] Figure 1 shows one embodiment of the fueling authentication system according to the present invention, which consists of a mobile terminal 2 owned by the customer and a management server 3 that constitutes a cloud.

[0017] Mobile device 2 has application software for this refueling authentication system (hereinafter referred to as "the app") installed. Using the installed app, the customer inputs various information, including user information, information about the container that stores gasoline or other fuel oil, and information about the object to be refueled from the container.

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

[0019] The management server 3 can communicate with the mobile terminal 2 and the certification authority 4 via the Internet. 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 records container information such as RFID information (tag number, manufacturing number), place of use, availability information, refueling object information to be linked (RFID tag number), and owner information. The refueling object information records RFID information (tag number), RFID tag attached image data, place of use, availability, container information to be linked (RFID tag number), owner information, etc.

[0020]

Table 1

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

[0022] The container 5 is a portable can as shown in FIG. 2, for example, and includes a lid (knob) 5b, an RFID tag 5c, and a graduated sight glass 5d on the main body 5a. When the lid 5b is closed, it is automatically locked, and when a unlock signal is input from the mobile terminal 2, the lock is released and the lid 5b opens. Note that instead of providing a locking mechanism on the container 5 itself, a locking mechanism may be provided on the cap of the container 5.

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

[0024] Next, the operation of the refueling authentication system 1 having the above configuration will be explained, mainly with reference to Figures 3 to 6. In each figure, at the step where the route branches, downwards correspond to Yes and sideways to No.

[0025] First, we will explain the registration process for container 5, primarily referring to Figure 3.

[0026] Customers register in advance using mobile device 2. User information includes name, address, phone number, email address, and identity verification data (driver's license data, My Number card information, passport information, etc.).

[0027] The customer reads the RFID tag 5c of the container 5 they will be using with their mobile terminal 2. In step S1 of the customer's mobile terminal 2, if the RFID information of the container 5 is entered (step S1; Yes), the customer selects the location where the container 5 will be used (the location where the refueling target will be refueled) (step S2). Next, the customer outputs the user information and container information (RFID information, 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 entered from the mobile terminal 2 (step S9; Yes), the management server 3 determines whether or not this user information exists in the database (step S10). If this user information exists (step S10; Yes), it outputs the user information and container information to the certification authority 4 (step S12).

[0029] On the other hand, in step S10, if the above 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 (step S11) and terminates its operation. If the mobile terminal 2 receives the above registration request (step S4; Yes), it notifies the customer of this fact (step S5) and terminates its operation.

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

[0031] If the management server 3 receives input from the certification authority 4 granting permission for registration (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 its operation. On the other hand, if the management server 3 receives input from the certification authority 4 granting permission for registration (step S13; No), it outputs a registration denial to the mobile terminal 2 (step S16), and terminates its operation.

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

[0033] Next, we will explain the registration process for refueling targets 6 and 7, primarily referring to Figure 4. In the following explanation, we will use the registration of refueling target 6 as an example.

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

[0035] Next, the customer outputs user information and fuel supply information (photo data, RFID information of the linked container, RFID information of the fuel supply, 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 fuel supply target information are input from the mobile terminal 2 (step S31; Yes), the management server 3 determines whether or not this user information exists in the database (step S32). If this user information exists (step S32; Yes), it outputs the user information and fuel supply target information to the certification authority 4 (step S33).

[0037] On the other hand, in step S32, if the above user information does not exist in the database of the management server 3 (step S32; No), the management server 3 outputs a registration request to the mobile terminal 2 (step S37) and terminates its operation. If the mobile terminal 2 receives the above registration request (step S26; Yes), it notifies the customer of this fact (step S27) and terminates its operation.

[0038] In step S41 of the certification authority 4, when user information and fuel supply item information are input from the management server 3 (step S41; Yes), the certification authority 4 checks whether the tag number or certification number of the fuel supply item derived from the photographic data (photographs of the fuel supply item and the RFID tag attached to the fuel supply item) matches the tag number or certification number of the fuel supply item derived from the RFID information read by the mobile terminal. 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 aforementioned certification number is assigned when the certification authority 4 issues an RFID tag for the fuel supply item.

[0039] If the management server 3 receives input from the certification authority 4 granting permission for registration (step S34; Yes), it registers information about the fuel to be dispensed, that the fuel to be dispensed 6 is available, and the pairing information between the container 5 and the fuel to be dispensed 6 in the database (step S35), outputs a message indicating the completion of registration to the mobile terminal 2 (step S36), and terminates its operation. On the other hand, if the management server 3 receives input from the certification authority 4 denying permission for registration (step S34; No), it outputs a message indicating that registration has been denied to the mobile terminal 2 (step S38), and terminates its operation.

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

[0041] Next, we will explain the refueling operation for container 5, referring primarily to Figure 5.

[0042] The customer reads the RFID tag on container 5 with their mobile terminal 2. In step S51 of the customer's mobile terminal 2, once the RFID information is entered into the mobile terminal 2 (step S51; Yes), the customer selects the intended use of 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 entered 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 above 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 (step S78) and terminates its operation. If the mobile terminal 2 receives the above registration request (step S54; Yes), it notifies the customer of this fact (step S55) and terminates its operation.

[0045] Next, the management server 3 checks whether the container 5 to be refueled is registered and detects the location information of the container 5 (step S74). If the container 5 to be refueled is registered and the container 5 is located at the refueling station (step S74; Yes), the management server 3 outputs an authentication signal (authentication OK) to the mobile terminal 2 (step S75). On the other hand, if in step S74 the container 5 to be refueled is not registered, or / or the container 5 is not located at the refueling station (step S74; No), the management server 3 outputs an authentication failure signal (authentication NG) to the mobile terminal 2 (step S79) and terminates its operation. When the mobile terminal 2 receives an authentication failure signal (authentication NG) from the management server 3 (step S56; No), it reports an authentication error (step S67) and terminates its operation.

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

[0047] In step S81, if an unlock signal is received from the mobile terminal 2 (step S81; Yes), the lock on container 5 is released (step S82).

[0048] After a lock release signal is sent from the mobile terminal 2 to container 5, the customer takes a picture of the markings on container 5 (step S60), the gas station staff starts refueling container 5 (step S61), and when the gas station staff or the customer presses the refueling complete button (step S62; Yes), the refueling process is completed (step S63).

[0049] After refueling is complete, the customer takes a picture of the markings on container 5 (step S64). The mobile terminal 2 then calculates the amount of refueled from the container markings photographed at the start and end of refueling (step S65), outputs the refueled amount information to the management server 3 (step S66), and terminates its operation.

[0050] When the management server 3 receives input from the mobile terminal 2 regarding the amount of fuel dispensed (step S76; Yes), it updates the fueling history (step S77) and terminates its operation. Also, when the gas station staff or customer closes the lid of container 5 (step S83; Yes), the lock on container 5 is automatically set (step S84).

[0051] Next, we will explain the refueling operation from container 5 to object 6, referring mainly to Figure 6.

[0052] When the customer reads the RFID tag on container 5 with their mobile terminal 2, and the RFID information is entered into the mobile terminal 2 in step S91 (step S91; Yes), the timer starts (step S92). This timer is used to confirm that container 5 and the object to be refueled 6 are close together.

[0053] Next, the customer reads the RFID tag of the refueling object 6 with the mobile terminal 2. In step S93 of the customer's mobile terminal 2, if the RFID information is entered into the mobile terminal 2 (step S93; Yes) and the timer has not yet elapsed a predetermined time t (step S94; Yes), the mobile terminal 2 outputs an authentication request to the management server 3 (step S95). On the other hand, if the timer has elapsed a predetermined time t (step S94; No), the mobile terminal 2 notifies the customer of the timeout (step S96) and terminates the operation.

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

[0055] On the other hand, in step S112, if the above 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 (step S120) and terminates its operation. If the mobile terminal 2 receives the above registration request (step S97; Yes), it notifies the customer of this fact (step S98) and terminates its operation.

[0056] Next, the management server 3 checks whether the refueling target object 6 associated with the container 5 being refueled matches the extracted refueling target object 6 (step S114). If they match (step S114; Yes), it determines whether the user is at the location to be registered as the usage location for the refueling target object (step S115). On the other hand, if the refueling target object 6 associated with the container 5 being refueled does not match the extracted refueling target object 6 (step S114; No), the management server 3 outputs an authentication failure signal (authentication NG) to the mobile terminal 2 (step S121) and terminates its operation.

[0057] In step S115, if the user is at a location registered as the usage location for the refueling object 6 (step S115; Yes), the management server 3 determines whether or not the user is at a location registered as the usage location for the container 5 (step S116). If the user is at a registered location (step S116; Yes), the management server 3 outputs an authentication signal (authentication OK) to the mobile terminal 2 (step S117). On the other hand, if the user is not at a location registered as the usage location for the refueling object 6 in step S115 (step S115; No), and if the user is not at a location registered as the usage location for the container 5 in step S116 (step S116; No), the management server 3 outputs an authentication failure signal (authentication NG) to the mobile terminal 2 (step S121) and terminates its operation. If the mobile terminal 2 receives an authentication failure signal (authentication NG) from the management server 3 (step S99; No), it reports an authentication error (step S110) and terminates its 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 its display unit (step S100). When the customer confirms the information displayed on the display unit and presses the container unlock button (step S101; Yes), the mobile terminal 2 sends an unlock signal to the container 5 (step S102).

[0059] In step S122, if an unlock signal is received from the mobile terminal 2 (step S122; Yes), the lock on container 5 is released (step S123).

[0060] After an unlock signal is sent from the mobile terminal 2 to the container 5, the customer takes a picture of the scale on the container 5 (step S103), starts refueling the object to be refueled 6 (step S104), and when they press the refueling complete button (step S105; Yes), the refueling operation is completed (step S106).

[0061] After refueling is complete, the customer takes a picture of the markings on container 5 (step S107). The mobile terminal 2 then calculates the amount of refueled from the container markings photographed at the start and end of refueling (step S108), outputs the refueled amount information to the management server 3 (step S109), and terminates its operation.

[0062] When the management server 3 receives input from the mobile terminal 2 regarding the amount of fuel dispensed (step S118; Yes), it updates the fuel dispensing history (step S119) and terminates its operation. Also, when the customer closes the lid of container 5 (step S124; Yes), the lock on container 5 is automatically set (step S125).

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

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

[0065] Furthermore, when refueling container 5 at a gas station, an authentication QR code (registered trademark) representing the authentication result from the management server 3 may be displayed on the mobile terminal 2. This authentication QR code can be read by a refueling authorization device held by a gas station employee, and once authenticated by the refueling authorization device, refueling from the dispenser may be permitted. This enables the refueling authentication system and the dispenser to be linked, preventing unauthorized refueling in the event of unauthenticated refueling and further improving safety.

[0066] Furthermore, while the above embodiments illustrate the handling of gasoline, the method can also be used to handle fuel oils such as kerosene, and in the case of handling kerosene, a plastic container will be used as container 5. The illustrated embodiments are for illustrative purposes only 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 Items to be refueled

Claims

1. A mobile terminal into which customer user information, information about a fuel oil storage container, and information about the fuel to be dispensed from the container are entered. The system includes a management server that records and manages the various types of information entered from the mobile terminal, The refueling authentication system is characterized in that the management server outputs to the mobile terminal whether or not refueling is permitted for the container and the object to be refueled, as entered from the mobile terminal.

2. The refueling authentication system according to claim 1, characterized in that the management server authenticates refueling to a container when the refueling target information linked to the container information entered from the mobile terminal is registered on the management server and the container to which the container information pertains is located at the specified location, and outputs the authentication to the mobile terminal.

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

4. When refueling is authenticated, the aforementioned mobile terminal outputs an unlock signal to the container. The fueling authentication system according to claim 1, 2, or 3, characterized in that the fueling port of the container is unlocked by an unlocking signal from the mobile terminal.

5. The refueling authentication system according to claim 1, 2, or 3, characterized in that the management server authenticates refueling from the container to the refueling target when the refueling target is located at a registered location.

6. The refueling authentication system according to claim 1, 2, or 3, characterized in that the management server authenticates refueling from the container to the object to be refueled when the container is located at a registered location.

Images