JP7781178B2 - Authentication system and authentication method - Google Patents

Description

The present invention relates to an authentication system and an authentication method.

Conventionally, shared battery services (hereinafter referred to as "battery exchange services") have been offered that involve removing a charged removable battery from a container and attaching it to a vehicle such as an electric scooter for use. For example, this service involves installing battery exchange devices at multiple locations in a local area, allowing users to visit the charging and exchange devices to exchange their removable batteries.

With regard to such battery replacement services, an authentication system has been proposed that enables battery replacement through user authentication (see, for example, Patent Document 1). Patent Document 1 describes how communication takes place between an authentication medium and a battery replacement device, and if the ID information matches, battery replacement is enabled.

However, in authentication systems using conventional technology, when a user applied to use a battery exchange service, the battery exchange service provider had to link the user who applied with the authentication medium to be supplied to that user, which could have increased the management burden associated with providing the service.

Japanese Patent Application Laid-Open No. 2021-078175

The present invention was made in consideration of these circumstances, and one of its objectives is to provide an authentication system and authentication method that can reduce the management burden associated with service provision.

The authentication system and authentication method of this invention adopt the following configuration.

(1): An authentication system according to one aspect of the present invention comprises an authentication medium provided to a user; a target device that is capable of executing a predetermined operation when authentication of the user is successful through communication with the authentication medium; and a server device that receives from the user's terminal device identification information of the authentication medium entered into the user's terminal device and input information entered into the terminal device as the user's membership information, the server device comprising a first memory unit that pre-stores the user's membership information, and an authentication medium registration unit that registers the user's authentication medium as a valid authentication medium when the input information received from the terminal device matches the membership information stored in the first memory unit, and the target device comprises an authentication unit that authenticates the user of the authentication medium by communicating with the authentication medium registered as the valid authentication medium.

(2): In the above aspect (1), in the server device, the authentication medium registration unit transmits identification information of the authentication medium registered as the valid authentication medium to the target device, and the target device further includes a second memory unit that stores the identification information received from the server device, and the authentication unit authenticates the user of the authentication medium when the identification information obtained from the authentication medium through communication with the authentication medium matches the identification information stored in the second memory unit.

(3): In the above aspect (2), the authentication medium registration unit transmits to the target device at a predetermined frequency the identification information of the authentication medium that has been registered as the valid authentication medium and has not yet been transmitted to the target device.

(4): In the above aspect (1), in the server device, the authentication medium registration unit records the identification information of the authentication medium registered as the valid authentication medium in the first memory unit, and in the target device, the authentication unit inquires of the server device whether the identification information obtained from the authentication medium through communication with the authentication medium matches the identification information stored in the first memory unit, and if they match, authenticates the user of the authentication medium.

(5): In any of the above aspects (1) to (4), the authentication medium further includes a display unit that displays a graphic in which the identification information is encoded, and the terminal device includes an imaging unit that captures an image of the graphic, a reading unit that decodes the image of the graphic captured by the imaging unit to obtain the identification information, and a transmitting unit that transmits the identification information obtained by the reading unit to the server device as the input information.

(6): In any of the above aspects (1) to (5), the target device further includes a battery replacement unit that collects used batteries and replaces them with charged batteries, and a near-field communication unit that wirelessly communicates with an authentication medium located within a predetermined distance from the target device, and the authentication unit enables the battery replacement unit to replace the battery when the user of the authentication medium is authenticated by communication between the near-field communication unit and the authentication medium.

(7): In the above aspect (6), the target device further includes a detection unit that detects the amount of usage of the battery when the battery is returned, and the battery replacement unit transmits to the server device identification information of the authentication medium obtained in the authentication related to the return of the battery and information on the amount of usage of the battery, and the server device further includes a usage fee calculation unit that identifies the user of the battery based on the identification information of the authentication medium received from the target device and calculates the usage fee for the battery used by the user over a specified period based on the usage information.

(8): An authentication system according to one aspect of the present invention comprises an authentication medium provided to a user, a target device that is capable of executing a predetermined operation if authentication of the user is successful, and a server device that receives from the user's terminal device identification information of the authentication medium entered into the terminal device and input information entered into the terminal device as the user's membership information, the server device comprising a first memory unit that pre-stores the user's membership information, and an authentication medium registration unit that registers the user's authentication medium as a valid authentication medium if the input information received from the terminal device matches the membership information stored in the first memory unit, and the target device comprises an authentication unit that authenticates the user of the authentication medium if identification information read from the authentication medium matches the identification information of the authentication medium registered as the valid authentication medium.

(9): An authentication method according to one aspect of the present invention is a method for authenticating a user using a target device that is capable of executing a predetermined operation when authentication of the user is successful through communication with an authentication medium provided to the user, and a server device that receives from the user's terminal device identification information of the authentication medium entered into the user's terminal device and input information entered into the terminal device as the user's membership information, wherein the server device pre-stores the user's membership information in a first memory unit, and when the input information received from the terminal device matches the membership information stored in the first memory unit, registers the user's authentication medium as a valid authentication medium, and the target device authenticates the user of the authentication medium by communicating with the authentication medium registered as the valid authentication medium.

(10): An authentication method according to one aspect of the present invention is a method for authenticating a user using an authentication medium provided to the user, a target device that is capable of executing a predetermined operation if authentication of the user is successful, and a server device that receives from the user's terminal device identification information of the authentication medium entered into the user's terminal device and input information entered into the terminal device as the user's membership information, wherein the server device pre-stores the user's membership information in a first memory unit, and when the input information received from the terminal device matches the membership information stored in the first memory unit, registers the user's authentication medium as a valid authentication medium, and the target device authenticates the user of the authentication medium when the identification information read from the authentication medium matches the identification information of the authentication medium registered as the valid authentication medium.

Aspects (1) to (10) above can reduce the management burden on businesses involved in providing battery exchange services. Specifically, aspects (1), (8) to (10) eliminate the need for businesses to link authentication media with users, allowing businesses to register authorized users to authentication media while reducing operational costs.

Furthermore, according to the above aspects (2) and (3), even when the target device and the server device are offline, the target device alone can authenticate the user, thereby improving the convenience of the battery replacement service.

Furthermore, according to the above aspect (4), user authentication can always be performed in the latest state without taking into account the time lag until the information from the server device is reflected on the target device.

Furthermore, according to the above aspect (5), it is possible to prevent the authentication medium from being erroneously registered due to manual input by the user and to reduce the complexity of input.

Furthermore, according to the above aspect (6), the above authentication system can be suitably applied to the authentication of battery replacement devices.

Furthermore, according to the above aspect (7), charges for each user can be easily managed using an authentication medium.

1 is a diagram illustrating an example of an overall configuration diagram of a battery exchange system according to an embodiment; 1 is a diagram illustrating an example of a configuration of an electric vehicle according to an embodiment; 1 is a block diagram showing an example of the configuration of a detachable battery according to an embodiment; 1 is a diagram illustrating an example of a configuration of a battery exchange device according to an embodiment; FIG. 2 illustrates an example of a configuration of a management server according to an embodiment. FIG. 10 is a diagram illustrating an example of the contents of a user management table. FIG. 10 is a diagram illustrating an example of the contents of a state table. FIG. 2 is a diagram illustrating an example of a configuration of a user card according to an embodiment. 10 is a flowchart illustrating an example of a flow of pre-use processing executed by the battery exchange system of the embodiment. 10 is a flowchart illustrating an example of the flow of a service providing process executed by the battery exchange system of the embodiment. FIG. 1 is a first diagram showing an example of a viewing screen for information regarding usage fees. FIG. 2 is a second diagram showing an example of a viewing screen for information regarding usage fees.

