Fee charging system, fee charging method, and program

Abstract

Provided is a fee charging system for charging a user of a service provided by a business operator for use fees for the service, said fee charging system comprising: a use amount acquisition unit that acquires the use amount of the service used by the user; a billing condition setting unit that receives an operation by the business operator and that sets a billing condition for the use fees; and a use fee calculation unit that calculates the use fees for the service for which the user is billed on the basis of the billing condition set by the billing condition setting unit and the use amount, wherein the billing condition setting unit determines one or more ranges for the use amount, and, for each of the one or more ranges, sets, as the billing condition, the slope of the ratio at which the use fees are determined for the use amount, and the use fee calculation unit calculates the use fees on the basis of said slope corresponding to a range including the amount of use by the user among the one or more ranges.

Description

Billing system, billing method, and program

[0001] The present invention relates to a billing system, a billing method, and a program.

[0002] In the past, an energy rate display system has been disclosed that displays the electricity rate, including the current cumulative usage, in an easy-to-understand manner for users when multiple levels of electricity rate unit prices for the amount of electricity used are set according to the amount of electricity used (Patent Document 1).It is expected that such improvements in the display interface will promote improvements in energy efficiency.

[0003] JP 2014-071600 A

[0004] In the prior art, since the invention concerns display on the residential side, the display is set according to the billing conditions set by a specific electric power company, but when multiple companies share a common billing system, it is desirable for each company to be able to individually and easily set different billing conditions for each company.

[0005] The present invention has been made in consideration of the above circumstances, and one of its objects is to provide a billing system, a billing method, and a program that enable multiple businesses to easily set different billing conditions in a billing system shared by multiple businesses, which will ultimately contribute to improving energy efficiency.

[0006] The billing system, billing method, and program according to the present invention employ the following configuration.

[0007] (1): A billing system according to one aspect of the present invention is a billing system for billing a user of a service provided by a business operator for a usage fee for the service, and includes: a usage amount acquisition unit that acquires the amount of usage of the service by the user; a charging condition setting unit that accepts operations by the business operator and sets charging conditions for the usage fee; and a usage fee calculation unit that calculates the usage fee for the service to be charged to the user based on the charging conditions set by the charging condition setting unit and the usage amount, wherein the charging condition setting unit determines one or more ranges for the usage amount and sets, for each of the one or more ranges, a slope of the ratio that determines the usage fee relative to the usage amount as the charging condition, and the usage fee calculation unit calculates the usage fee based on the slope corresponding to a range of the one or more ranges that includes the user's usage amount.

[0008] (2): In the aspect of (1) above, the service is a battery sharing service that enables multiple users to share multiple batteries via a battery exchange station, and the usage amount acquisition unit acquires the amount of electricity used by the user within a specified period through use of the battery as the usage amount of the service, and the usage fee calculation unit calculates the usage fee to be charged to the user for using the service within the specified period based on the amount of electricity used acquired by the usage amount acquisition unit.

[0009] (3): In the above-mentioned (1) or (2) aspect, the billing system comprises a first server that realizes the functions necessary for the battery sharing service, and a second server that has at least the charging condition setting unit among the usage amount acquisition unit, the charging condition setting unit, and the usage fee calculation unit, and the first server is prohibited from being accessed by the operator, and the second server is accessible by the operator.

[0010] (4): In any of the above aspects (1) to (3), the operator is a service provider that provides the battery sharing service to the user in partnership with a service vendor of the battery sharing service, and the first server is accessible from the service vendor, while the second server is prohibited from being accessed by the service vendor.

[0011] (5): In any of the above aspects (1) to (4), the second server is provided with either or both of a schedule setting unit that accepts operations from the business operator and sets information regarding the business schedule of the battery exchange station, and a tax rate setting unit that sets the tax rate for the area where the business operator is located or the tax rate for the area where the business operator operates the battery exchange station.

[0012] (6): In any of the above aspects (1) to (5), the charging condition setting unit presents the operator with candidate charging conditions according to the region or country in which the service is offered, and accepts editing operations of variable elements by the operator for a charging condition selected from the candidate charging conditions.

[0013] (7): In any of the above aspects (1) to (6), the charging condition setting unit presents the candidate charging conditions to the user based on a priority order that can be changed by the business operator and that is used when presenting the candidate charging conditions to the business operator.

[0014] (8): A billing method according to one aspect of the present invention is a billing method in which a billing device for billing a user of a service provided by a business operator for the usage fee of the service acquires the amount of usage of the service by the user, accepts operations by the business operator to set charging conditions for the usage fee, and calculates the usage fee of the service to be charged to the user based on the set charging conditions and the usage amount, wherein one or more ranges are defined for the usage amount, and for each of the one or more ranges, a slope of the ratio that determines the usage fee relative to the usage amount is set as the charging condition, and the usage fee is calculated based on the slope corresponding to the range of the one or more ranges that includes the user's usage amount.

[0015] (9): A program according to one aspect of the present invention is a program for causing a billing device for billing a user of a service provided by a business operator for a usage fee of the service to execute a billing method, which acquires the amount of usage of the service by the user, accepts the operation of the business operator to set charging conditions for the usage fee, and calculates the usage fee of the service to be charged to the user based on the set charging conditions and the usage amount, and causes the program to define one or more ranges for the usage amount, and for each of the one or more ranges, set as the charging condition a slope of the ratio that determines the usage fee relative to the usage amount, and calculates the usage fee based on the slope corresponding to the range of the one or more ranges that includes the user's usage amount.

[0016] According to the above (1) to (9), in a billing system shared by a plurality of businesses, it is possible to allow the businesses to easily set different billing conditions.

