Management server, its control method, and battery charging system
A management server system allows batteries to be used across multiple charging stations, addressing the limitation of station-specific charging by managing and allocating charging rights, thereby improving user convenience.
Patent Information
- Application Number
- JP2024507318
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-03-16
- Publication Date
- 2026-01-14
- Estimated Expiration
- 2042-03-16
AI Technical Summary
Existing battery charging systems do not allow batteries to be used interchangeably across stations operated by different companies, limiting charging options for vehicle drivers.
A management server manages batteries distributed by a supplier, enabling charging rights to be sold in predetermined units and allocated to multiple stations, allowing users to charge batteries at any station equipped with the system.
Enables batteries managed collectively by a supplier to be charged at stations operated by various businesses, enhancing user convenience by allowing seamless charging at any station with available rights.
Smart Images

Figure 0007799032000001 
Figure 0007799032000002 
Figure 0007799032000003
Abstract
Description
[Technical Field]
[0001] The present invention relates to a management server, a control method thereof, and a battery charging system. [Background technology]
[0002] From the perspective of environmental issues, there is an urgent need to develop a battery charging system that supplies power to vehicles. For vehicle drivers, it would be more convenient if they could charge their vehicles at a battery station (hereinafter simply referred to as a station) that is closer to their current location, regardless of the company that operates the station.
[0003] Patent Document 1 proposes an energy supply system that distributes batteries installed in electric vehicles and provides convenience comparable to that of conventional gasoline-powered vehicles. Patent Document 2 proposes a battery management system that allows users to easily grasp the operating status of stations in their desired area, regardless of their current location. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2001-57711 [Patent Document 2] International Publication No. 2020 / 179262 Summary of the Invention [Problem to be solved by the invention]
[0005] The above-mentioned conventional technology realizes a more efficient charging system by presenting the battery to be charged at a station and receiving the charged battery in return. However, no consideration has been given to a system that allows batteries to be used interchangeably at stations operated by different operators when there are multiple operators operating stations. Therefore, a battery received at a station operated by Company A cannot be charged at a different station operated by Company B. In this case, the options for drivers requesting charging are limited.
[0006] An object of the present invention is to provide a system that allows batteries managed collectively by a battery supplier to be charged at stations operated by a plurality of different businesses. [Means for solving the problem]
[0007] According to the present invention, there is provided a management server that manages batteries of a first business that has batteries that can be attached to or detached from vehicles, the management server comprising: The first business operator Based on the number of batteries distributed to the market a management means for managing the right to charge in predetermined units; A battery station capable of charging the battery is provided. A second carrier, 2nd business operator Either providing means for selling the right to charge in the predetermined unit in response to a request from the Equipped with The battery station provides a charging service for the battery to the user in accordance with the charging right provided in the predetermined unit.
[0008] Further, according to the present invention, a management server that manages batteries of a first business operator that has a battery that can be attached to a vehicle; Different multiple 2nd business operator Either a battery charging system capable of communicating with an information processing device that manages a plurality of battery stations that charge the batteries, the information processing device being owned by The management server The first business operator Based on the number of batteries distributed to the market a management means for managing the right to charge in predetermined units; The aforementioned Multiple 2nd business operator Either providing means for selling the right to charge in the predetermined unit in response to a request from the Equipped with The information processing device includes: a requesting means for requesting the right to charge from the management server; an allocation means for allocating the charging right provided by the providing means to the plurality of battery stations managed by the information processing device; The present invention is characterized by comprising: [Effects of the Invention]
[0009] According to the present invention, it is possible to provide a system in which a battery managed collectively by a battery supplier can be charged at stations operated by a plurality of different businesses.
[0010] Other features and advantages of the present invention will become apparent from the following description taken in conjunction with the accompanying drawings, in which the same or similar elements are designated by the same reference numerals. [Brief explanation of the drawings]
[0011] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention. [Figure 1] System overview. [Figure 2] FIG. 1 is an explanatory diagram showing an example of service operation. [Figure 3] FIG. 2 is a diagram showing an example of the configuration of each device. [Figure 4] 10 is a flowchart showing an example of processing executed by a station server. [Figure 5] 10 is a flowchart illustrating an example of a process executed by a mobile terminal. [Figure 6A]10 is a flowchart showing an example of processing executed by a management server. [Figure 6B] 10 is a flowchart showing an example of processing executed by a management server. [Figure 7] 10 is a flowchart showing an example of processing executed in a battery station. [Figure 8] 10 is a flowchart showing an example of a process for managing usage status in a management server. [Figure 9] FIG. 10 is a diagram showing a modified example of the system configuration. DETAILED DESCRIPTION OF THE INVENTION
[0012] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the scope of the invention as claimed, and not all combinations of features described in the embodiments are necessarily essential to the invention. Two or more of the features described in the embodiments may be arbitrarily combined. Furthermore, the same reference numerals are used for the same or similar components, and redundant explanations will be omitted.
[0013] <System Overview> FIG. 1 is a schematic diagram of a system according to one embodiment. The system 100 includes vehicles 1a, 1b, and 1c, a management server 2, mobile terminals 3a, 3b, and 3c, a station server 4, battery stations 5a, 5b, and 5c, and a battery 6. Users 101a, 101b, and 101c represent drivers of the vehicles 1a, 1b, and 1c and the mobile terminals 3a, 3b, and 3c, respectively. The management server 2, the mobile terminals 3a, 3b, and 3c, the station server 4, and the battery stations 5a, 5b, and 5c are communicatively connected to each other via a communication network 7. Note that there is no intention to limit the number of vehicles, mobile terminals, battery stations, and station servers. In the following, when the alphabet at the end of a reference number is omitted, the description applies to all of the vehicles. For example, vehicle 1 refers to all of vehicles 1a, 1b, and 1c.
[0014] The vehicle 1 is a straddle-type vehicle that receives power from a battery 6. Here, a motorcycle is used as an example, but this is not intended to limit the present invention. Any vehicle capable of attaching or detaching the battery 6, such as a four-wheeled vehicle, may be used. The battery 6 is a portable battery that can be attached or detached to a vehicle, such as a lithium-ion battery. The battery 6 is provided with a memory that stores identification information indicating the battery type and information such as the number of times the battery can be charged and the charge capacity. The mobile terminal 3 is a portable terminal such as a smartphone owned by a user who wishes to charge the battery 6. Each user can access the charging service provided by this system via their own mobile terminal 3. Note that, while the mobile terminal 3 is used as an example of a user authentication device, the mobile terminal 3 is not essential to the present invention; any device or medium capable of authenticating a user may be used. For example, other portable devices or storage media such as credit cards or cards usable for public transportation may be used. In other words, any device or medium capable of authentication, such as identity verification, is applicable to the present invention.
[0015] The management server 2 is a server that manages batteries 6 that have been distributed on the market by battery suppliers (supply companies) that supply the batteries 6. For example, it manages the number of batteries 6 that can be charged, the amount of charge and discharge, the full charge capacity, and the degree of deterioration for each battery 6. The management server 2 sells the right to charge the batteries 6 that it manages to one or more businesses (battery businesses) that operate battery stations 5. Therefore, the management server 2 also manages the right to charge that is assigned to each battery station 5.
[0016] The station server 4 is a server that manages the battery stations 5 operated by battery operators, and is installed for each operator. The station server 4 manages the battery stations 5 that it operates, purchases charging rights from the management server 2, and assigns the charging rights purchased from the battery supplier to each of the one or more battery stations 5 that it operates.
[0017] The battery station 5 is a charging station for charging batteries 6, and has multiple slots, each of which can accommodate one battery 6 inserted for charging. The battery station 5 may be operated as an unmanned vending machine-type device. When a user 101 wishes to charge a battery 6, the user inserts the battery 6 to be charged into a slot in the battery station 5. The battery station 5 authenticates the inserted battery 6, and if the inserted battery 6 is chargeable, provides the user 101 with another charged battery instead. Therefore, when charging the battery 6, the user 101 does not need to wait until charging is completed at the battery station 5, and can receive the other battery 6 that has been efficiently charged.
[0018] <Service Overview> (Ticket sales) Figure 2 shows an overview of the services provided by this system. First, charging rights are assigned to each battery station 5. The station server 4 manages the charging rights assigned to the battery stations 5a, 5b, and 5c that it operates, and when those rights run short, it requests the management server 2 to purchase more charging rights. Charging rights are sold, for example, as tickets in predetermined units. These tickets are virtual electronic tickets that are bought and sold on the network. The predetermined units are the amount of charge or the number of times the charge is made. This makes it easy to obtain the total amount of charge or the total number of times the charge is made from the quantity of batteries 6 distributed on the market, and makes it easy to manage the buying and selling of charging rights.
[0019] In response to a ticket purchase request from the station server 4, the management server 2 authenticates the requested information and performs payment. Once payment is complete, the management server 2 provides the requested ticket to the station server 4. The station server 4 assigns the received ticket to each battery station 5a, 5b, and 5c. The assigned ticket is sent to each battery station 5 via the communication network 7. The station server 4 also notifies the management server 2 of information about the assigned ticket. The management server 2 manages this information and also manages the usage status obtained from the battery station 5 at any time, thereby making it possible to grasp the amount of charge and number of charges that can be made at each battery station 5.
[0020] (Charging reservation) Next, a service procedure when a user 101c requests charging of the battery 6 will be described. The user 101c accesses the management server 2 via the user's mobile terminal 3c and initiates a charging reservation. Here, information about the user and information about the battery 6 to be charged are transmitted. The information about the user includes, for example, the user's authentication information and location information. Note that the authentication information can also be registered in a memory chip or the like provided in the battery 6. In that case, it is desirable to transmit the authentication information assigned to the battery 6. The authentication information is information that is registered in advance in this system (management server 2). The information that is registered in advance in the management server 2 includes, in addition to authentication information for each user or battery, information such as credit card information for payment. The location information may be information acquired by a location information acquisition device such as a GPS provided in the mobile terminal 3c, or information obtained from a base station or wireless access point accessed by the mobile terminal 3c. Alternatively, the location information may be input by the user. For example, the user may wish to charge near a destination, in which case the user may select a location.
[0021] When the management server 2 receives a request from the mobile terminal 3c to start a charging reservation, it authenticates the user, and if the authentication is successful, it provides information on at least one battery station 5 that can be charged based on the location information. Here, the management server 2 does not notify the mobile terminal 3c of information on battery stations 5 for which the user does not have enough rights to charge, i.e., for which the user does not have enough tickets corresponding to the charging reservation. Therefore, the mobile terminal 3c only guides the user to battery stations 5 that can be charged. For example, the mobile terminal 3c displays information on one or more battery stations 5 that have been guided to the user, centered around its own position (or a position input by the user), on a map, and presents this information to the user. In other words, the information guided to the user does not include battery stations 5 that cannot be charged, and unnecessary information can be suitably omitted.
[0022] The user selects the desired battery station 5c from the presented battery stations 5. The mobile terminal 3c notifies the management server 2 of the battery station 5c selected by the user and makes a charging reservation. Upon receiving the charging reservation, the management server 2 notifies the corresponding battery station 5c of the reservation information. The battery station 5c reserves the battery 6 with the reserved capacity as reserved.
[0023] (battery replacement) Next, a service procedure for battery replacement at the battery station 5 reserved by the user 101c will be described. The user 101c moves to the battery station 5c for which charging has been reserved and inputs predetermined authentication information into the battery station 5c. Here, the predetermined authentication information is, for example, information such as the user's authentication information or a reservation number. This information may be input by, for example, inserting a credit card registered for payment or a card that may be issued for receiving services of this system, or it may be input manually. Alternatively, the barcode issued at the time of reservation may be displayed on the user's mobile terminal 3c and read by a reader provided in the battery station 5c.
[0024] If authentication is successful, the battery station 5c prompts the user 101c to insert the battery 6 to be charged, which was installed in the vehicle 1c, into a designated empty slot. When the user 101c inserts the battery 6 into the designated empty slot, the battery station 5c reads the identification information of the battery 6 and determines whether charging is possible. The identification information includes information on the type of battery 6, the number of times it can be charged, and the charge capacity. The battery station 5c determines whether the identification information is legitimate. Valid identification information indicates the identification information of a battery (referred to as a swap battery) supplied to the market by a battery supplier. On the other hand, charging of privately owned batteries is restricted even if the battery type is the same. This allows the sale and purchase of charging rights accurately based on the total charge capacity of batteries supplied to the market. In other words, if charging of privately owned batteries were permitted, the total number of batteries circulating in the market would differ from the total number of managed swap batteries, resulting in a discrepancy between the number of tickets set based on the total number of managed swap batteries and the number of chargeable batteries. Therefore, it is desirable to impose such restrictions.
[0025] If the battery station 5c determines that charging is possible, it provides the battery 6 with a different charge capacity requested by the user 101 instead. For example, the battery station 5c unlocks the relevant battery 6 and controls it so that it can be removed from the slot. As described above, according to this embodiment, when a user wants to charge the battery 6, the battery to be charged is simply exchanged for an already charged battery, thereby eliminating the waiting time required for charging the battery 6 at the battery station 5. On the other hand, in this system, it is also possible to request charging at the battery station 5 without reserving battery charging. Even in this case, it is possible to exchange the battery for an already charged battery.
[0026] <Configuration of each device> 3 is a diagram showing the configuration of each device included in this system. The management server 2 includes a communication unit 21, a control unit 22, and a storage unit 23. The communication unit 21 controls communication with each device via the communication network 7. The control unit 22 is a processor such as a CPU, and executes programs stored in the storage unit 23. The storage unit 23 is a storage device such as RAM, ROM, or a hard disk. In addition to the programs executed by the control unit 22, various types of management information are stored in the storage unit 23.
[0027] The control unit 22 executes programs stored in the memory unit 23 to realize the functions of the management unit 24, sales unit 25, and reservation unit 26. The management unit 24 acquires various types of management information from each device and stores it in the memory unit 23. The management information includes information about batteries distributed on the market, information about the right to charge (information about tickets), information about each battery station 5, information about registered users, reservation information, etc. The management unit 24 updates this management information as needed according to information from external devices, etc.
[0028] The sales unit 25 sells tickets, which are the right to charge, to the station server 4 and the battery station 5 in a predetermined unit. The predetermined unit is the charging capacity or the number of times charging can be performed. The tickets are adjusted according to the number of batteries 6 circulating in the market and the number of times they can be charged. The sales unit 25 sells tickets based on requests from the station server 4 and the battery station 5. The sales unit 25 may also monitor the ticket allocation status of each battery station 5, and automatically prompt the purchase of tickets when there is a shortage of tickets.
[0029] Reservation unit 26 controls charging reservations from user 101. As described with reference to FIG. 2, reservation unit 26 guides to battery stations 5 that can be charged in accordance with the request from user 101, notifies the reserved battery station 5 of reservation information, and manages the information.
[0030] The mobile terminal 3 includes a communication unit 31, a control unit 32, an operation unit 33, a display unit 34, and a storage unit 35. The communication unit 31 controls communication with each device via the communication network 7. The control unit 32 is a processor represented by a CPU, and executes programs stored in the storage unit 35. The storage unit 35 is a storage device such as a RAM, a ROM, or a hard disk. In addition to the programs executed by the control unit 32, the storage unit 35 also stores information about the user.
[0031] The operation unit 33 is a user interface that accepts user operations. The operation unit 33 may also be provided as a touch panel liquid crystal display that is integral with the display unit 34. Various information is displayed on the display unit 34, and for example, chargeable battery stations 5 are displayed on a map so that they can be selected according to guidance information received from the management server 2.
[0032] The station server 4 includes a communication unit 41, a control unit 42, an operation unit 43, a display unit 44, and a storage unit 45. The communication unit 41 controls communication with each device via the communication network 7. The control unit 42 is a processor, such as a CPU, and executes programs stored in the storage unit 45. The storage unit 45 is a storage device, such as a RAM, a ROM, or a hard disk. The storage unit 45 stores information about each battery station 5 to be managed, in addition to the programs executed by the control unit 42. The station server 4 may be provided for each business operator that operates a battery station 5, or may be provided integrally with the battery station 5, as shown in a modified example described below. The function of the station server 4 is realized as a ticket purchasing application. Therefore, the station server 4 can be realized as an information processing device, such as a PC or a tablet, that is capable of executing the application.
[0033] The operation unit 43 is a user interface that accepts user operations. The operation unit 43 may also be provided as a touch panel liquid crystal display that is integrated with the display unit 44. Various information is displayed on the display unit 44, for example, a screen for a ticket purchase application is displayed.
[0034] The battery station 5 includes a communication unit 51, a control unit 52, an operation unit 53, a display unit 54, a memory unit 55, a charging unit 56, a human presence sensor 57, and a charging slot 58. The communication unit 51 controls communication with each device via the communication network 7. The control unit 52 is a processor represented by a CPU, and executes programs stored in the memory unit 55. The memory unit 55 is a storage device such as RAM, ROM, or a hard disk. In addition to the programs executed by the control unit 52, the memory unit 55 stores information about assigned tickets, the battery charging status, notified reservation information, and the like.
[0035] The operation unit 53 is a user interface that accepts user operations. The operation unit 53 may also be provided as a touch panel liquid crystal display that is integrated with the display unit 54. Various information is displayed on the display unit 54, such as a message to the user when replacing the battery.
[0036] The charging unit 56 controls the charging of the battery 6 installed in the charging slot 58. The charging unit 56 charges the battery 6 using a ticket stored in the memory unit 55. The human presence sensor 57 detects people around the battery station 5 using a human detection sensor such as an infrared sensor. The battery station 5 has, for example, a normal state in which power is supplied to all components and a power-saving state in which power is supplied to only some components, as power supply states. In the power-saving state, for example, power is not supplied to the display unit 54 or the operation unit 53. When a predetermined time has passed since the human presence sensor 57 detected a person, the control unit 52 returns the power supply state from the power-saving state to the normal state. On the other hand, when the human presence sensor 57 does not detect a person for a predetermined time, the control unit 52 transitions the power supply state from the normal state to the power-saving state.
[0037] The charging slot 58 allows the battery 6 to be detachably attached, and charging can be performed with the battery 6 attached. When the battery 6 is attached, information about the battery stored in the battery 6 can be read out. Furthermore, the charging slot 58 has a locking mechanism that locks the attached battery 6, preventing it from being freely removed. When the battery to be charged is inserted correctly, the locking mechanism of the replacement battery is released and it is provided to the user.
[0038] <Station server processing example> 4 shows the processing procedure for purchasing a ticket from the station server 4. The processing described below is realized, for example, by the CPU of the station server 4 reading a control program stored in a ROM or the like into a RAM and executing it.
[0039] First, in S101, the control unit 42 displays the remaining chargeable capacity of each battery station 5 under management on the display unit 44. One method of displaying this information may be to display the number of tickets allocated to each battery station 5. Next, in S102, the control unit 42 determines whether or not an instruction to purchase tickets has been received through the screen displayed on the display unit 44. If the instruction has been received, the process proceeds to S103; if not, the process of this flowchart ends.
[0040] In S103, the control unit 42 notifies the management server 2 of a purchase request for the number of tickets according to the received instructions. The request provides information necessary for payment in addition to the number of tickets to be purchased. The information necessary for payment includes at least authentication information for the business that operates the battery station 5. Note that notification of this information may be realized through multiple exchanges between the management server 2 and the station server 4. For example, if the management server 2 can secure the requested number of tickets, it may further acquire information necessary for payment.
[0041] Next, in S104, the control unit 42 determines whether the payment has been completed successfully based on the notification from the management server 2. If it is determined that the payment has been completed successfully, the process proceeds to S105; if not, the process of this flowchart ends. In S105, the control unit 42 allocates the acquired tickets to each battery station 5, transmits the allocated tickets to the target battery station 5, and ends the process of this flowchart.
[0042] <Example of processing on a mobile terminal> 5 shows a processing procedure for reserving charging for the mobile terminal 3. The processing described below is realized, for example, by the CPU of the mobile terminal 3 reading a control program stored in the ROM or the like into the RAM and executing it.
[0043] In S201, the control unit 32 starts a charging reservation with the management server 2, and first obtains location information that serves as a reference for searching for the battery station 5, and notifies the management server 2. The location information may be location information of the mobile terminal 3 obtained by GPS, or location information around a destination input by the user. Furthermore, the control unit 32 notifies the management server 2 of the user's authentication information in addition to the location information.
[0044] Next, in S202, the control unit 32 determines whether a response has been received from the management server 2. If a response has been received, the process proceeds to S203; if not, the process waits until a response is received. If a response has been received, the control unit 32 displays at least one chargeable battery station 5 on a map on the display unit 34 in accordance with the guidance information included in the response in S203. Here, the guidance information does not include battery stations 5 for which the user 101 does not have the right to charge, so the user 101 can select the desired battery station 5 from the presented battery stations 5. Note that if the response information indicates authentication failure, the process from S203 onwards is not performed, and the process of this flowchart ends.
[0045] Next, in S204, the control unit 32 determines whether or not the user 101 has selected any battery station 5 from the at least one chargeable battery station 5 presented in S203. If selected, the process proceeds to S205; if not, the process waits until a selection is made. In S205, the control unit 32 notifies the management server 2 of the selected battery station 5, thereby completing the charging reservation and ending the processing of this flowchart.
[0046] <Example of management server processing> 6 shows the processing steps when (a) providing a ticket and (b) accepting a charging reservation by the management server 2. The processing described below is realized, for example, by the CPU of the management server 2 reading a control program stored in the ROM or the like into the RAM and executing it.
[0047] 6(a) will be explained. First, in S301, the control unit 22 receives a ticket purchase request from the station server 4 via the communication unit 21. Next, in S302, the sales unit 25 determines whether payment is possible based on the ticket purchase amount and payment-related information notified from the station server 4. More specifically, the sales unit 25 determines via the management unit 24 whether the requested number of tickets can be secured, and further determines whether payment is possible by authenticating the purchaser and determining whether payment can be made from a pre-registered account, etc. If payment is possible, the process proceeds to S303; if not, the process of this flowchart ends.
[0048] In S303, the control unit 22 provides the requested number of tickets to the station server 4 via the communication unit 21, and stores ticket buying and selling information in the memory unit 23 via the management unit 24. Thereafter, in S304, the control unit 22 receives ticket allocation information provided from the station server 4 via the communication unit 21, and stores the allocation information in the memory unit 23 via the management unit 24 to update the management information, thereby terminating the processing of this flowchart.
[0049] 6(b) will be explained. First, in S311, the control unit 22 receives location information from the mobile terminal 3 via the communication unit 21 when a charging reservation is initiated. User authentication information is also notified along with the location information, and the control unit 22 determines whether the user is a pre-registered user. If the user is legitimate, in S312 the control unit 22 notifies the mobile terminal 3 via the communication unit 21 of guidance information including information on battery stations 5 that can be charged, in accordance with the location information acquired in S311. Thereafter, in S313, the control unit 22 determines whether or not reservation information has been received from the mobile terminal 3 via the communication unit 21. If reservation information has been received, the process proceeds to S314; if not, the reservation process is stopped when a predetermined time has elapsed after the start of the charging reservation, and the process of this flowchart ends.
[0050] In S314, control unit 22 notifies selected battery station 5 included in the reservation information received from mobile terminal 3 of the reservation information, stores the reservation information in storage unit 23, updates the management information, and ends the processing of this flowchart. Note that the reservation information includes information indicating the selected battery station 5, as well as a reservation number, charging capacity, information about the user, and the like.
[0051] <Example of battery station processing> 7 shows the processing procedure when replacing a battery in the battery station 5. The processing described below is realized, for example, by the CPU of the battery station 5 reading a control program stored in the ROM or the like into the RAM and executing it.
[0052] First, in S401, the control unit 52 receives reservation information via the communication unit 51. Here, the control unit 52 stores the reservation information in the storage unit 55 and reserves a battery 6 with the requested charge capacity included in the reservation information. For example, if there is a battery 6 with the corresponding charge capacity, the control unit 52 reserves the battery to prevent it from being used by another user. Furthermore, if there is no battery 6 with the corresponding charge capacity, the control unit 52 causes the charging unit 56 to charge an arbitrary battery 6 to reserve the battery 6.
[0053] Next, in S402, the control unit 52 determines whether or not a person has been detected around the battery station 5 by the human presence sensor 57. If a person is detected, the power supply state of the battery station 5 is switched from the power saving state to the normal state, and the process proceeds to S403.
[0054] In S404, the control unit 52 performs user authentication and accepts the number of the battery to be purchased. The battery number is, for example, the number of the charging slot 58. For example, the display unit 54 displays the charge amount of the battery 6 installed in each charging slot 58, and the user selects the battery 6 with the desired charge capacity and inputs the number.
[0055] Upon receiving the number of the battery to be purchased, the control unit 52 prompts the user 101 to insert the battery 6 to be charged into an empty slot in S404, and when the battery 6 is inserted into that slot, acquires identification information for the inserted battery 6. Furthermore, the control unit 52 determines whether the battery 6 is rechargeable (i.e., a swap battery distributed on the market rather than an individually owned battery) according to the acquired identification information, and if it is a legitimate battery 6, proceeds to S405, but if it is an unchargeable battery 6, the process is stopped and the process of this flowchart ends. The legitimate identification information may be stored for each battery station 5, or may be queried from the management server 2 each time.
[0056] In S405, the control unit 52 displays the purchase price on the display unit 54 and receives payment of the purchase price. The purchase price may be paid in cash, or may be debited from pre-registered account information or a credit card. Once payment is complete, in S406 the control unit 52 unlocks the battery 6 with the number accepted in S404, provides the charged battery 6 to the user 101, and ends the processing of this flowchart. The control unit 52 charges the battery 6 inserted by the user 101 by consuming the ticket, and notifies the management server 2 of the usage status of the battery 6 as operation information.
[0057] <Usage Management> 8 shows the processing procedure when the management server 2 manages the usage status of the battery station 5. The processing described below is realized, for example, by the CPU of the management server 2 reading a control program stored in the ROM or the like into the RAM and executing it.
[0058] First, in S321, the control unit 22 receives operation information including the usage status from each battery station 5. As described above, the operation information includes the usage status at each battery station 5. The operation information is notified from each battery station 5 as needed, for example, each time a ticket is used. The control unit 22 further stores the received information in the storage unit 23 and updates the management information.
[0059] Next, in S322, when the control unit 22 updates the management information, it determines whether the update has caused a battery station 5 to run out of tickets. The determination of whether there is a ticket shortage may be made by, for example, setting a threshold value for a predetermined charge amount, number of charges, number of tickets, etc., and determining whether the threshold value has been exceeded. If there is a shortage, the process proceeds to S323; if not, the process of this flowchart ends.
[0060] In S323, the control unit 22 notifies the station server 4 that manages the corresponding battery station 5 that there are insufficient tickets for the corresponding battery station 5, and ends the processing of this flowchart. Note that the notification of the insufficient tickets may be sent directly to the corresponding battery station 5, rather than to the station server 4. By notifying the user of a lack of charging rights (tickets), it is possible to prevent the user from missing out on purchasing tickets, and to always provide the user with a wide range of options. Furthermore, rather than notifying the user of a lack of tickets, it is also possible to control the system so that tickets are automatically replenished. In this case, payment is also automatically made according to the registered information.
[0061] <Modification> A modified example of the above embodiment will be described below. Fig. 9 is a diagram showing a modified example of the configuration of each device included in this system. Note that the same reference numerals are used to designate the same components as those in the above embodiment shown in Fig. 3, and their description will be omitted.
[0062] In this modified example, the functions of the station server 4 are integrated into the battery station 5. Therefore, ticket purchases are performed by each battery station 500, and the functions of the station server 4 described above are performed by the control unit 510 of each battery station 500. Note that in this modified example, when the management server 2 determines that there are insufficient tickets, tickets may be automatically sold to the battery station 5. Of course, this modified example can also be applied in combination with the above embodiment. In that case, when it is determined that there are insufficient tickets, each battery station 500 automatically performs the purchase procedure, and further, tickets to be allocated to multiple battery stations 500 can be purchased in bulk via the station server 4.
[0063] <Summary of the embodiment> The above-described embodiments disclose at least the following information processing apparatus and information processing method.
[0064] 1. The management server (2) of the above embodiment is A management server that manages batteries of a first business operator that has a battery that can be attached to a vehicle, a management means (24) for managing the right to charge the batteries owned by the first business operator in predetermined units; a provision means (25) for selling the right to charge in the predetermined unit in response to a request from a second business operator that owns a battery station capable of charging the battery; Equipped with The battery station provides the user with a battery charging service according to the charging right provided in the predetermined unit. According to this embodiment, a battery supplier can collectively manage batteries and provide multiple businesses that operate battery stations with the right to charge the batteries. That is, a system can be provided in which batteries managed collectively by a battery supplier can be charged at stations operated by multiple different businesses. This allows users to charge their batteries at the battery station of their choice, further improving convenience.
[0065] 2. In the above embodiment, Acceptance means (21, 26, S311) for accepting a battery charging reservation from a user; a response means (21, 26, S312) for informing the user of the location of the battery station that has the right to charge in accordance with the accepted charging reservation; Further equipped According to this embodiment, it is possible to accept a charging reservation in advance and guide the user to a battery station that meets the request.
[0066] 3. In the above embodiment, The response means does not provide information about the location of the battery station for which the charging right is not held (S312). According to this embodiment, it is possible to prevent the user from being guided to a battery station where charging is not possible, and it is possible to provide a more convenient system.
[0067] 4. In the above embodiment, The accepting unit further accepts the battery station to be charged and the amount of charge to be purchased, which are designated by the user (S313), The management server further The battery station that performs the charging includes a notification means (21, S314) that notifies the battery station that performs the charging of information about the amount of charge purchased by the user. According to this embodiment, the user's charging reservation information can be notified to the battery station in advance, and the battery desired by the user can be prepared in advance at the battery station, thereby providing batteries efficiently.
[0068] 5. In the above embodiment, The providing means provides the charging rights that can be used at the plurality of battery stations owned by the second business in a lump sum in response to a request from the second business (S303); A predetermined right is allocated to each battery station from among the charging rights collectively provided to the second business operator (S105). According to this embodiment, a business that operates a battery station can purchase and assign charging rights to multiple battery stations under its management in bulk, eliminating the need to go through the purchasing process for each battery station and increasing convenience.
[0069] 6. In the above embodiment, The management means monitors the charging rights held by each battery station, and when the result of the monitoring is that the remaining chargeable amount falls below a predetermined value, it notifies the corresponding battery station or the information processing device of the second operator that owns the battery station of this fact (S321 to S323). According to this embodiment, it is possible to provide a plurality of battery stations capable of charging, preventing failure to purchase charging rights, and thus providing a highly convenient system.
[0070] 7. In the above embodiment, Further, a receiving means (21, S321) for receiving information regarding the result of charging by the battery station is provided, The management means manages the total charge amount that can be charged for each battery based on the information received by the receiving means. According to this embodiment, it is possible to determine the degree of deterioration of the battery, and to know in advance that the battery will become unable to be charged, and to notify a battery station or the like.
[0071] 8. In the above embodiment, the charging right provided in the predetermined unit is related to a total charge amount that can be charged to the battery; The battery station can provide charging service for the battery up to the total charge amount. According to this embodiment, the right to charge can be bought and sold according to the total amount of charge, and management can be easily performed.
[0072] 9. In the above embodiment, The right to charge provided in the predetermined unit is related to the number of times the battery can be charged; The battery station can provide charging service for the battery up to the provided number of charging times. According to this embodiment, the right to charge can be bought and sold according to the number of times charging is performed, and management can be easily performed.
[0073] 10. In the above embodiment, each of said batteries is assigned an individual identification; The battery station can provide a charging service to a battery having identification information managed by the management server. According to this embodiment, it is possible to easily grasp the usage status of each battery.
[0074] 11. In the above embodiment, The battery station cannot provide charging services to batteries whose individual identification information is not managed by the management server. According to this embodiment, it is possible to restrict charging of batteries owned by individuals, and only swap batteries can be targeted for the service, thereby enabling accurate management of charging rights.
[0075] 12. In the above embodiment, When the battery to be charged is inserted into a slot provided in the battery station for receiving the battery, a replacement battery is provided to the user. According to this embodiment, it is possible to prevent battery theft and maintain the quality of service in an optimal manner.
[0076] 13. The system (100) of the above embodiment is A battery charging system (100) in which a management server (2) that manages a battery (6) of a first company that owns a detachable battery (6) for a vehicle (1) and an information processing device (4) that manages a plurality of battery stations (5) that are owned by a second company and that charge the battery can communicate with each other via a network, The management server (2) a management means (24) for managing the right to charge the batteries owned by the first business operator in predetermined units; a provision means (25) for selling the right to charge in the predetermined unit in response to a request from the second business; Equipped with The information processing device (4) a request means (42) for requesting the right to charge from the management server; an allocation means (42) for allocating the charging right provided by the provision means to the plurality of battery stations managed by the information processing device; Equipped with. According to this embodiment, a battery supplier can collectively manage batteries and provide multiple businesses that operate battery stations with the right to charge the batteries. That is, a system can be provided in which batteries managed collectively by a battery supplier can be charged at stations operated by multiple different businesses. This allows users to charge their batteries at the battery station of their choice, further improving convenience.
[0077] 14. In the above embodiment, The management server further Acceptance means (21, 26, S311) for accepting a battery charging reservation from a mobile terminal (3) owned by a user; a response means (21, 26, S312) for notifying the user of the location of a battery station that has the right to charge among the plurality of battery stations in accordance with the accepted charging reservation; Equipped with The mobile terminal a transmission means (31) for transmitting the charging reservation to the management server in accordance with a user operation; a display control means (32) for displaying on a display unit (34) the location of the battery station that has the right to charge, in accordance with information received from the management server as a response to the charge reservation transmitted by the transmission means; Equipped with. According to this embodiment, it is possible to accept a charging reservation in advance and guide the user to a battery station that meets the request.
[0078] The invention is not limited to the above-described embodiment, and various modifications and variations are possible within the scope of the gist of the invention.
Claims
1. A management server that manages batteries of a first business that owns batteries that can be attached to or detached from vehicles, a management means for managing the right to charge in predetermined units based on the number of batteries distributed in the market by the first business; a providing means which is a second business operator that owns a battery station capable of charging the battery, and sells the right to charge in the predetermined unit in response to a request from any of a plurality of different second businesses; Equipped with The management server is characterized in that the battery station provides a charging service for the battery to the user in accordance with the charging right provided in the predetermined unit.
2. Acceptance means for accepting a battery charging reservation from a user; a response means for providing information on the location of the battery station that has the right to charge in accordance with the accepted charging reservation; The management server according to claim 1 , further comprising:
3. 3. The management server according to claim 2, wherein the response means does not notify the location of the battery station for which the charging right is not held.
4. the accepting unit further accepts the battery station to be charged and the amount of charge to be purchased, which are designated by the user; The management server further 4. The management server according to claim 2, further comprising a notification unit that notifies the battery station that performs the charging of information about the amount of charge purchased by the user.
5. the providing means, in response to a request from any of the plurality of second businesses, provides the charging rights that can be used at the plurality of battery stations owned by the second business in a lump sum; A management server as described in any one of claims 1 to 4, characterized in that each battery station is assigned a predetermined right from among the charging rights provided collectively to any of the plurality of second operators.
6. The management server described in any one of claims 1 to 5, characterized in that the management means monitors the charging rights held by each battery station, and when the result of the monitoring indicates that the remaining chargeable amount falls below a predetermined value, notifies the corresponding battery station or any of the information processing devices of the plurality of second operators that own the battery station.
7. a receiving means for receiving information regarding a result of charging by the battery station; 7. The management server according to claim 1, wherein the management unit manages a total charge amount that can be charged for each battery based on the information received by the receiving unit.
8. the charging right provided in the predetermined unit is related to a total charge amount that can be charged to the battery; 8. The management server according to claim 1, wherein the battery station is capable of providing a charging service for the battery up to the total charge amount.
9. The right to charge provided in the predetermined unit is related to the number of times the battery can be charged; 8. The management server according to claim 1, wherein the battery station is capable of providing a charging service for the battery up to the number of charging times provided.
10. each of said batteries is assigned an individual identification; 10. The management server according to claim 1, wherein the battery station is capable of providing a charging service to a battery having identification information managed by the management server.
11. The management server according to claim 10, wherein the battery station cannot provide a charging service to a battery whose individual identification information is not managed by the management server.
12. A management server as described in any one of claims 1 to 11, characterized in that in the battery station, when the battery to be charged is inserted into a slot provided in the battery station that receives the battery, a replacement battery is provided to the user.
13. A control method for a management server that manages a battery of a first business that has a battery that can be attached to a vehicle, comprising: a management step of managing the right to charge in predetermined units based on the number of batteries distributed in the market by the first business; a provision step of selling the right in the predetermined unit in response to a request from any one of a plurality of second businesses that own a battery station capable of charging the battery; Including, The control method of the management server, wherein the battery station provides the user with a charging service for the battery in accordance with the charging right provided in the predetermined unit.
14. A battery charging system in which a management server that manages batteries of a first company that owns batteries that can be attached to or detached from vehicles and an information processing device that manages a plurality of battery stations that charge the batteries and are owned by any of a plurality of different second companies can communicate via a network, The management server a management means for managing the right to charge in predetermined units based on the number of batteries distributed in the market by the first business; a providing means for selling the right to charge in the predetermined unit in response to a request from any one of the plurality of second businesses; Equipped with The information processing device includes: a requesting means for requesting the right to charge from the management server; an allocation means for allocating the charging right provided by the providing means to the plurality of battery stations managed by the information processing device; A battery charging system comprising:
15. The management server further an accepting means for accepting a battery charging reservation from a mobile terminal owned by a user; a response means for notifying the user of a location of a battery station that has the right to charge among the plurality of battery stations in accordance with the accepted charging reservation; Equipped with The mobile terminal a transmitting means for transmitting the charging reservation to the management server in accordance with a user operation; a display control means for displaying on a display unit the location of the battery station that has the right to charge, in accordance with information received from the management server as a response to the charge reservation transmitted by the transmission means; 15. The battery charging system of claim 14, comprising:
Citation Information
Patent Citations
Energy supply system for electric vehicle, battery for electric vehicle, battery charger for the electric vehicle, battery vending apparatus and battery managing system for the electric vehicle
JP2001057711A
Charging system for electric car
JP2013037429A
Battery replacement system for electric vehicle, and program
JP2019004693A
Battery managing system, battery managing method, and terminal device
WO2019163573A1
Battery managing system, battery managing method, and terminal device
WO2020179262A1