Embodiments of the authentication system and authentication method of the present invention will be described below with reference to the drawings. In the following description, the battery exchange system manages multiple battery exchange devices (charging/discharging stations) that accept the return and rental of removable batteries that supply power to electric vehicles. The electric vehicles are equipped with one or more removable batteries rented from the battery exchange devices and run on the power supplied by the installed removable batteries. The electric vehicles may also be hybrid electric vehicles or fuel cell vehicles that run on a combination of a removable battery and an internal combustion engine such as a diesel engine or gasoline engine. Electric vehicles applicable to the battery exchange system include electric motorcycles, electric bicycles, electric tricycles, electric four-wheeled vehicles, hybrid vehicles, electric scooters, robots, etc. The multiple removable batteries installed in the electric vehicles may be rented to users as a battery unit.

<Overall configuration of battery exchange system 1>
FIG. 1 is a diagram illustrating an example of the overall configuration of a battery exchange system 1 according to an embodiment. The battery exchange system 1 is a system that provides a battery exchange service to a user U. The battery exchange service is a service that charges and replaces (returns or lends) removable batteries 100, which are the driving sources of electric vehicles 10. The battery exchange system 1 includes, for example, a plurality of removable batteries 100, a plurality of battery exchange devices 200, and a management server 300. A user terminal device 400 is an information processing device used by a user U of the battery exchange system 1. The management server 300 is communicably connected to the plurality of battery exchange devices 200 and the user terminal device 400 via a network NW. An electric vehicle 10 may be communicably connected to the network NW. The network NW includes, for example, the Internet, a cellular network, a Wi-Fi network, a wide area network (WAN), a local area network (LAN), Bluetooth (registered trademark), and the like. The management server 300 is an example of a "server device."

The battery exchange device 200 is a device that charges and exchanges (returns and lends) the removable battery 100, which is the driving source of the electric vehicle 10. The removable battery 100 is detachably attached to the electric vehicle 10. The removable battery 100 may be a power supply device used for applications such as a mobile portable power source. The battery exchange device 200 may also discharge the removable battery 100 for grid connection, etc.

In the battery exchange system 1 shown in the example of FIG. 1, user U uses user terminal device 400 to apply for a battery exchange service to management server 300. When management server 300 accepts user U's application, it notifies product provider D of this fact. Upon receiving this notification, product provider D delivers products for using the battery exchange service to user U who has applied for the service in accordance with the notification. Product provider D is, for example, a dealer that sells electric vehicles 10 or a leasing company that rents electric vehicles 10. Product provider D may also be the manufacturer of electric vehicles 10. Product provider D delivers to user U the electric vehicle 10, the removable battery 100, and the user card 30 as products for using the battery exchange service. If user U owns an electric vehicle 10 that can use the removable battery 100, product provider D may deliver to user U the removable battery 100 and the user card 30 as products for using the battery exchange service. The user U can use the battery exchange service by activating the provided user card 30 in the battery exchange system 1. The battery exchange service is performed by the battery exchange system 1 shown in the example of Fig. 1. Each component will be described below in order.

[Electric vehicle 10]
The electric vehicle 10 is a vehicle that detachably mounts a removable battery 100. The example in FIG. 1 shows a saddle-ride type electric vehicle (electric two-wheeler) 10-1 and an in-cabin type electric vehicle (electric four-wheeler) 10-2, both of which are driven by an electric motor powered by power supplied from a power storage unit 120 (described below) of the removable battery 100. For example, the electric vehicle 10-1 shown in FIG. 1 can be equipped with two removable batteries 100, and the electric vehicle 10-2 can be equipped with three removable batteries 100. In this way, the number of removable batteries that can be mounted varies depending on the type and shape of the electric vehicle 10. Furthermore, different removable batteries may be usable depending on the vehicle model. In the following description, the electric two-wheeler will mainly be referred to as the "electric vehicle 10."

2 is a diagram showing an example of the configuration of the electric vehicle 10 according to the embodiment. The electric vehicle 10 includes, for example, a battery connection unit 12, a vehicle control unit 14, a driving force output device 16, vehicle sensors 18, an HMI (Human Machine Interface) 20 , a GNSS (Global Navigation Satellite System) receiver 22, and a communication unit 24.

The battery connection unit 12 is electrically connected to the connection unit 150 (described below) of the removable battery 100 when the removable battery 100 is attached to the electric vehicle 10. The battery connection unit 12 includes, for example, a power line connection terminal (battery terminal) for receiving power from the removable battery 100, and a communication line connection terminal for data communication between the removable battery 100 and the vehicle control unit 14.

The vehicle control unit 14 acquires measurement results from the vehicle sensors 18, acquires a value representing the state of charge (SOC: State of Charge) of the power storage unit 120 from the BMU (Battery Management Unit) 110 (described below) of the removable battery 100, and acquires the position of the electric vehicle 10 from the GNSS receiver 22. Based on the acquired data, the vehicle control unit 14 controls the driving force output device 16 in response to operation of an operator (not shown) or by autonomous driving. The vehicle control unit 14 may output the position information of the electric vehicle 10 acquired from the GNSS receiver 22 to the removable battery 100 via the battery connection unit 12.

The driving force output device 16 includes, for example, an electric motor, an inverter, and an ECU (Electronic Control Unit) that controls the inverter. The ECU controls the power supplied to the electric motor from the removable battery 100, for example, by controlling the inverter. In this way, the ECU controls the driving force (torque) output by the electric motor to the drive wheels. The driving force output device 16 also controls the output frequency of the inverter to be lower than the rotation speed of the drive wheels, thereby operating the electric motor as a regenerative brake and converting the braking energy of the drive wheels into electrical energy, which can charge the removable battery 100.

The vehicle sensors 18 include various sensors such as a speed sensor, an acceleration sensor, a rotational speed sensor, an odometer, and others mounted on the electric vehicle 10. The vehicle sensors 18 output the measurement results to the vehicle control unit 14.

The HMI 20 outputs various information to the user of the electric vehicle 10 and accepts input operations from the occupant. The HMI 20 includes, for example, various display devices (which may be touch panels) such as a HUD (Head Up Display) and a meter display unit, a speaker, etc.

The GNSS receiver 22 determines the position of the electric vehicle 10 based on radio waves received from GNSS satellites such as GPS satellites.

The communication unit 24 communicates with the management server 300 via the network NW. For example, the communication unit 24 transmits the position information of the electric vehicle 10 measured by the GNSS receiver 22 to the management server 300 at an arbitrary timing, together with a vehicle ID serving as identification information for identifying the vehicle. Here, arbitrary timing refers to, for example, every predetermined time interval or every predetermined mileage, when the electric vehicle 10 is started or stopped, or at a predetermined time. The communication unit 24 may also transmit the position of the electric vehicle 10 to the management server 300 upon receiving an inquiry about the position of the electric vehicle 10 from the management server 300. In addition to the position information of the electric vehicle 10, the communication unit 24 may also transmit the charge status of the two removable batteries 100 mounted on the electric vehicle 10 to the management server 300. The communication unit 24 may also communicate with the battery exchange device 200 via the network NW.

[Detachable battery 100]
3 is a block diagram showing an example of the configuration of the detachable battery 100 according to the embodiment. The detachable battery 100 includes, for example, a power storage unit 120, a BMU 110, and a connection unit 150. The BMU 110 also includes a measurement sensor 130 and a storage unit 140.