[0017] 1 is a diagram showing an example of the overall configuration of a battery exchange system 1 of an embodiment. FIG. 2 is a diagram showing an example of the configuration of an electric vehicle 10 of an embodiment. FIG. 3 is a block diagram showing an example of the configuration of a removable battery 100 of an embodiment. FIG. 4 is a diagram showing an example of the configuration of a battery exchange station 200 of an embodiment. FIG. 5 is a diagram showing an example of the configuration of a management server 300 of an embodiment. FIG. 6 is a diagram showing an example of the contents of a user management table 352. FIG. 7 is a diagram showing an example of the contents of a status table 354. FIG. 8 is a diagram showing an example of the configuration of a business operator server 400 of an embodiment. FIG. 9 is a diagram showing first to sixth billing models as an example of a method of setting billing conditions. A flowchart showing an example of the flow of processing executed by the battery exchange station 200 of an embodiment. A flowchart showing an example of the flow of processing executed by the business operator server 400 of an embodiment.

[0018] Hereinafter, with reference to the drawings, embodiments of a fee billing system, fee billing method, and program of the present invention will be described. In the following description, the battery exchange system manages multiple battery exchange stations that accept the return and rental of removable batteries, and manages the service fees of each user for the rental, collection, or replacement service of removable batteries via the battery exchange stations (hereinafter referred to as the "battery exchange service"). Although the following description exemplifies an electric vehicle as an application for a removable battery, the removable battery may also be used for electrical equipment other than electric vehicles. An electric vehicle is equipped with one or more removable batteries rented from a battery exchange station and runs on power supplied by the installed removable batteries. Furthermore, an electric vehicle may be a hybrid electric vehicle or a fuel cell vehicle that runs on a combination of a removable battery and an internal combustion engine such as a diesel engine or a gasoline engine. In addition to electric motorcycles, electric bicycles, electric tricycles, electric four-wheelers, hybrid vehicles, electric scooters, robots, etc., may also be applicable to the battery exchange system. The multiple removable batteries installed in an electric vehicle may be rented to users as a battery unit. In the following description, it is assumed that the operation of the battery exchange station is managed by a service vendor (also referred to as an organizer), and one or more service providers provide a battery exchange service using the battery exchange station to contracted users. The battery exchange service is an example of a "battery sharing service."

[0019] <Overall Configuration of Battery Exchange System 1> Fig. 1 is a diagram showing an example of the overall configuration of a battery exchange system 1 according to an embodiment. The battery exchange system 1 includes, for example, a plurality of removable batteries 100, a plurality of battery exchange stations 200, a management server 300, and a plurality of business operator servers 400. The plurality of battery exchange stations 200, the management server 300, and the plurality of business operator servers 400 are capable of communicating with each other via a network NW. An electric vehicle 10 may be communicatively 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.

[0020] Here, the management server 300 is an example of a "first server." The provider server 400 is an example of a "second server." The management server 300 is controlled so that access from providers is prohibited, while the provider server 400 is controlled so that access from providers is possible. Furthermore, the management server 300 is controlled so that access from service vendors is possible, while the provider server 400 is controlled so that access from service vendors is prohibited. By performing such access control, security can be appropriately ensured between the service vendor and the provider. Note that the access control may be realized by a switch or a router included in the network NW, or may be performed by the management server 300 and the provider server 400.

[0021] The battery exchange station 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 station 200 may also discharge the removable battery 100 for grid connection or the like. The battery exchange system 1 shown in the example of FIG. 1 provides an exchange service for the removable battery 100. Each component will be described below in order.