The BMU 110 controls the charging and discharging of the power storage unit 120, performs cell balancing, detects abnormalities in the power storage unit 120, derives the cell temperature of the power storage unit 120, derives the charge/discharge current of the power storage unit 120, and estimates the SOC of the power storage unit 120. The BMU 110 stores abnormalities, failures, etc. of the power storage unit 120 identified based on the measurement results of the measurement sensor 130 in the memory unit 140 as battery status information.

The power storage unit 120 is, for example, a battery pack consisting of multiple cells connected in series. The cells that make up the power storage unit 120 are, for example, lithium-ion secondary batteries (LIBs), nickel-metal hydride batteries, all-solid-state batteries, etc.

The measurement sensor 130 is a voltage sensor, current sensor, temperature sensor, etc. for measuring the state of charge of the storage unit 120. The measurement sensor 130 outputs the measurement results of the measured voltage, current, temperature, etc. to the BMU 110.

The storage unit 140 includes, for example, a non-volatile storage device such as a flash memory. The storage unit 140 stores battery status information. The storage unit 140 may also store a battery ID assigned to the removable battery 100.

The connection unit 150 is electrically connected to the battery connection unit 12 when the removable battery 100 is attached to the electric vehicle 10. Furthermore, when the removable battery 100 is accommodated in one of the multiple slots 210 present in the battery exchange device 200, the connection unit 150 is electrically connected to the battery exchange device 200, and receives a supply of power from the battery exchange device 200 to charge the power storage unit 120. The connection unit 150 includes, for example, a power line connection terminal (battery terminal) and a communication line connection terminal, etc., to correspond to the battery connection unit 12 and the connection unit 220 (described below).

[Battery exchange device 200]
4 is a diagram illustrating an example of the configuration of a battery exchange device 200 according to an embodiment. The battery exchange device 200 includes, for example, a plurality of slots 210, a plurality of connection units 220, a charger 230, a display unit 235, a reading unit 240, an authentication unit 245, a communication unit 250, and a control unit 260.

The slot 210 is a mechanism for receiving and charging the removable battery 100 .
In the battery exchange device 200 shown in the example of FIG. 1 , the slots 210 include, for example, an upper slot 210U (see FIG. 1 ) and a lower slot 210L (see FIG. 1 ). Each slot includes, for example, a turntable that rotates around a vertical axis. A battery storage section for storing the removable battery 100 is provided on the turntable. For example, the battery storage sections are provided in each of the four equal areas of the turntable when viewed from above. Note that the configuration of the battery exchange device 200 for receiving (returning) and lending the removable battery 100 is not limited to this; for example, the storage sections for the removable batteries may be arranged in a matrix. The following description will be given using the above-described turntable-type configuration.

Before a user returns or lends a removable battery 100, the battery replacement device 200 authenticates the user using the authentication unit 245 (described below). For example, the authentication unit 245 permits a user who has been successfully authenticated to return a used removable battery 100 or lend a charged removable battery 100 (hereinafter referred to as a "charged battery 100"). The battery replacement device 200 also has an outlet on the front side. The outlet may be automatically opened when the user is authorized for use through the authentication process performed by the authentication unit 245. The storage compartment located at the outlet can be swapped by rotating a turntable. For example, if the user is authorized for use through the authentication process performed by the authentication unit 245, the battery replacement device 200 positions an empty battery storage compartment at the outlet on the front side, ready to accept the user's return of the removable battery 100. When the removable battery 100 is returned to the battery storage compartment, the battery ID of the removable battery 100 is read. The battery exchange device 200 also rotates the turntable to position the battery storage unit that stores the charged battery 100 at the front removal opening. This allows the user to remove the charged battery 100 and attach it to the electric vehicle 10. At the time of this rental, the control unit 260 transmits the user ID of the user and the battery ID of the newly rented removable battery 100 to the management server 300 as usage information.

A connection part 220 is provided for each of the plurality of slots 210 on the bottom surface of the battery housing section. The connection part 220 is electrically connected to the connection part 150 of the removable battery 100 when the removable battery 100 is housed in the battery housing section. The connection part 220 includes, for example, a connection terminal (battery terminal) for a power line for supplying power to the removable battery 100, and a connection terminal for a communication line for data communication (e.g., serial communication) between the removable battery 100 and the control unit 260.

The charger 230 is connected to the power storage unit 120 of the removable battery 100 via multiple connection units 220. A charger 230 may be provided for each of the multiple connection units 220, or may be provided as a common configuration for the multiple connection units 220. A power source for supplying power to the power storage unit 120 is connected to the charger 230. The charger 230 converts the power supplied from the power source into, for example, direct current and supplies it to the power storage unit 120.

The display unit 235 is, for example, a display device such as an LCD (Liquid Crystal Display) or an organic EL (Electro Luminescence) display. The display unit 235 may also be a touch panel. The display unit 235 displays various information when the user uses the battery exchange device 200 and accepts input of predetermined information (for example, authentication information) from the user.

The reading unit 240 reads authentication information and other information from the user card 30, which is an example of an authentication medium held by the user. The authentication information includes, for example, a card ID and a security code, which are identification information of the user card 30. The reading unit 240 outputs the read authentication information to the control unit 260. Details of the user card 30 will be described later. The reading unit 240 is an example of a "near-field communication unit."

The authentication unit 245 determines whether to permit the user to use the battery exchange device 200 based on the authentication information received from the display unit 235 or read by the reading unit 240. The authentication information may be obtained, for example, from the user's voice collected by a microphone (not shown) of the battery exchange device 200. For example, the authentication unit 245 uses the authentication information to compare it with the authentication list 282 stored in the memory unit 280, and determines that the user has been successfully authenticated if the authentication list 282 contains information matching the authentication information. The authentication list 282 contains authentication information for one or more users and is distributed to each battery exchange device 200 by the management server 300 at a predetermined timing or interval. The battery exchange device 200 permits use of its own device if the authentication list 282 contains authentication information for comparison that matches the authentication information presented by the user (hereinafter referred to as "authentication information"). The memory unit 280 is an example of a "second memory unit."

The authentication list 282 may include information other than the verification authentication information. For example, the authentication list 282 may include information such as the user ID and password of a user authorized to use the battery exchange device 200, an expiration date, the number of removable batteries 100 available for rental, and a status. The expiration date is, for example, the last day of the period during which the battery exchange device 200 can be used. The number of removable batteries 100 available for rental is, for example, the number of removable batteries 100 that can be installed in an electric vehicle 10 associated with the card ID. The status is information indicating the usage status of the battery exchange system 1 in the electric vehicle 10 associated with the card ID. The usage status includes, for example, whether a removable battery 100 is being rented, whether authentication for battery replacement is in progress, or whether usage has been temporarily or permanently suspended due to unauthorized use by the user. By including additional information other than the verification authentication information in the authentication list 282, the battery exchange device 200 can perform processing according to the user authentication result.

For example, if the authentication unit 245 determines that the authentication of a user has been successful, it can determine whether the user satisfies certain usage conditions. The certain usage conditions, for example, are that the current date (date of use) does not exceed the expiration date included in the authentication list 282. The certain usage conditions may also include that the user has not engaged in fraudulent use, etc., and is therefore in an unusable state (suspension of use). For example, the authentication unit 245 may permit the user to use (return and lend) the battery exchange device 200 if the current date does not exceed the expiration date included in the authentication list 282.

Furthermore, if the authentication list 282 does not contain any matching authentication information that matches the authentication information, the authentication unit 245 may send the authentication information from the communication unit 250 to the management server 300 to make an authentication inquiry. In this case, the authentication unit 245 may obtain an authentication result and additional information from the management server 300 as the inquiry result, and if the user authentication is successful, may use the additional information to determine whether or not the specified usage conditions are met. Furthermore, the authentication unit 245 may allow the user to use the battery exchange device 200 if the specified usage conditions are met.

Furthermore, if the user authentication is not successful or if the specified usage conditions are not met, the authentication unit 245 may notify the user by displaying information on the display unit 235 indicating that the device is not available. Note that user authentication using the above-mentioned authentication information does not necessarily need to be performed every time the removable battery 100 is replaced. Furthermore, instead of (or in addition to) the above-mentioned authentication, the authentication unit 245 may perform biometric authentication using biometric information such as the user's fingerprint information, voiceprint information, or iris information. In this case, matching biometric information may be stored in the authentication list 282, and the authentication unit 245 may perform authentication by comparing the biometric information with the matching biometric information.

In the following, we will explain the case where the above-mentioned authentication information for verification is a card ID as identification information for the user card 30, but the authentication information for verification may be information other than a card ID as long as it can identify the user and is recognized by the user card 30. For example, if a user ID or password is displayed or recorded on the user card 30, this information may be used as authentication information for verification.

The communication unit 250 includes wired communication devices such as a terminal adapter or an Ethernet (registered trademark) communication device, and wireless communication devices such as a Wi-Fi adapter or 3G/LTE, 4G, or Bluetooth, and communicates with the management server 300, terminal devices, etc. via the network NW.

The control unit 260 includes, for example, an exchange control unit 262, a charging control unit 264, an authentication list acquisition unit 266, a battery information upload unit 268, a usage information upload unit 270, and a memory unit 280. The exchange control unit 262, the charging control unit 264, the authentication list acquisition unit 266, the battery information upload unit 268, and the usage information upload unit 270 are realized by a hardware processor such as a CPU (Central Processing Unit) executing a program (software). Furthermore, some or all of their functions may be realized by hardware such as an LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), or GPU (Graphics Processing Unit), or may be realized by a combination of software and hardware. The above-mentioned program may be stored in advance in a storage device (a storage device with a non-transitory storage medium) such as an HDD or flash memory of the battery replacement device 200, or may be stored in a removable storage medium such as a DVD, CD-ROM, or memory card, and installed in the storage device of the battery replacement device 200 by inserting the storage medium (non-transitory storage medium) into a drive device, card slot, etc.

The memory unit 280 may be realized by the various storage devices mentioned above, or by an EEPROM (Electrically Erasable Programmable Read Only Memory), a ROM (Read Only Memory), or a RAM (Random Access Memory). The memory unit 280 stores, for example, an authentication list 282, battery information 284, programs, and various other information. The authentication list 282 is distributed by the management server 300. The battery information 284 stores battery IDs assigned to one or more removable batteries 100 managed within the battery exchange device 200, and SOC information (an example of battery status) for each removable battery 100.

Based on the authentication result by the authentication unit 245, the replacement control unit 262 controls the return of a used removable battery 100 (hereinafter referred to as the "used battery 100") mounted on the electric vehicle 10 and the lending of a charged battery 100. For example, the replacement control unit 262 opens the slot 210 for storing the used battery 100 when returning it, or opens the slot 210 in which the charged battery 100 is stored when lending it. The replacement control unit 262 may also determine whether the stored used battery 100 is a genuine (genuine) removable battery. In this case, the replacement control unit 262 acquires the battery ID of the stored removable battery 100 and queries the management server 300 based on the acquired battery ID and user information (user ID, card ID). The management server 300 compares the battery ID and user information acquired from the battery exchange device 200 with the user management table 352, etc., and determines that the battery is a genuine removable battery if matching information is found. Otherwise, it determines that the battery is not a genuine removable battery. Examples of cases where the battery is not a genuine removable battery include a battery that is not a genuine product or a removable battery returned by a user other than the one who originally rented it. If the battery is not a genuine removable battery, the management server 300 temporarily or permanently suspends subsequent use by that user. The management server 300 transmits the above-described processing details to the battery exchange device 200 as an inquiry result. If the battery 100 is a genuine removable battery 100 based on the received inquiry result, the replacement control unit 262 performs the above-described rental control. If the battery 100 is not a genuine removable battery 100, the replacement control unit 262 does not perform rental control, but instead notifies the user of error information or returns the stored used removable battery. The combination of the exchange control unit 262 and the plurality of slots 210 is an example of a "battery exchange unit."

The charging control unit 264 controls the charger 230 so that the storage unit 120 is charged to a predetermined state of charge (e.g., SOC) based on the state of charge of the storage unit 120, etc., obtained from the removable battery 100 via a signal line. The SOC of the storage unit 120 is, for example, sequentially transmitted to the charging control unit 264, and the charging control unit 264 associates the battery ID and SOC information of the removable battery 100 with each other and stores them in the memory unit 280 as battery information 284.

The authentication list acquisition unit 266 records the authentication list distributed from the management server 300 in the memory unit 280 as the authentication list 282. For example, when a new authentication list is distributed from the management server 300, the authentication list acquisition unit 266 replaces the authentication list 282 stored in the memory unit 280 with the newly acquired authentication list.

Furthermore, for example, if the authentication list distributed from the management server 300 is difference information relative to the authentication list 282 already distributed to the battery exchange device 200, the authentication list acquisition unit 266 updates the authentication list 282 based on the difference information. For example, if the difference information includes additional user information, the authentication list acquisition unit 266 adds matching authentication information for the additional user to the authentication list 282. Furthermore, if the difference information includes a specific user, the authentication list acquisition unit 266 deletes the matching authentication list for the specific user from the authentication list 282. A specific user is, for example, a user whose expiration date for using the battery exchange device 200 has passed, a user who has committed fraudulent use, or a user whose usage fees have not been paid and are in arrears. Furthermore, a specific user may include a user who has not used the device for a predetermined period of time since their last use. As described above, by distributing difference information and updating the authentication list 282, the amount of communication data required during the update can be reduced.

The battery information upload unit 268, for example, counts the number of removable batteries 100 that have been fully charged (charged to a specified SOC) at any given time, and transmits this count to the management server 300 along with its own device ID (identification information for identifying the battery exchange device 200) and battery ID. Here, "any given time" includes, for example, the time when charging of a removable battery 100 is completed (or when the battery has been charged to a desired SOC) or the time when a removable battery 100 is lent out. In other words, the "any given time" may be the time when a change occurs in the number of removable batteries or the number of charged batteries stored in the battery exchange device 200. Furthermore, the battery information upload unit 268 may include in the information transmitted the "remaining time required for charging" calculated from the charging speed, capacity, etc., for each removable battery 100 currently being charged. The combination of the charging control unit 264 and the battery information upload unit 268 is an example of a "detection unit."

The usage information upload unit 270 transmits the usage status of each user's battery exchange device 200 and its own device ID as usage information to the management server 300 at any time. Here, "any time" refers, for example, to the time when authentication by the authentication unit 245 is permitted and the replacement of the removable battery (e.g., return or rental) is performed. The usage status may include, for example, the user ID, card ID, battery ID of the returned removable battery 100, battery ID of the rented removable battery 100, date and time of replacement (date and time of use), etc. Information uploaded at any time by the battery information upload unit 268 or usage information upload unit 270 may be temporarily stored in the storage unit 280.