[0022] [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."

[0023] 2 is a diagram showing an example of the configuration of an electric vehicle 10 according to an 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, an electric vehicle GNSS (Global Navigation Satellite System) receiver 22, and a vehicle-side communication unit 24.

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

[0025] The vehicle control unit 14 acquires measurement results from the vehicle sensors 18, acquires a value representing the state of charge (SOC) of the power storage unit 120 from a BMU (Battery Management Unit) 110 (described later) 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 an operation on 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 connector 12.

[0026] 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 causing the electric motor to operate as a regenerative brake and converting the braking energy of the drive wheels into electrical energy to charge the removable battery 100.

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

[0028] The HMI 20 outputs various information to the user of the electric vehicle 10 and accepts input operations by 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, and the like.

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

[0030] The vehicle-side communication unit 24 communicates with the management server 300 via the network NW. For example, the vehicle-side communication unit 24 transmits 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, the 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 vehicle-side 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 vehicle-side communication unit 24 may also transmit the charge states of the two removable batteries 100 mounted on the electric vehicle 10 to the management server 300. The vehicle-side communication unit 24 may also communicate with the battery exchange station 200 via the network NW.

[0031] 3 is a block diagram showing an example of the configuration of the detachable battery 100 according to an 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.

[0032] The BMU 110 controls 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, which are identified based on the measurement results of the measurement sensor 130, in the memory unit 140 as battery state information.

[0033] The power storage unit 120 is, for example, a battery pack in which a plurality of cells are connected in series. The cells constituting the power storage unit 120 are, for example, lithium-ion secondary batteries (LIBs), nickel-metal hydride batteries, all-solid-state batteries, etc.

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

[0035] The storage unit 140 includes 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.

[0036] 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 a plurality of slots 210 present in the battery exchange station 200, the connection unit 150 is electrically connected to the battery exchange station 200 and receives a supply of power from the battery exchange station 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., corresponding to the battery connection unit 12 and the battery connection unit 220 (described below).

[0037] 4 is a diagram showing an example of the configuration of the battery exchange station 200 according to the embodiment. The battery exchange station 200 includes, for example, a plurality of slots 210, a plurality of battery connectors 220, a charger 230, a display unit 235, a reader 240, an authentication unit 245, a communication unit 250, and a control unit 260.

[0038] The slots 210 are mechanisms for receiving and charging the removable batteries 100. In the battery exchange station 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 batteries 100 is provided on the turntable. For example, the battery storage sections are provided in each of the four equal sections of the turntable when viewed from above. Note that the configuration of the battery exchange station 200 for receiving (returning) and lending the removable batteries 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.

[0039] Before a user returns or lends a removable battery 100, the battery exchange station 200 authenticates the user using the authentication unit 245 (described later). 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. The battery exchange station 200 also has an outlet on the front side. The outlet may be automatically opened when the authentication unit 245 authorizes the user. The battery storage compartment located at the outlet can be swapped by rotating a turntable. For example, if the authentication unit 245 authorizes the user to use the battery exchange station 200, the battery exchange station 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 station 200 also rotates the turntable to position the battery storage unit that stores the charged removable battery 100 at the front removal opening. This allows the user to remove the charged removable 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.

[0040] A battery connection section 220 is provided for each slot on the bottom surface of the battery housing section of each of the multiple slots 210. The battery connection section 220 is electrically connected to the connection section 150 of the removable battery 100 when the removable battery 100 is housed in the battery housing section. The battery connection section 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 performing data communication (e.g., serial communication) between the removable battery 100 and the control section 260.

[0041] The charger 230 is connected to the power storage unit 120 of the removable battery 100 via the plurality of battery connectors 220. A charger 230 may be provided for each of the plurality of battery connectors 220, or may be provided as a common configuration for the plurality of battery connectors 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.

[0042] 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 a user uses the battery exchange station 200 and receives input of predetermined information (for example, authentication information) from the user.

[0043] The reading unit 240 reads authentication information and other information from a user card, which is an example of a medium held by the user. The authentication information includes, for example, a user ID and a password. The user card is, for example, a contactless IC card. Alternatively, the user card may be a contact IC card. Furthermore, the user card may be, for example, a card issued for each electric vehicle 10 used by the user. In this case, the authentication information includes a card ID and a vehicle ID as identification information for identifying the user card. Furthermore, the medium held by the user may be an electronic device such as a smartphone or a tablet terminal. Furthermore, the manner in which the reading unit 240 acquires the authentication information is not limited to acquisition via communication, and may also be acquisition by optically reading information from a code image such as a QR code (registered trademark). The reading unit 240 outputs the read authentication information to the control unit 260.

[0044] The authentication unit 245 determines whether to permit a user to use the battery exchange station 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 station 200. For example, the authentication unit 245 uses the authentication information to check against an authentication list 282 stored in the storage unit 280. If the authentication list 282 contains information that matches the authentication information, the authentication unit 245 determines that the user has been successfully authenticated. The authentication list 282 is authentication information for verification distributed by the management server 300 at a predetermined timing or interval. The authentication information for verification includes authentication information for one or more users. The authentication information for verification includes, for example, the user ID, card ID, password, expiration date, number of removable batteries 100 that can be rented, status, and other information permitted for use of the battery exchange station 200. The expiration date is, for example, the last day of the period during which the battery exchange station 200 can be used. The number of removable batteries 100 that can be rented out is, for example, the number of removable batteries 100 that can be installed in the electric vehicle 10 associated with the card ID. The status is information that indicates 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, a state in which a removable battery 100 is being rented out, a state in which authentication for battery exchange is in progress, or a state in which usage has been temporarily or permanently suspended due to fraudulent use by a user, etc.

[0045] If it is determined that the user authentication has been successful, the authentication unit 245 determines whether the user satisfies predetermined usage conditions. The predetermined usage conditions may include, for example, that the current date (date of use) is not past the expiration date included in the authentication list 282. The predetermined usage conditions may also include that the user has not engaged in unauthorized use or the like, rendering the battery exchange station 200 unusable (suspended). For example, if the current date is not past the expiration date included in the authentication list 282, the authentication unit 245 permits the user to use (return and lend) the battery exchange station 200.

[0046] Furthermore, if the authentication list 282 does not contain 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 inquire about authentication. In this case, the authentication unit 245 obtains the authentication result and verification authentication information from the management server 300 as the inquiry result, and if the user authentication is successful, uses the verification authentication information to determine whether or not the user satisfies predetermined usage conditions. Furthermore, if the predetermined usage conditions are satisfied, the user is permitted to use the battery exchange station 200.

[0047] Furthermore, if the authentication of the user is not successful or if the predetermined conditions for use are not met, the authentication unit 245 notifies the user by displaying information indicating that the device cannot be used on the display unit 235. Note that the authentication using the user ID or the like described above does not necessarily need to be performed every time a device is exchanged. Furthermore, instead of (or in addition to) the above-described 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, biometric information for comparison is stored in the authentication list 282, and the authentication unit 245 performs authentication by comparing the biometric information with the biometric information for comparison.

[0048] The communication unit 250 includes 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 management server 300, terminal devices, etc. via the network NW.

[0049] The control unit 260 includes, for example, an exchange control unit 262, a charging control unit 264, a battery information upload unit 268, a usage information upload unit 270, and a storage unit 280. The exchange control unit 262, the charging control unit 264, the battery information upload unit 268, and the usage information upload unit 270 are realized by, for example, a hardware processor such as a CPU (Central Processing Unit) executing a program (software). Furthermore, some or all of the functions may be realized by hardware such as an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a 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 exchange station 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 exchange station 200 by inserting the storage medium (non-transitory storage medium) into a drive device, card slot, etc.

[0050] The storage unit 280 may be realized by the various storage devices described above, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a ROM (Read Only Memory), or a RAM (Random Access Memory). The storage 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 in the battery exchange station 200, and SOC information (an example of the battery status) for each removable battery 100.

[0051] The replacement control unit 262 controls the return of a used removable battery 100 mounted on the electric vehicle 10 and the lending of a charged removable battery 100 based on the authentication result by the authentication unit 245. For example, the replacement control unit 262 opens the slot 210 for storing a used removable battery 100 when returning the battery, or opens the slot 210 storing a charged removable battery 100 when lending the battery. The replacement control unit 262 may also determine whether the stored used removable 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 station 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 station 200 as an inquiry result. If the battery 100 is a genuine removable battery based on the received inquiry result, the exchange control unit 262 controls the rental described above. If the battery 100 is not a genuine removable battery, the exchange control unit 262 does not control the rental, but instead notifies the battery owner of error information or controls the return of the stored used removable battery.

[0052] The charging control unit 264 controls the charger 230 so that the power storage unit 120 is charged to a predetermined state of charge (e.g., SOC) based on the state of charge of the power storage unit 120 and other information acquired via a signal line from the removable battery 100. The SOC of the power 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 storage unit 280 as battery information 284.

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

[0054] The usage information uploading unit 270 transmits the usage status of each user's battery exchange station 200 and its own station ID as usage information to the management server 300 at any timing. Here, "any timing" refers to, for example, the timing when authentication by the authentication unit 245 is permitted and a removable battery is exchanged (e.g., returned or rented). 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, and the date and time of exchange (date and time of use). The information uploaded at any timing by the battery information uploading unit 268 or the usage information uploading unit 270 may be temporarily stored in the storage unit 280.

[0055] [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, and a storage unit 350. The management unit 320 is implemented, for example, by a hardware processor such as a CPU executing a program (software). Some or all of its 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.

[0056] The storage unit 350 may be realized by the various storage devices described above, or an EEPROM, a ROM, a RAM, etc. The storage unit 350 stores, for example, a user management table 352, a status table 354, map information 356, programs, and various other information.

[0057] 6 is a diagram showing an example of the contents of the user management table 352. The user management table 352 contains information in which a user ID and a card ID are associated with a password, expiration date, number of mountable batteries, usable battery type, status, loaned battery ID, usage history, detailed information, etc. For example, the user ID (or card ID) and password are examples of information required for user authentication.

[0058] The expiration date is set, for example, at the time of registration for use of the battery exchange system 1 or at the time of payment of 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 date set in association with the expiration date (vehicle inspection date) determined by the vehicle inspection (vehicle renewal inspection established 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.

[0059] The loaned battery ID is identification information of the removable battery 100 currently loaned to the electric vehicle 10 associated with the card ID. The usage history is information related to the past usage history of the battery exchange system 1 associated with the user ID and the card ID. The usage history includes, for example, the station ID of the battery exchange station 200 used and information such as the date and time of use. 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 of the electric vehicle 10 associated with the card ID. The performance information of the electric vehicle 10 may, for example, be the mileage when one charged removable battery 100 is installed.

[0060] FIG. 7 is a diagram showing an example of the contents of the status table 354. The status table 354 stores information about the status of multiple battery exchange stations 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. For example, the status table 354 contains information that associates, for a station ID, the number of charged batteries in the battery exchange station 200 associated with the station ID, the location of the battery exchange station 200, and the business ID of the business that provides battery exchange services using the battery exchange station 200 identified by the station ID. 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 about 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 about the removable batteries 100. Performance information about the removable batteries 100 includes, for example, the amount of power consumed when fully charged, the number of times the battery has been charged, and the degree of deterioration.

[0061] The map information 356 may include, for example, information about the location of the battery exchange station 200 in map coordinates, as well as facility information (POI: Points of Interest) about convenience stores, restaurants, accommodations, various activity facilities, and the like. The map coordinates are, for example, a three-dimensional or two-dimensional coordinate system measured by a GNSS receiver. The map information 356 may also include the location of roads in the map coordinates and other road information. The road information may include, 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. The map information 356 may be updated as needed by communicating with other devices via the communication unit 310.

[0062] The communication unit 310 includes 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 station 200, the operator server 400, the electric vehicle 10, etc. via the network NW.

[0063] The management unit 320 manages the usage status (including authentication, etc.) of users when replacing the removable battery 100 shown in Fig. 6. For example, the management unit 320 manages the content of verification authentication information required for authentication at each battery exchange station 200, and manages the timing of distribution of the verification authentication information. Furthermore, when an authentication inquiry is made from a battery exchange station 200, the management unit 320 may perform authentication using the authentication information acquired together with the inquiry and the user management table 352, and may transmit the authentication result and verification authentication information based on the authentication result to the battery exchange station 200.

[0064] The management unit 320 also accepts requests for new user registrations or changes to registered information, and updates the user management table 352 based on the accepted information. New registrations and changes to registered information are performed, 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 exchange station 200. The management unit 320 may also manage, for example, the billing status and expiration date for each user ID or card ID.

[0065] [Provider Server 400] Figure 8 is a diagram illustrating an example of the configuration of the provider server 400 according to the embodiment. The provider server 400 includes, for example, a communication unit 410, a usage amount acquisition unit 420, a charging condition setting unit 430, a usage fee calculation unit 440, a schedule setting unit 450, a tax rate setting unit 460, a notification unit 470, and a storage unit 490. The usage amount acquisition unit 420, the charging condition setting unit 430, the usage fee calculation unit 440, the schedule setting unit 450, the tax rate setting unit 460, and the notification unit 470 are realized by a hardware processor such as a CPU executing a program (software). Some or all of the functions may be realized by hardware such as an LSI, an ASIC, an FPGA, or a GPU, 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 operator server 400, 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 operator server 400 by inserting the storage medium (non-transitory storage medium) into a drive device, card slot, etc.

[0066] The communication unit 410 includes 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 station 200, the management server 300, the electric vehicle 10, etc. via the network NW.

[0067] The usage amount acquiring unit 420 has a function of acquiring the usage amount of the battery exchange service by a user of the service. For example, the usage amount acquiring unit 420 acquires the amount of power used by the user within a predetermined period of time by using the removable battery 100 as the usage amount of the battery exchange service. For example, the usage amount acquiring unit 420 may inquire of the management server 300 about the usage amount of the target user, or may calculate the usage amount by acquiring necessary information (e.g., user ID, usage history, SOC information, etc.) from the battery exchange station 200 or the management server 300. For example, the usage amount acquiring unit 420 may calculate the difference in the SOC of the removable battery 100 before and after use or the value obtained by integrating the discharge amount of the removable battery 100 over time as the usage amount. These are based on the idea of ​​charging the user for the amount of power used (discharged). However, if the electric vehicle 10 is capable of using regenerative power, the amount of power minus the amount of regenerative power used may be calculated as the usage amount.

[0068] The charging condition setting unit 430 has a function of setting charging conditions for the usage fee of the battery exchange service. For example, the charging condition setting unit 430 accepts a setting operation of the charging conditions by the business operator via an input device (not shown) such as a mouse or keyboard. Furthermore, for example, the charging condition setting unit 430 may accept a request to set charging conditions from a terminal device (not shown) operated by the business operator. More specifically, the charging condition setting unit 430 determines one or more ranges for the usage amount and sets a curve (hereinafter referred to as a "charging curve") that determines a fee according to the usage amount for each of the one or more ranges. Here, the charging curve is an example of a "ratio that determines a usage fee."

[0069] For simplicity, the following description will be given of a case where a charging curve is defined by a combination of one or more straight lines, but the charging curve is not limited to this. A charging curve may be partially or entirely non-linear, may be discontinuous, or may include non-differentiable points. In this sense, the slope of a charging curve may refer to the slope of the charging curve if the charging curve is linear, or may refer to the slope of the tangent to the charging curve (i.e., the derivative) if the charging curve is curved.

[0070] Figure 9 shows first to sixth billing models as examples of methods for setting billing conditions. The billing models express billing conditions as a function that determines the usage fee for the amount of power used. The first billing model is a model in which the usage fee is a fixed fee regardless of the amount of power used by the user (a completely flat-rate model). In this case, the business operator can set the completely flat-rate model by defining a function (a straight line with a slope of zero) that assigns a fixed fee for any amount of power used.

[0071] The second billing model is a so-called pay-as-you-go model in which the usage fee increases as the amount of electricity used increases. More specifically, FIG. 9 illustrates a pay-as-you-go model (a completely pay-as-you-go model) that applies pay-as-you-go billing across the entire range of electricity used as the second billing model. While FIG. 9 illustrates a function connecting two lines with different slopes as an example of a completely pay-as-you-go model, the completely pay-as-you-go model is not limited to this. The completely pay-as-you-go model may be any function that has a positive slope (i.e., monotonically increasing) for electricity used amounts greater than or equal to zero. It may be represented by a single line or by connecting three or more lines with different slopes. In this case, for example, a business operator can set a completely pay-as-you-go model by setting one or more ranges for electricity used and defining consecutive lines with different slopes between adjacent ranges.

[0072] The third billing model is a basic fee added to the second billing model (full pay-per-use model) (basic + pay-per-use model). In this case, the operator can set the basic + pay-per-use model by setting the same settings as the second billing model (range and slope of the line) and also setting the basic fee.

[0073] The fourth billing model is a fixed fee up to a certain amount of power usage, and a pay-as-you-go fee thereafter (fixed + pay-as-you-go model). In this case, the business operator can set the fixed + pay-as-you-go model by setting the amount of the fixed fee and the range of power usage to which the fixed fee applies, in addition to the same settings as the second billing model (the range and slope of the line).

[0074] The fifth billing model is one in which charges are made under the second billing model (fully pay-as-you-go model) up to a certain amount of power usage, and a fixed fee is charged thereafter (basic + pay-as-you-go model (with cap)). In this case, the business operator can set the basic + pay-as-you-go model (with cap) by setting the amount of power usage at which the fixed fee begins to apply, in addition to the same settings as the third billing model (the range and slope of the line and the amount of the basic fee).

[0075] The sixth billing model is a first fixed fee until the first amount of energy usage is reached, followed by pay-as-you-go until the second amount of energy usage is reached, after which the second fixed fee is charged again (fixed + pay-as-you-go model (with cap)). In this case, the fixed + pay-as-you-go model (with cap) can be set by setting the first and second amounts of energy usage and the amounts of the first and second fixed fees. Note that within the range from the first amount of energy usage to the second amount of energy usage, a function may be defined that connects multiple straight lines with different positive slopes.

[0076] In the battery exchange system 1 of this embodiment, each business can freely set any billing model by performing the above-mentioned operations on the respective business server 400. Note that the billing condition setting unit 430 may be configured to allow the business to select one of a plurality of setting patterns (e.g., the first to sixth billing models illustrated in FIG. 9 ) registered in advance, and to accept editing operations for the selected setting pattern, such as the amount of the fixed fee and the range to which pay-per-use billing is applied.

[0077] In this case, the charging condition setting unit 430 may be configured to present to the operator candidate charging conditions (e.g., first to sixth charging conditions) according to the region or country where the battery exchange service is provided, and to accept an edit operation of variable elements by the operator for a charging condition selected from the candidate charging conditions. For example, the charging condition setting unit 430 may present to the operator a completely flat-rate model as the default charging condition and accept an edit operation of a fixed fee as a variable element. The charging condition setting unit 430 may also be configured to present candidate charging conditions to the user based on a priority order that can be changed by the operator when presenting candidate charging conditions to the operator. For example, in the example of FIG. 9 , the charging condition setting unit 430 may present the first to sixth charging conditions in the order of priority. In this case, the charging condition setting unit 430 may also be configured to accept an operation by the operator to change the priority order of the charging conditions.

[0078] Returning to Fig. 8, the usage fee calculation unit 440 calculates the usage fee for the battery exchange service to be charged to the user based on the usage amount and the charging conditions set by the charging condition setting unit 430. More specifically, the usage fee calculation unit 440 calculates the usage fee based on the slope of a straight line corresponding to a range that includes the usage amount of the user being calculated, out of one or more ranges set for the amount of power usage, in various charging models such as those shown in Fig. 9.

[0079] The schedule setting unit 450 accepts a setting operation for information relating to the business schedule of the battery exchange station 200, regarding the provision of the battery exchange service by the business operator. The schedule setting unit 450 registers the information relating to the business schedule accepted by the setting operation in the schedule information 494.

[0080] The tax rate setting unit 460 receives a setting operation for information regarding the tax rate (regional tax rate) of the region in which the business is located with regard to the provision of the battery exchange service by the business. The tax rate setting unit 460 registers the information regarding the regional tax rate received by the setting operation in the tax rate information 496.

[0081] The notification unit 470 notifies the target user of the usage fee calculated by the usage fee calculation unit 440 .

[0082] The storage unit 490 includes a non-volatile storage device such as a flash memory. The storage unit 490 stores billing conditions 492, schedule information 494, and tax rate information 496. The storage unit 490 may also store identification information (e.g., a battery ID and a station ID) of the removable battery 100 and the battery exchange station 200 related to the battery exchange service provided by the business operator.

[0083] [Processing Flow] The flow of processing executed by the battery exchange system 1 of this embodiment will be described below. The processing executed by the battery exchange system is broadly divided into processing on the battery exchange station 200 and management server 300 side, and processing on the provider server 400 side. The management server 300 executes authentication processing in conjunction with processing by the battery exchange station 200 (described later), and updates the user management table 352 and the status table 354 depending on the status of the battery exchange service, but details will not be given here. The processing by the battery exchange station 200 and the processing by the provider server 400 will be described in detail below.

[0084] [Processing of Battery Exchange Station 200] FIG. 10 is a flowchart illustrating an example of the flow of processing executed by the battery exchange station 200 according to the embodiment. In the example of FIG. 10 , the authentication unit 245 receives authentication information input from a user (step S200). Next, the authentication unit 245 compares the received authentication information with the authentication list 282 stored in the storage unit 280 (step S202) and determines whether matching authentication information is included in the authentication list 282 (step S204). If it is determined that matching authentication information does not exist, the authentication unit 245 communicates with the management server 300 via the communication unit 250 and transmits the received authentication information to the management server 300 to inquire about the authentication result (step S206). Next, the authentication unit 245 determines whether an authentication result corresponding to the inquiry has been obtained (step S208). The authentication result corresponding to the inquiry may include information indicating whether authentication was successful and, if successful, authentication information for comparison.

[0085] If it is determined in step S204 that matching authentication information exists, or if it is determined in step S208 that authentication information corresponding to the inquiry has been acquired, the authentication unit 245 determines whether the usage conditions are met (step S210). The usage conditions here include, for example, that the expiration date for use of the battery exchange system 1 has not passed, and that use of the battery exchange system 1 has not been suspended due to unauthorized use.

[0086] If it is determined that the usage conditions are met, the authentication unit 245 determines that the user authentication has been successful and permits the user to use the battery (step S212). If the user's use is permitted in step S212, the replacement control unit 262 opens the empty slot 210 and stores the used removable battery 100 to be replaced. Next, the replacement control unit 262 determines whether the removable battery 100 stored in the opened slot is a genuine battery (step S214). If it is determined that a genuine battery has been stored, the replacement control unit 262 opens the slot containing the charged removable battery 100 and lends it out (step S216). Next, the usage information upload unit 270 uploads the usage information to the management server 300 (step S218). Furthermore, if it is determined in step S214 that a genuine battery has not been stored, the replacement control unit 262 performs error processing (step S220). In the process of step S220, the replacement control unit 262 displays information on the display unit 235 indicating that a charged removable battery 100 cannot be lent out because a genuine battery is not stored. Alternatively, the slot may be opened so that a used removable battery 100 stored in the empty slot can be removed.

[0087] If it is determined in step S208 that authentication information corresponding to the inquiry has not been acquired, or if it is determined in step S210 that the conditions for use are not met, the user is notified that they cannot use the battery exchange station 200 due to the user authentication result (step S222).This ends the processing of this flowchart.

[0088] [Processing of the Business Operator Server 400] Figure 11 is a flowchart showing an example of the flow of processing executed by the business operator server 400 according to the embodiment. Here, it is assumed that the flowchart in Figure 11 is executed repeatedly at a predetermined interval. First, the charging condition setting unit 430 accepts a setting operation by the business operator regarding the charging conditions for charging a user for the battery exchange service provided by the business operator (step S400). The charging condition setting unit 430 registers the contents of the charging conditions accepted by the setting operation in the charging conditions 492.

[0089] Next, the schedule setting unit 450 accepts a setting operation for information relating to the business schedule of the battery exchange station 200 in relation to the provision of the battery exchange service by its own business (step S402). The schedule setting unit 450 registers the information relating to the business schedule accepted by the setting operation in the schedule information 494.

[0090] Next, the tax rate setting unit 460 accepts a setting operation for information regarding the tax rate (regional tax rate) in the region where the company is located with regard to the provision of the battery exchange service by the company (step S404). The tax rate setting unit 460 registers the information regarding the regional tax rate accepted by the setting operation in the tax rate information 496.

[0091] Next, the usage fee calculation unit 440 determines whether the timing for executing processing to charge the user for the provision of the battery exchange service (hereinafter referred to as the "charging timing") has arrived (step S406). The charging timing may be any timing for calculating the service usage fee for the user of the battery exchange service. For example, if the usage fee for the battery exchange service is collected monthly, the charging timing may be the timing of monthly processing for invoicing the user for the usage fee. Furthermore, for example, if the user is notified of the current usage fee when using the service, the charging timing may be the timing when the user uses the battery exchange service. The charging timing may be set at any timing by the business operator, and is assumed to be set in advance in the business operator server 400.

[0092] If usage fee calculation unit 440 determines that the billing time has not arrived, it terminates the series of processes without calculating the usage fee. On the other hand, if usage fee calculation unit 440 determines that the billing time has arrived, it calculates the amount to be charged to the user as the usage fee for the battery exchange service based on the billing conditions preset by its own company (step S408).

[0093] Next, the notification unit 470 notifies the target user of the invoice for the usage fee calculated by the usage fee calculation unit 440 (step S410). For example, the invoice for the usage fee may be notified to the user's terminal device by SMS (Short Message Service) or push notification, or, if the battery exchange service provides a dedicated portal site for users, the invoice may be notified within the dedicated portal site. In addition to these, the invoice for the usage fee may be notified by any other means, and one invoice may be notified by one or more means.

[0094] Next, the notification unit 470 determines whether the user who received the notification has paid the usage fee within a predetermined period after the notification (step S412). This determination may be made for the users who received the notification of the usage fee invoice in step S410, or may be made to confirm whether or not users who received notification of the usage fee invoice in the past but whose payment of the usage fee has not yet been confirmed have paid.

[0095] If there is any user who has not paid the usage fee within a predetermined period of time from the notification among the users who have received the usage fee bill, the notification unit 470 returns the process to step S410. On the other hand, if there is no user who has not paid the usage fee within a predetermined period of time from the notification among the users who have received the usage fee bill, the notification unit 470 ends the series of processes.

[0096] Here, we have described a processing flow in which the first process (steps S400 to S404) accepts various setting operations by the operator, the second process (steps S406 to S410) calculates and notifies the usage fee when the billing timing arrives, and the third process (step S412) confirms whether the usage fee has been paid, are executed in that order. However, the first process, second process, and third process may each be executed as separate processing flows at their own timings.

[0097] According to the battery exchange system 1 of the embodiment configured as described above, in the battery exchange system 1 shared by multiple businesses, the multiple businesses can easily set different billing conditions. More specifically, the business server 400 includes a usage amount acquisition unit 420 that acquires the amount of battery exchange service used by the user, a billing condition setting unit 430 that accepts the operation of the business and sets the billing conditions for the usage fee, and a usage fee calculation unit 440 that calculates the usage fee for the battery exchange service to be charged to the user based on the billing conditions set by the billing condition setting unit 430 and the usage amount. The billing condition setting unit 430 determines one or more ranges for the usage amount and sets, as the billing condition, the slope of a curve that determines the usage fee for the usage amount for each of the one or more ranges. The usage fee calculation unit 440 calculates the usage fee based on the slope corresponding to the range that includes the user's usage amount among the one or more ranges. This allows each business to easily set multiple fee plans and flexibly and easily change the billing conditions for each fee plan.

[0098] Furthermore, according to the battery exchange system 1 of the embodiment, the business operator server 400 can use the schedule setting unit 450 to accept operations from the business operator and set information related to the business schedule of the battery exchange station 200, which enables the business operator to easily adjust the start date of the rate plan in addition to setting a rate plan. Furthermore, according to the battery system 1 of the embodiment, the business operator server 400 can use the tax rate setting unit 460 to set a tax rate according to the region in which the business operator is located and the region in which the battery exchange service is provided. This allows the business operator to appropriately manage tax rates and the like applied to the usage fees for the battery exchange service, and to more flexibly and easily develop services.

[0099] [Modification] In the above-described embodiment, the battery exchange station 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 station 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 station 200 may lend out a charged removable 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.

[0100] When the removable battery 100 is lent using the method described above, the replacement control unit 262 stores the authentication information from the user in the storage unit 280, and after communication is restored, queries the management server 300 about the authentication information in the storage 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 may set the status in the user management table 352 to "suspended use" and prohibit future use of the removable battery.

[0101] In the above embodiment, the battery exchange system 1 is described in which the provider server 400 sets the billing conditions, business schedule, and regional tax rates for the battery exchange service, and the management server 300 controls the core components necessary for operating the battery exchange station 200 as a BaaS (Battery as a Service) system (e.g., setting thresholds for the basic functions of the battery exchange station 200 and controlling the use of functions by multiple providers). However, some or all of the functions of the provider server 400 may be realized by the management server 300. In the above embodiment, the battery exchange system 1 is described in which a provider server 400 is provided for each provider. However, the provider server 400 may manage multiple providers, or may provide the provider servers 400 of the multiple providers as virtual servers. Furthermore, by configuring the management server 300 as a virtual server, the management server 300 and the multiple provider servers 400 may be physically configured on the same server. In this case, access control to the management server 300 and the provider server 400 and access control between the multiple provider servers 400 may be realized by a virtual switch connecting the virtual servers to a network.

[0102] The above-described embodiment can be expressed as follows: A billing system for billing a user of a service provided by a business operator for a usage fee for the service, comprising: a storage medium for storing computer-readable instructions; and one or more processors connected to the storage medium, wherein the one or more processors execute the computer-readable instructions to: obtain the amount of usage of the service by the user; set charging conditions for the usage fee in response to an operation by the business operator; calculate the usage fee for the service to be charged to the user based on the set charging conditions and the usage amount; define one or more ranges for the usage amount, and set, as the charging condition, the slope of a curve that determines the usage fee versus the usage amount; and calculate the usage fee based on the slope corresponding to a range of the one or more ranges that includes the user's usage amount.

[0103] The above describes the form for carrying out the present invention using an embodiment, but the present invention is not limited to such an embodiment, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention.

[0104] 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 Satellite System) receiver, 24... Vehicle-side communication unit, 100... Detachable battery, 120... Power storage unit, 130... Measurement sensor, 140... Memory unit, 150... Connection unit, 200... Battery exchange station, 210... Slot, 220... Battery connection unit, 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, 268... Battery information upload unit, 270... Usage information upload unit, 280... Memory unit , 282...Authentication list, 284...Battery information, 300...Management server, 310...Communication unit, 320...Management unit, 350...Storage unit, 352...User management table, 354...Status table, 356...Map information, 400...Business operator server, 410...Communication unit, 420...Usage amount acquisition unit, 430...Charging condition setting unit, 440...Usage fee calculation unit, 450...Schedule setting unit, 460...Tax rate setting unit, 470...Notification unit, 490...Storage unit, 492...Charging conditions, 494...Schedule information, 496...Tax rate information

Claims

1. A charge billing system for billing users of a service provided by a business operator for the usage fee of the service, comprising: a usage amount acquisition unit that acquires the usage amount of the service by the user; a charging condition setting unit that accepts an operation of the business operator and sets charging conditions for the usage fee; a usage fee calculation unit that calculates the usage fee of the service to be charged to the user based on the charging conditions set by the charging condition setting unit and the usage amount; and the charging condition setting unit defines a range of 1 or more for the usage amount, and for each of the ranges of 1 or more, sets the slope of the ratio for determining the usage fee with respect to the usage amount as the charging condition; the usage fee calculation unit calculates a single usage fee of the service to be charged to the single user by using the slope of the ratio corresponding to the range including a single usage amount of a single user among the ranges of 1 or more for the usage amount; A charge billing system.

2. The service is a battery sharing service that enables a plurality of batteries to be shared among a plurality of users via a battery exchange station, the usage amount acquisition unit acquires, as the usage amount of the service, the amount of power used by the user within a predetermined period by using the battery; the usage fee calculation unit calculates the single usage fee to be charged to the single user for the usage of the service within the predetermined period based on the amount of power used acquired by the usage amount acquisition unit; The charge billing system according to claim 1.

3. The charge billing system includes a first server that realizes functions necessary for the battery sharing service, and a second server that includes at least the charging condition setting unit among the usage amount acquisition unit, the charging condition setting unit, and the usage fee calculation unit; and access from the business operator to the first server is prohibited, and access from the business operator to the second server is possible. The charge billing system according to claim 2.

4. The charge billing system includes a first server that realizes functions necessary for the battery sharing service, and a second server that includes at least the charging condition setting unit among the usage amount acquisition unit, the charging condition setting unit, and the usage fee calculation unit; and The operator is a service provider that partners with a service vendor of the battery sharing service to provide the battery sharing service to the user, the first server is accessible by the service vendor, access from the service vendor to the second server is prohibited, The charge billing system according to claim 2 or 3.

5. The charge billing system is a first server that realizes functions necessary for the battery sharing service, and a second server that includes at least the billing condition setting unit among the usage amount acquisition unit, the billing condition setting unit, and the usage charge calculation unit, and includes The second server includes at least one of a schedule setting unit that receives an operation of the operator and sets information regarding the business schedule of the battery exchange station, and a tax rate setting unit that sets a tax rate of the region where the operator is located or a tax rate of the region where the operator operates the battery exchange station. The charge billing system according to claim 2.

6. The billing condition setting unit presents candidates for the billing conditions according to the region or country where the service is operated to the operator, and receives an editing operation of variable elements by the operator for the billing conditions selected from among the candidates. The charge billing system according to claim 1.

7. The billing condition setting unit presents the candidates for the billing conditions to the user based on a priority order that can be changed by the operator and is based on the priority order when presenting the candidates for the billing conditions to the operator. The charge billing system according to claim 6.

8. A charge billing device for billing a user of a service provided by an operator for the usage fee of the service acquires the usage amount of the service by the user, receives an operation of the operator and sets the billing conditions for the usage fee, calculates the usage fee of the service to be charged to the user based on the set billing conditions and the usage amount, A charge billing method, defines one or more ranges for the usage amount, and for each of the one or more ranges, sets the slope of the ratio for determining the usage fee with respect to the usage amount as the billing condition. Calculating a usage fee for a service to be charged to the user by using the slope of the ratio corresponding to a range including one usage amount of one user among one or more ranges of the usage amount. A billing method.

9. In a billing device for billing a user of a service provided by a business operator for a usage fee of the service, acquiring the usage amount of the service by the user, receiving an operation of the business operator to set a charging condition for the usage fee, calculating a usage fee for the service to be charged to the user based on the set charging condition and the usage amount, A program for causing a billing method to be executed, causing one or more ranges to be defined for the usage amount, and for each of the one or more ranges, setting the slope of a ratio for determining the usage fee with respect to the usage amount as the charging condition, causing a usage fee for the service to be charged to the one user to be calculated by using the slope of the ratio corresponding to a range including one usage amount of one user among one or more ranges of the usage amount, A program for this purpose.