[Management Server 300]
FIG. 5 is a diagram illustrating an example of the configuration of the management server 300 according to the embodiment. The management server 300 includes, for example, a communication unit 310, a management unit 320, a distribution unit 330, a usage fee calculation unit 340, and a storage unit 350. The management unit 320 and the distribution unit 330 are implemented by, for example, a hardware processor such as a CPU executing a program (software). Furthermore, some or all of their functions may be implemented by hardware such as an LSI, ASIC, FPGA, or GPU, or may be implemented by a combination of software and hardware. The above-described program may be stored in advance in a storage device (a storage device having a non-transitory storage medium) such as an HDD or flash memory of the management server 300, or may be stored in a removable storage medium such as a DVD, CD-ROM, or memory card, and installed in the storage device of the management server 300 by inserting the storage medium (non-transitory storage medium) into a drive device, card slot, or the like.

The memory unit 350 may be realized by the various storage devices mentioned above, or by EEPROM, ROM, RAM, etc. The memory unit 350 stores, for example, a user management table 352, a status table 354, map information 356, billing information 358, programs, and various other information.

Figure 6 shows an example of the contents of the user management table 352. The user management table 352 contains information in which the user ID and card ID are associated with a password, expiration date, number of batteries that can be installed, usable battery type, status, loaned battery ID, usage history, detailed information, etc. For example, the card ID is an example of information required for user authentication.

The expiration date is set, for example, when registering to use the battery exchange system 1 or when paying the usage fee. The expiration date may be, for example, a fixed period (e.g., one year from the time of registration or renewal), or may be a deadline set in association with the expiration date (vehicle inspection date) set by the vehicle inspection (vehicle renewal inspection set by the government, etc.) of the electric vehicle 10. The number of mountable batteries is the number of batteries that can be mounted on the electric vehicle 10 associated with the card ID. The usable battery type is information such as the type, size, model number, etc. of the removable battery 100 that can be used by the electric vehicle 10 associated with the card ID.

The loaned battery ID is identification information for the removable battery 100 currently loaned to the electric vehicle 10 associated with the card ID. The usage history is information relating to the past usage history of the battery exchange system 1 associated with the user ID and card ID. The usage history includes, for example, the device ID of the battery exchange device 200 used, the date and time of use, etc. The usage history may also include, for example, information uploaded by the usage information upload unit 270. The detailed information includes, for example, personal information such as the user's address, age, and gender obtained at the time of user registration. The detailed information may also include performance information and vehicle model information for the electric vehicle 10 associated with the card ID. The performance information for the electric vehicle 10 is, for example, the mileage when one charged battery 100 is installed.

Figure 7 is a diagram showing an example of the contents of the status table 354. The status table 354 stores information regarding the status of multiple battery exchange devices 200 managed by the battery exchange system 1. The status table 354 may include, for example, information uploaded by the battery information upload unit 268. The status table 354 is information that associates, for example, a device ID, the number of charged batteries in the battery exchange device 200 associated with the device ID, and the location of the battery exchange device 200. If the uploaded information includes the remaining time required to charge each removable battery 100 as described above, the status table 354 may also include information on the number of removable batteries 100 currently being charged and the remaining time for each removable battery 100. The status table 354 may also include performance information for the removable batteries 100. Performance information for the removable batteries 100 includes, for example, information such as the amount of power when fully charged, the number of charges, and the degree of deterioration.

Map information 356 may include, for example, information on the location of battery exchange device 200 in map coordinates, as well as facility information (POI: Points of Interest) such as convenience stores, restaurants, accommodations, and various activity facilities. Map coordinates are, for example, a three-dimensional or two-dimensional coordinate system measured by a GNSS receiver. Map information 356 may also include the location of roads in map coordinates and other road information. Road information includes, for example, road type (e.g., general road or expressway), number of lanes, traffic regulation information, installed road signs, legal speed limits, radius of curvature (or curvature), width, gradient, unevenness, etc. Map information 356 may be updated at any time by communicating with other devices via communication unit 310.

The communication unit 310 is equipped with a wired communication device such as a terminal adapter or an Ethernet (registered trademark) communication device, or a wireless communication device such as a Wi-Fi adapter or 3G/LTE, 4G, or Bluetooth, and communicates with the battery exchange device 200, the electric vehicle 10, etc. via the network NW.

The management unit 320 manages the user's usage status (including authentication, etc.) when replacing the removable battery 100 shown in Figure 6. For example, the management unit 320 manages the content of the matching authentication information required when performing authentication in each battery replacement device 200, and manages the timing of delivering the matching authentication information, etc. Furthermore, when an authentication inquiry is made from the battery replacement device 200, the management unit 320 may perform authentication using the authentication information acquired with the inquiry and the user management table 352, and may transmit the authentication result and matching authentication information based on the authentication result to the battery replacement device 200.

The management unit 320 also accepts new user registrations (applications for use) and requests to change registered information, and updates the user management table 352 based on the accepted information. New registrations and changes to registered information are made, for example, by the user communicating with the management server 300 from a terminal device or the like. The management unit 320 also updates the status table 354 based on uploaded information acquired from the battery replacement device 200. The management unit 320 may also manage, for example, the billing status and expiration date for each user ID or card ID.

The distribution unit 330 generates an authentication list based on information contained in the user management table 352 and information about the battery obtained from the battery replacement device 200, etc., and distributes the generated authentication list to multiple battery replacement devices.

The distribution unit 330 generates an authentication list for each battery exchange device 200 and distributes the generated authentication information for verification to the corresponding battery exchange device 200. The distribution unit 330 may also generate an authentication list that includes the authentication information for verification of all users as an authentication list common to all battery exchange devices 200. While standardizing the authentication list reduces management load, it may also result in the authentication list becoming larger. Therefore, whether or not to standardize the authentication list should be selected based on the amount of effort, time, and resource consumption that can be tolerated in distributing the authentication list. The distribution unit 330 may store information about the distributed authentication list in the storage unit 350 as a distribution history.

The distribution unit 330 distributes the generated authentication list at any timing. "Any timing" refers to, for example, a predetermined time (e.g., 10:00 and 20:00 every day) or a predetermined cycle (e.g., half a day, one day, or one week). For example, the distribution unit 330 may execute the process of generating the above-mentioned authentication list a predetermined time before the timing of distribution.

The distribution unit 330 may generate and distribute the authentication list at any timing, but the convenience of the battery exchange service can be improved by performing the generation and distribution of the authentication list at the following timings. For example, the distribution unit 330 may be configured to distribute the authentication list using differential information frequently (e.g., every 10 minutes) and distribute the entire authentication list less frequently (e.g., once a day). For example, by updating the authentication list by distributing differential information at times when the communication bandwidth is relatively congested, such as during the day, it is possible to enable new users to start using the service promptly after activating their user card 30. Furthermore, by updating the authentication list by distributing the entire authentication list at times when the communication bandwidth is relatively less congested, such as at night, it is possible to reliably reflect updates that occur during the course of a day, for example, in the battery exchange device 200.

The usage fee calculation unit 340 identifies the user of the returned used battery 100 based on the card information received from the battery exchange device 200, and calculates the usage fee for the removable battery 100 used by the user over a specified period based on the battery information of the used battery 100. The usage fee calculation unit 340 generates billing information 358 regarding the fee to be billed to the user based on the calculated usage fee, and stores the generated billing information 358 in the memory unit 350.

[User card 30]
FIG. 8 is a diagram illustrating an example of the configuration of a user card 30 according to an embodiment. The user card 30 is an example of an authentication medium held by a user. The user card 30 is a medium storing authentication information and other information. The authentication information includes, for example, a card ID and a security code. The user card 30 is, for example, a contactless IC card. Alternatively, the user card 30 may be a contact IC card. For example, the user card 30 is issued for each battery exchange service contract. The contract includes the number of removable batteries 100 to be used and is associated with the electric vehicle 10 that uses the removable battery 100. In this case, the authentication information includes a card ID and a vehicle ID as identification information for identifying the user card 30. The authentication medium held by the user may be an electronic device such as a smartphone or a tablet terminal. The reader 240 may acquire the authentication information not only through communication but also by optically reading information from a code image such as a QR code (registered trademark, the same applies hereinafter).

The user card 30 also has a display unit 31 that displays card information. The card information is information required when a user activates the user card 30 provided to them when they begin using the battery replacement service. The card information includes, for example, identification information for the user card 30 (hereinafter referred to as "card ID") and a security code. Figure 8 shows an example of a user card 30 in which the display unit 31 displays a QR code 31A indicating card information, a card ID 31B (e.g., 10-digit alphanumeric characters), and a security code 31C (e.g., a 4-digit number).

For example, the display unit 31 is a medium such as paper or a sticker attached to the surface of the user card 30. Furthermore, for example, the display unit 31 may be an area on the surface of the user card 30 where card information is printed or engraved. Furthermore, if the user card 30 is equipped with a display device such as a liquid crystal display or an organic EL display, the display unit 31 may display the card information using such a display device. Furthermore, the user card 30 may have a general card shape such as a cash card or a credit card, or may have a different shape. For example, the user card 30 may be a so-called key holder that can be attached to the key of the electric vehicle 10 , or may be an electronic tag .

In an embodiment of the battery exchange system 1 having such a configuration, for example, a user can activate the user card 30 by reading the QR code 31A displayed on their user card 30 using the user terminal device 400 and transmitting the card information read from the QR code 31A to the management server 300. Alternatively, for example, a user can manually input the card ID 31B and security code 31C displayed on their user card 30 into the user terminal device 400, and then transmit the input card information to the management server 300 to activate the user card 30. In this way, by displaying a character string indicating the card information on the user card 30 in addition to the encoded card information, the user can activate the user card 30 even if the QR code 31A cannot be read. Note that the battery exchange system 1 may also be configured to require the user to manually input the security code 31C even when reading the card information from the QR code 31A.

The user terminal device 400 is equipped with a camera 410 for capturing an image of the QR code 31A, a function for recognizing and decrypting the QR code from the image captured by the camera 410, an input unit (such as a touch panel or keyboard) for inputting card information as a string of characters, and a communication unit (an example of a transmission unit) for transmitting the input card information to the management server 300, so that the user can perform the activation process for the user card 30 described above. The camera 410 is an example of an "imaging unit."

In addition, the user card 30 may be configured to display card information on the display unit 31, as well as store the card information together with authentication information. In this case, the user terminal device 400 may be configured to include a reading unit that reads information from the memory unit of the user card 30, and to transmit the card information read by the reading unit to the management server 300.

[Processing flow]
The following describes the flow of processing executed by the battery exchange system 1 of the embodiment. The processing executed by the battery exchange system 1 is broadly divided into processing from when a user applies for use of the battery exchange service until the user card 30 is activated (hereinafter referred to as "pre-use processing"), and processing performed when the user uses the activated user card 30 to use the battery exchange service (hereinafter referred to as "service provision processing"). Therefore, the following will describe each type of processing separately.

[Pre-use processing]
FIG. 9 is a flowchart illustrating an example of the flow of pre-use processing executed by the battery exchange system 1 according to the embodiment. In the example of FIG. 9 , first, a user uses the user terminal device 400 to apply for the battery exchange service to a service provider (hereinafter simply referred to as the “provider”) of the battery exchange service (step S101: membership). Specifically, the user transmits their personal information to the management server 300, which accepts the application (step S102). Upon accepting the application, the provider assigns membership information to the user. The management server 300 stores the assigned membership information in the storage unit 350 (first storage unit). The personal information includes, for example, a copy of identification documents (such as a driver's license or health insurance card). Here, the provider is assumed to be a business entity that serves as a contact point for providing the battery exchange service to users under contract with the main operator of the battery exchange service (hereinafter simply referred to as the “service vendor”). The provider coordinates various information between the user and the service vendor. The service vendor may also include a provider, in which case the provider's processing may be executed by the management server 300 .

Next, the provider verifies the user's identity based on the personal information uploaded from the user terminal device 400 (step S103). If the user's identity cannot be verified, the provider returns to step S102. On the other hand, if the user's identity is verified in step S103, the provider prompts the user to add a contract plan, and the user then adds the desired contract plan (step S104). The processing up to this point is the enrollment process for the battery exchange service, and is carried out between the user and the provider.

When the enrollment process is complete, the management server 300 (service vendor) is notified of this. In the management server 300, the management unit 320 confirms that the service can be provided for the contract plan added by the user (step S105), and then registers user information related to the provision of the battery replacement service under that contract plan in the user management table 352 (step S106). For example, the management unit 320 registers the user information after confirming the availability of items necessary for service provision and the user's eligibility to use the contract plan. Once the management unit 320 has completed the registration of the user information, it notifies the user of instructions to pay the fee required to start using the battery replacement service under that contract plan (hereinafter referred to as the "initial fee") (step S107). After notifying the user of the instructions to pay the initial fee in step S107, the management unit 320 waits for the user to make the payment (step S108). If the payment is confirmed, the management unit 320 prompts the user to activate the user card 30. If the deposit cannot be confirmed here, the management unit 320 continues to wait for the deposit to be made by sending another deposit notification or the like.

Meanwhile, after adding a contract plan in step S104, the user receives a notification from management server 300 instructing them to pay the initial usage fee. Upon receiving this notification, the user pays the initial usage fee (step S109). Once this payment is confirmed by management server 300, management server 300 notifies the user that the battery replacement service will become available upon activation of user card 30. Meanwhile, product provider D is notified that the initial usage fee has been paid, and product provider D delivers to the user the product required to use the battery replacement service. The user then uses the delivered user card 30 to activate the user card 30 (step S110).

Specifically, the user logs in to the management server 300 by entering their membership information (user ID and password) provided as a result of the identity verification in step S103 into the user terminal device 400, and transmits card information readable from the user card 30 to the management server 300. The reading and input of the card information may be achieved using the reading function of the user terminal device 400, or may be achieved by the user manually entering information read visually from the user card 30. In the management server 300, the management unit 320 references the user management table 352 based on the card information and membership information received from the user terminal device 400, selects the record of the user card 30 to be activated, and updates the status value in the selected record to a value indicating that the battery replacement service is available, thereby activating the target user card 30.

When activating the user card 30 described above, the management unit 320 provides a login function based on member information to the user accessing the management server 300. This login function allows the user to send member information by logging in to the management server 300. In this way, by having the user send card information while logged in, the effort of having the user send member information can be eliminated.

When activating the user card 30, it is possible that a third party who obtains the user's card ID may submit a fraudulent application for use. Therefore, to prevent the acceptance of such fraudulent applications, the management unit 320 may be configured to verify the legitimacy of the requested activation based on the security code 31C included in the received card information. For example, upon accepting a usage application, the management unit 320 issues a security code to be displayed or recorded on the user card 30 of the user who made the usage application, notifies the product provider D, and stores the issued security code in the memory unit 350 in association with the user ID of the user. In this manner, upon accepting a request to activate the user card 30, the management unit 320 can verify the legitimacy of the activation request by verifying that the security code submitted by the user matches the security code previously stored in the memory unit 350. Note that validity verification using a security code is not required, so if validity verification is omitted, the security code need not be included in the card information.

Next, in the management server 300, after the user card 30 has been activated, the distribution unit 330 generates an authentication list (step S111). The distribution unit 330 distributes the generated authentication list to each battery replacement device 200 (step S112: data synchronization). By completing the processing up to this point, the user can use the battery replacement device 200 in accordance with the contract plan for which they have applied.

[Service provision processing]
Fig. 10 is a flowchart showing an example of the flow of a service provision process executed by the battery exchange system 1 of the embodiment. In the example of Fig. 10, first, a user presents the user card 30 provided to the user to the battery exchange apparatus 200 to be used (step S201). More specifically, the user brings the user card 30 close to the reading unit 240 of the battery exchange apparatus 200, causing the battery exchange apparatus 200 to read the card information. The battery exchange apparatus 200 reads the card information (card ID, security code) from the presented user card 30 (step S202) and performs user authentication processing based on the read card information (step S203).

Specifically, the authentication unit 245 determines whether the card ID (authentication information) included in the read card information matches any of the card IDs (verification authentication information) included in the authentication list 282. If there is no matching card ID, the authentication unit 245 determines that authentication has failed, and if there is a matching card ID, it determines that authentication has succeeded. If authentication fails, the authentication unit 245 returns to step S202, but if authentication is successful, it accepts the return of the used battery 100 by the user (step S204) and instructs the replacement control unit 262 to collect the used battery 100. Upon receiving this instruction, the replacement control unit 262 performs the operation of collecting the used battery 100 (step S205).

After collecting the used battery 100, the replacement control unit 262 then performs a rental operation for a charged battery 100 (step S206). In response to this rental operation, the user obtains a charged battery 100 from the battery replacement device 200 (step S207) and begins using the obtained charged battery 100 (step S208). The charged battery 100 that has been started to be used here is returned to the battery replacement device 200 as a used battery 100 in the same manner the next time the battery is returned, and is replaced with a new charged battery 100.

On the other hand, when the used battery 100 is collected in step S205, the battery information upload unit 268 in the battery exchange device 200 uploads the battery information of the returned used battery 100 to the management server 300 (step S209). In response to this battery information upload, the usage fee calculation unit 340 in the management server 300 calculates the usage fee to be charged to the user for the battery exchange service based on the uploaded battery information (step S210). For example, the battery information upload unit 268 can calculate the amount of discharge of the returned used battery 100 due to use by the user based on the SOC information included in the battery information 284, and calculate the usage fee by multiplying this amount of discharge by a predetermined unit price. The predetermined unit price may include the unit price of electricity as well as a unit price for recovering the loss of deterioration due to discharge of the removable battery 100. Furthermore, if the amount of regenerated power generated by driving the electric vehicle 10 can be obtained in addition to the amount of discharge, the usage fee calculation unit 340 may calculate the usage fee by subtracting the fee for the line power amount from the fee calculated based on the amount of discharge. The usage fee calculation unit 340 notifies the provider of the calculated usage fee for the user.

Next, the provider bills the user for the usage fee notified by the management server 300 (step S211) and confirms that the billed usage fee has been paid (step S212), thereby completing one cycle of use of the removable battery 100 and settlement of the usage fee. Note that by billing the user for the usage fee in step S211, the provider can provide the user with information related to the billed usage fee (step S213). For example, the provider issues the user an invoice that includes access information to a website that provides information about the usage fee. The invoice may be issued on paper, by email, or as information viewable on a website. In this case, the user can access the website using the user terminal device 400 and view information about the usage fee on a screen such as that shown in Figures 11 and 12 below. The user then confirms the information about the usage fee and pays the usage fee (step S214). The website is implemented, for example, by the management unit 320 of the management server 300. The management unit 320 generates a web page based on the usage fee information generated by the usage fee calculation unit 340 and causes the generated web page to be displayed on the user terminal device 400 .

Figures 11 and 12 are diagrams showing examples of viewing screens for information regarding usage fees. Figure 11 shows viewing screen D1, which displays billing information for a month specified by the user. Viewing screen D1 has, for example, a display area D11 of a user interface for specifying the month, an area D12 displaying the number of contracts to be billed, an area D13 displaying the total amount to be billed for the specified month (total billed amount), and an area D14 displaying the payment deadline for the total billed amount. Viewing screen D1 is configured so that the number of contracts displayed in area D12, the total billed amount displayed in area D13, and the payment deadline displayed in area D14 change depending on the month selected via the user interface in area D11.

Figure 12 shows the viewing screen D2 that displays detailed information about the bill for the month specified by the user. The viewing screen D2 has, for example, an area D21 that displays detailed information about the charges for the month specified by the user (basic charge, electricity usage charge, etc.), and an area D22 that displays historical information about the user's use of the battery exchange device 200. By checking this viewing screen, the user can confirm the details of the charges billed by the provider when paying the usage fee.

[Variations]
In the above-described embodiment, the battery exchange device 200 queries the management server 300 for authentication information if the authentication information entered by the user is not stored in the authentication list 282 stored in the storage unit 280. However, there may be cases where communication between the battery exchange device 200 and the management server 300 is disrupted due to a disaster such as a typhoon or earthquake, a system error, or the like, making it impossible to query the management server 300. Therefore, when querying the management server 300 for user authentication information, the battery exchange device 200 may lend out a charged battery 100 if it is unable to communicate with the management server 300 for a predetermined period of time and if certain conditions are met, regardless of whether authentication was successful. Examples of cases where the predetermined conditions are met include when the authentication information entered by the user for user authentication matches the registered user information of the battery exchange system 1, or when the authentication information includes a flag that permits lending when communication is unavailable. This allows the removable battery 100 to be lent out without waiting for communication to be restored, even if proper user authentication is not possible due to a communication error or the like.

When lending out a removable battery 100 using the method described above, the replacement control unit 262 stores the authentication information from the user in the memory unit 280, and after communication is restored, queries the management server 300 for the authentication information in the memory unit 280. If matching authentication information exists in the user management table 352 and the usage conditions are met, the management server 300 updates the usage history for that user. On the other hand, if matching authentication information does not exist in the user management table 352, or if the usage conditions are not met, the management server 300 suspends subsequent use by the user. In this case, the management server 300 sets the status in the user management table 352 to "suspended use" and prohibits future use of the removable battery.

The distribution unit 330 may also distribute a list of suspended users (unavailable list) to the battery replacement device 200 at any timing. Here, "any timing" refers to, for example, every predetermined time interval or when the number of users whose status is suspended reaches a predetermined number. The battery replacement device 200 to which the unavailable list has been distributed may compare the authentication information from the user with the unavailable list during authentication, and if there is no match, may determine that the user has been successfully authenticated.

The management server 300 may also provide a function to change the enabled status of a user card 30 to a disabled status when the user loses the user card 30. For example, the management unit 320 accepts a user's login using membership information and provides the logged-in user with a user interface that allows the logged-in user to select the user card 30 that they wish to disable from among the user cards 30 currently under contract. This allows the user to log in to the management server 300 using the user terminal device 400, and the management unit 320 changes the status of the selected user card 30 to a disabled status, thereby disabling the lost user card 30.

As described above, the battery exchange system 1 (an example of an authentication system) of the embodiment includes a user card 30 (an example of an authentication medium) provided to a user, a battery exchange device 200 (an example of a target device) that can execute a predetermined operation when the user is successfully authenticated through communication with the user card 30, and a management server 300 (an example of a server device) that receives, from the user terminal device 400, the identification information of the user card 30 recognized by the user terminal device 400 and the input information entered into the user terminal device 400 as the user's membership information. In the battery exchange system 1 of the embodiment, the management server 300 includes a memory unit 350 (an example of a first memory unit) and a management unit 320 (an example of an authentication medium registration unit), and the battery exchange device 200 includes an authentication unit 245. The storage unit 350 stores the user's membership information in advance, and the management unit 320 registers the user's user card 30 as a valid authentication medium when the input information received from the user terminal device 400 matches the membership information stored in the storage unit 350. Furthermore, the authentication unit 245 communicates with the user card 30 registered as a valid authentication medium to authenticate the user of the user card 30.

According to the battery exchange system 1 of this embodiment configured as described above, the user who has applied to use the battery exchange service can take the initiative in linking the user with the authentication medium to be supplied to that user, thereby reducing the management burden on the operator involved in providing the battery exchange service.

The above describes the form for implementing the present invention using embodiments, but the present invention is in no way limited to these embodiments, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention.

1... Battery exchange system, 10... Electric vehicle, 12... Battery connection unit, 14... Vehicle control unit, 16... Driving force output device, 18... Vehicle sensor, 22... GNSS (Global Navigation Satellite System) receiver, 24... Communication unit, 30... User card, 31... Display unit, 31A... QR code, 31B... Card ID, 31C... Security code, 100... Detachable battery, 110... BMU (Battery Management Unit) Unit), 120...power storage unit, 130...measurement sensor, 140...storage unit, 150...connection unit, 200...battery exchange device, 210...plurality of slots, 210U...upper slot, 210L...lower slot, 220...plurality of connection units, 230...charger, 235...display unit, 240...reading unit, 245...authentication unit, 250...communication unit, 260...control unit, 262...exchange control unit, 264...charging control unit, 266...authentication list acquisition unit, 268...battery information upload unit, 270...Usage information upload unit, 280...Memory unit, 282...(authentication information) authentication list, 282...related verification authentication information authentication list, 282...Authentication list, 284...Battery information, 300...Management server, 310...Communication unit, 320...Management unit, 330...Distribution unit, 340...Usage fee calculation unit, 350...Memory unit, 352...User management table, 354...Status table, 356...Map information, 358...Billing information, 400...User terminal device, 410...Camera

Claims (13)

an authentication medium provided to a user for authenticating the user;
a target device that is capable of executing a predetermined operation when the authentication of the user using the authentication medium is successful;
a server device that receives, from a terminal device of a user, identification information of an authentication medium that has been input into the terminal device of the user before the user uses the medium for authentication , and input information that has been input into the terminal device as membership information of the user;
Equipped with
The server device
a first storage unit that pre-stores a group of member information items that are a plurality of pieces of member information for a plurality of users including the one user;
an authentication medium registration unit that, when the member information of the one user included in the input information received from the terminal device matches one piece of member information included in the member information group stored in the first storage unit, newly registers the one authentication medium of the one user as a valid authentication medium and transmits valid identification information, which is the one identification information of the one authentication medium registered as the valid authentication medium, to the target device;
Equipped with
The target device is
a second storage unit that stores the valid identification information received from the server device;
an authentication unit that authenticates a user of the target device using the authentication medium registered as a valid authentication medium;
Equipped with
the authentication unit authenticates the one user when the one identification information acquired from the one authentication medium matches the valid identification information stored in the second storage unit;
Authentication system. the authentication medium registration unit transmits, to the target device, the valid identification information of the valid authentication medium that has not yet been transmitted to the target device at a predetermined frequency;
The authentication system of claim 1 . the server device records the valid identification information of the valid authentication medium in the first storage unit;
the authentication unit of the target device inquires of the server device whether the one identification information acquired from the one authentication medium matches the valid identification information stored in the first storage unit, and authenticates the one user if they match;
The authentication system of claim 1 . the authentication medium further includes a display unit that displays a graphic in which the identification information is encoded,
The terminal device
an imaging unit that captures an image of the figure;
a reading unit that decodes the graphic image captured by the imaging unit to obtain the identification information;
a transmitting unit that transmits the identification information acquired by the reading unit to the server device as the input information;
Equipped with
An authentication system according to any one of claims 1 to 3. The target device is
A battery exchange device further comprising a battery exchange unit that collects used batteries and provides a stored battery for exchange,
The battery exchange unit of the battery exchange device
When the user is authenticated by the authentication unit, the used battery is replaced with the stored battery.
An authentication system according to any one of claims 1 to 4. the battery exchange device further includes a detection unit that detects the amount of use of the used battery when the used battery is collected ;
the battery replacement unit transmits to the server device the identification information of the authentication medium acquired in the authentication of the user by the authentication unit and information on the amount of use of the used battery detected by the detection unit .
The authentication system according to claim 5 . The server device
an identification unit that identifies a user of the used battery based on the identification information of the authentication medium received from the battery exchange device;
The authentication system of claim 6. a usage fee calculation unit that calculates a usage fee for the used battery used by the user identified by the identification unit based on the information on the usage amount,
The authentication system of claim 7. an authentication medium provided to a user for authenticating the user;
a target device that is capable of executing a predetermined operation when the authentication of the user using the authentication medium is successful;
a server device that receives, from the terminal device of the user, the identification information of the authentication medium that has been input to the terminal device and the input information that has been input to the terminal device as the member information of the user;
Equipped with
The server device
a first storage unit that stores in advance a group of member information that is a plurality of pieces of member information of a plurality of users including the user;
an authentication medium registration unit that, when the member information included in the input information received from the terminal device matches one piece of member information included in the member information group stored in the first storage unit, registers the authentication medium of the user as a valid authentication medium and transmits valid identification information, which is the identification information of the authentication medium registered as the valid authentication medium, to the target device;
Equipped with
The target device is
a second storage unit that stores the valid identification information received from the server device;
an authentication unit that authenticates the user using the authentication medium that has been registered as the valid authentication medium;
Equipped with
the authentication unit authenticates the user when the identification information acquired from the authentication medium matches the valid identification information stored in the second storage unit;
The target device is
A battery exchange device further comprising a battery exchange unit that collects used batteries and provides a stored battery for exchange,
The battery exchange unit of the battery exchange device
When the user is authenticated by the authentication unit, the used battery is replaced with the stored battery.
Authentication system. the battery exchange device further includes a detection unit that detects the amount of use of the used battery when the used battery is collected;
the battery replacement unit transmits to the server device the identification information of the authentication medium acquired in the authentication of the user by the authentication unit and information on the amount of use of the used battery detected by the detection unit.
The authentication system of claim 9. The server device
an identification unit that identifies a user of the used battery based on the identification information of the authentication medium received from the battery exchange device;
The authentication system of claim 10. a usage fee calculation unit that calculates a usage fee for the used battery used by the user identified by the identification unit based on the information on the usage amount,
The authentication system of claim 11. An authentication method for authenticating a user using a target device that is capable of executing a predetermined operation when authentication of the user using an authentication medium provided to the user for authenticating the user is successful, and a server device that receives, from a terminal device of the user, one piece of identification information of one authentication medium that has been input into the terminal device of the user before the user used it for authentication , and input information that has been input into the terminal device as membership information of the user, comprising:
The server device:
A first storage unit stores in advance a group of member information, which is a plurality of pieces of member information of a plurality of users including the one user;
If the member information of the one user included in the input information received from the terminal device matches one piece of member information included in the member information group stored in the first storage unit, newly registering the one authentication medium of the one user as a valid authentication medium;
transmitting valid identification information, which is the one identification information of the one authentication medium registered as the valid authentication medium, to the target device;
The target device is
storing the valid identification information received from the server device in a second storage unit;
a method for authenticating a user of the target device using an authentication medium registered as the valid authentication medium, and authenticating the user when the identification information acquired from the authentication medium matches the valid identification information stored in the second storage unit;
Authentication method.