Charging management device and charging management method

Abstract

To improve an operation rate of a charger.SOLUTION: A charging management device includes: a processor configured to execute a program; and a storage device configured to store the program. The processor is configured to execute: acquisition processing to acquire a reference unit price of a charging price; selection processing to receive selection of an operation factor from an operation factor group capable of operating the reference unit price acquired by the acquisition processing; and calculation processing of calculating a charging unit price based on the reference unit price and the operation factor selected by the selection processing.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a charge management device and a charge management method for managing charging. [Background technology]

[0002] The environment for utilizing EVs (Electric Vehicles) is being developed in Japan as well, but domestic businesses have pointed out the low utilization rate of existing chargers. To improve the utilization rate of existing chargers at corporations, the corporations that host the chargers need to integrate with vehicle dispatch reservation systems and attendance plans to incorporate charging plans into delivery operations for specific deployed vehicles. In that case, it will be difficult for the corporations that host the chargers to determine how to set prices for the charger groups and distribute the set prices when the number of chargers they manage increases in the future.

[0003] The pricing system of Patent Document 1 below includes an input unit, a determination unit, and a price setting unit. The input unit inputs demand data indicating a time-series demand for the service, the data being generated based on data indicating at least one of a customer's actions of reservation, purchase, and settlement for the service. The determination unit determines predetermined associated data for the demand data. The price setting unit sets a price for the service at a predetermined target time based on the demand data and the predetermined associated data. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 7081733 Summary of the Invention [Problem to be solved by the invention]

[0005] However, no consideration is given to manipulating the charging unit price based on the operating status of the charger.

[0006] An object of the present invention is to improve the operating rate of a charger. [Means for solving the problem]

[0007] A charging management device which is one aspect of the invention disclosed in the present application is a charging management device having a processor which executes a program and a storage device which stores the program, and is characterized in that the processor executes an acquisition process which acquires a standard unit price for charging prices, a selection process which accepts the selection of an operation factor from a group of operation factors of the standard unit price based on the operation status of a charger installed in a parking lot, and a calculation process which calculates the charging unit price of the charger based on the standard unit price and the operation factor selected by the selection process. Effect of the Invention

[0008] According to the representative embodiment of the present invention, it is possible to improve the operating rate of a charger. Problems, configurations and effects other than those described above will become apparent from the following description of the embodiment. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is an explanatory diagram showing an example of how an electric vehicle runs. [Diagram 2] FIG. 2 is an explanatory diagram illustrating an example of the system configuration of the charging unit price calculation system. [Diagram 3] FIG. 3 is a block diagram showing an example of the hardware configuration of a computer. [Figure 4] FIG. 4 is an explanatory diagram illustrating an example of the parking lot DB. [Diagram 5] FIG. 5 is an explanatory diagram showing an example of the reservation information DB. [Figure 6] FIG. 6 is an explanatory diagram illustrating an example of the incoming / outgoing record DB. [Figure 7] FIG. 7 is an explanatory diagram showing an example of the charger operation information DB. [Figure 8] FIG. 8 is an explanatory diagram illustrating an example of the charging result management DB. [Figure 9]FIG. 9 is an explanatory diagram showing an example of the charging unit price operation factor DB. [Figure 10] FIG. 10 is an explanatory diagram illustrating an example of the charging fee calculation DB. [Figure 11] FIG. 11 is a flowchart illustrating a first operational example of the edge device. [Figure 12] FIG. 12 is a flowchart illustrating a second operation example of the edge device. [Figure 13] FIG. 13 is a flowchart illustrating a third operation example of the edge device. [Figure 14] FIG. 14 is a flowchart showing a fourth operation example of the edge device. [Figure 15] FIG. 15 is a flowchart showing a first operation example of the charge managing server. [Figure 16] FIG. 16 is a flowchart showing a second operation example of the charge managing server. [Figure 17] FIG. 17 is a flowchart illustrating an example of a charging price calculation process performed by the charging management server. [Figure 18] FIG. 18 is a flowchart illustrating an example of an electricity cost calculation process performed by the charging management server. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] <Example of electric vehicle operation> Fig. 1 is an explanatory diagram showing an example of the running of an electric vehicle. The electric vehicle 101 is a vehicle that runs on electricity charged in an internal battery. The electric vehicle 101 runs along a set route 100. The electric vehicle 101 may be a corporate business vehicle, a delivery vehicle, a taxi, or a privately owned vehicle.

[0011] The route 100 includes waypoints P1 to P5. The waypoint P1 is the starting point of the waypoint P1, and the waypoint P5 is also the destination point (hereinafter referred to as destination point P5). The waypoint P1 may be the destination point. The waypoint P4 is a parking lot 102.

[0012] The parking lot 102 is managed by an edge device 121. The parking lot 102 also includes a gate 122, a gate-side camera 123, a parking space 124, a flapper 125, a charger 126, and a parking space-side camera 127.

[0013] The gate 122 is an entrance / exit through which the electric vehicle 101 enters and exits the parking lot 102. The gate-side camera 123 captures an image of the license plate of the electric vehicle 101 passing through the gate 122, and transmits the captured image data to the edge device 121. The parking space 124 is an area where the electric vehicle 101 is parked. The flapper 125 is a device that restricts the movement of the electric vehicle 101 by raising a flap plate and releases the movement restriction by lowering the flap plate. The flapper 125 has a weight sensor, and raises the flap plate when it detects the passage of the electric vehicle 101. The flapper 125 lowers the flap plate in response to a release signal from the edge device 121.

[0014] The charger 126 is a facility for charging the electric vehicle 101. The electric vehicle 101 is charged by connecting a nozzle of the charger 126 to the electric vehicle 101. The parking space side camera 127 captures an image of the license plate of the electric vehicle 101 parked in the parking space 124 and transmits the captured image data to the edge device 121.

[0015] <System configuration example> 2 is an explanatory diagram showing an example of a system configuration of a charging unit price calculation system. The charging unit price calculation system 200 includes a charging management server 201 and an edge device 121. The charging management server 201 and the edge device 121 are communicatively connected via a network 210 such as the Internet, a LAN (Local Area Network), or a WAN (Wide Area Network).

[0016] The charging management server 201 is a computer that calculates a charging unit price. The charging management server 201 can access a parking lot DB 202, a reservation information DB 203, a parking entry / exit record DB 204, a charger operation information DB 205, a charging record management DB 206, a charging unit price operation factor DB 207, and a charging fee calculation DB 208. These DBs may be stored inside the charging management server 201, or may be stored in another computer that can communicate with the charging management server 201 via a network 210.

[0017] The edge device 121 is a computer that manages the parking lot 102. The edge device 121 is connected to a gate-side camera 123, a flapper 125, a charger 126, and a parking space-side camera 127 so as to be able to communicate with each other.

[0018] The communication terminal 230 is connected to the charging management server 201 and the edge device 121 via the network 210 so as to be able to communicate with each other.

[0019] The reservation server 250 is communicatively connected to the charging management server 201 via the network 210. It is a computer that sets reservation information for the electric vehicle 101 and the parking lot 102. The reservation information includes the vehicle ID 503 of the electric vehicle 101, a parking lot ID that identifies the parking lot 102, and a parking space ID that identifies the reserved parking space in which the electric vehicle 101 should be parked in the parking lot 102. The reservation server 250 transmits the reservation information to the charging management server 201.

[0020] <Example of Hardware Configuration of Computers (Charge Management Server 201, Edge Device 121, Reservation Server 250)> FIG. 3 is a block diagram showing an example of a hardware configuration of a computer. The computer 300 includes a processor 301, a storage device 302, an input device 303, an output device 304, and a communication interface (communication IF) 305. The processor 301, the storage device 302, the input device 303, the output device 304, and the communication IF 305 are connected by a bus 306. The processor 301 controls the computer 300. The storage device 302 serves as a working area for the processor 301. The storage device 302 is a non-transient or temporary recording medium that stores various programs and data. Examples of the storage device 302 include a read only memory (ROM), a random access memory (RAM), a hard disk drive (HDD), and a flash memory. The input device 303 inputs data. Examples of the input device 303 include a keyboard, a mouse, a touch panel, a numeric keypad, a scanner, a microphone, and a sensor. The output device 304 outputs data. The output device 304 may be, for example, a display, a printer, or a speaker. The communication IF 305 is connected to the network 210 and transmits and receives data.

[0021] <Parking lot database> 4 is an explanatory diagram showing an example of the parking lot DB 202. The parking lot DB 202 is a database that stores information about the parking lot 102. The parking lot DB 202 has the following fields: parking lot ID 401, location information 402, edge device ID 403, and parking lot information 404. A combination of values ​​of each field in the same row forms an entry that specifies one piece of parking lot information.

[0022] The parking lot ID 401 is identification information that uniquely identifies the parking lot 102. The location information 402 is information that indicates the location of the parking lot 102, such as latitude and longitude. The edge device ID 403 is identification information that uniquely identifies the edge device 121 that manages the parking lot 102.

[0023] The parking lot information 404 has a parking space ID 441, a flapper ID 442, a charger ID 443, a charging output 444, and a charging cost 445 in the parking lot 102. The parking space ID 441 is identification information that uniquely identifies the parking space 124. The flapper ID 442 is identification information that uniquely identifies the flapper 125. The charger ID 443 is identification information that uniquely identifies the charger 126. The charging output 444 is the output performance of the charger 126. The charging cost 445 is the charging price per 1 kW-hour.

[0024] <Reservation information DB203> 5 is an explanatory diagram showing an example of the reservation information DB 203. The reservation information DB 203 is a table that manages reservation information for the electric vehicle 101. The reservation information DB 203 has a parking lot ID 401 and reservation information 500 as fields.

[0025] The reservation information 500 is information related to a reservation made for the parking lot 102. Specifically, for example, the reservation information 500 has a reservation ID 501, a user ID 502, a vehicle ID 503, a reservation start time 504, a reservation end time 505, a previous location 506, a next location 507, and a predicted electricity consumption 508. The reservation information 500 is obtained from the reservation server 250.

[0026] The reservation ID 501 is identification information that uniquely identifies the reservation information 500 for the electric vehicle 101 .

[0027] The user ID 502 is identification information that uniquely identifies the user 240 of the electric vehicle 101 .

[0028] The vehicle ID 503 is identification information that uniquely identifies the electric vehicle 101 used by the user 240 identified by the user ID 502. Specifically, for example, the vehicle ID 503 is the vehicle number indicated on the license plate.

[0029] The reservation start time 504 is the reservation time at which the electric vehicle 101 identified by the vehicle ID 503 starts parking in the parking lot 102 identified by the parking lot ID 401 .

[0030] The reservation end time 505 is the reservation time at which parking of the electric vehicle 101 identified by the vehicle ID 503 in the parking lot 102 identified by the parking lot ID 401 ends.

[0031] The previous point 506 is a point where the electric vehicle 101 identified by the vehicle ID 503 passes before the parking lot 102, which is the pass point.

[0032] The next point 507 is a point through which the electric vehicle 101 identified by the vehicle ID 503 passes after the parking lot 102, which is the pass point.

[0033] The predicted electricity consumption 508 is a predicted value of electricity consumption, which is a driving index of the electric vehicle 101 identified by the vehicle ID 503. The electricity consumption is a driving index indicating the driving distance of the electric vehicle 101 per 1 kWh of electricity, and is expressed in units of "km / kWh". The predicted electricity consumption 508 may be set by the reservation server 250 or may be set by the charging management server 201.

[0034] <Incoming / Outgoing Record DB204> 6 is an explanatory diagram showing an example of the entry / exit record DB 204. The entry / exit record DB 204 is a table that manages the records of entry and exit of the electric vehicle 101 in the parking lot 102. The entry / exit record DB 204 has a parking lot ID 401 and record information 600 as fields.

[0035] The performance information 600 includes a performance ID 601, a parking space ID 441, an entry time 602, an exit time 603, a charging start time 604, a charging end time 605, an acquired user ID 606, an acquired vehicle ID 607, a corresponding reservation ID 608, and a reservation difference judgment 609.

[0036] The performance ID 601 is identification information that uniquely identifies the performance information 600 .

[0037] The entry time 602 is the time when the electric vehicle 101 driven by the user 240 identified by the user ID 502 via the reservation ID 501 actually enters the parking lot 102. More specifically, it is the time when the image is captured by the gate-side camera 123 at the time of entry.

[0038] The departure time 603 is the time when the electric vehicle 101 driven by the user 240 identified by the user ID 502 via the reservation ID 501 actually leaves the parking lot 102. More specifically, it is the time when the image is captured by the gate-side camera 123 at the time of departure.

[0039] The charging start time 604 is the time when the electric vehicle 101 driven by the user 240 identified by the user ID 502 via the reservation ID 501 actually starts charging at the charger 126. When the nozzle of the charger 126 is connected to the electric vehicle 101, a detection signal including the time of the connection is transmitted from the charger 126 to the edge device 121.

[0040] The charging start time 604 is the time when the electric vehicle 101 driven by the user 240 identified by the user ID 502 via the reservation ID 501 actually finishes charging at the charger 126. When the nozzle of the charger 126 is detached from the electric vehicle 101, a detection signal including the time of detachment is transmitted from the charger 126 to the edge device 121.

[0041] The acquired user ID 606 is the user ID 502 associated with the vehicle ID 503 recognized from the image data of the license plate captured by the gate side camera 123 or the parking space side camera 127.

[0042] The acquired vehicle ID 607 is the vehicle ID 503 recognized from the image data of the license plate captured by the gate side camera 123 or the parking space side camera 127.

[0043] The corresponding reservation ID 608 is the reservation ID 501 of the reservation information 500 in which the parking lot ID 401 , the acquired user ID 606 , and the acquired vehicle ID 607 match the parking lot ID 401 , the user ID 502 , and the vehicle ID 503 .

[0044] When the flapper 125 of the parking space 124 detects the vehicle weight, the edge device 121 identifies the parking space ID 441 corresponding to the flapper ID 442 of the flapper 125, and transmits it to the charging management server 201 together with the parking lot ID 401 and the entry time 602. The charging management server 201 stores the received information (parking space ID 441, entry time 602) in the performance information 600 of the received parking lot ID 401.

[0045] <Charger operation information DB205> 7 is an explanatory diagram showing an example of the charger operation information DB 205. The charger operation information DB 205 is a table showing the operation status of the charger 126. The charger operation information DB 205 has a parking lot ID 401 and charger operation information 700. The charger operation information 700 has a charger ID 701, an operation status 702, and a remaining charging time 703.

[0046] The charger ID 701 is identification information that uniquely identifies the charger 126 .

[0047] The operation status 702 is information indicating whether the charger 126 identified by the charger ID 701 is in operation or not. "1" indicates that the charger 126 is in operation, and "0" indicates that the charger is not in operation.

[0048] The remaining charging time 703 is the remaining time for charging by the charger 126 identified by the charger ID 701. Specifically, for example, it is the time from the current time to the reservation end time 505 of the electric vehicle being charged by the charger 126.

[0049] <Charging record management DB206> 8 is an explanatory diagram showing an example of the charging record management DB 206. The charging record management DB 206 is a table for managing the charging record by the charger 126. The charging record management DB 206 has, as fields, a user ID 502, a reservation ID 501, a record ID 601, a total payment amount 801, a charging unit price at the time of payment 802, and a charging unit price operation factor ID 803. A combination of values ​​of the respective fields in the same row becomes an entry that specifies one charging record.

[0050] The total payment amount 801 is the charging fee paid by the user 240 identified by the user ID 502. Specifically, for example, the total payment amount=charging time×charging unit price at time of payment. The charging time is the time from the charging start time 604 to the charging end time 605.

[0051] The charging unit price at payment 802 is the charging unit price 445 when the total payment amount 801 is paid. The time when the total payment amount 801 is paid is, for example, the charging end time 605.

[0052] The charging price operation factor ID 803 is identification information that uniquely identifies the charging price operation factor. The charging price operation factor is a factor that operates (increases or decreases) the charging price. Specifically, for example, the charging price operation factor is a factor for operating the reference electricity price 1001 (described later) based on the operation status of the charger 126 installed in the parking lot 102. The charging price varies depending on the charging price operation factor.

[0053] <Charging unit price operation factor DB207> 9 is an explanatory diagram showing an example of the charging unit price operation factor DB207. The charging unit price operation factor DB207 is a table that specifies charging unit price operation factors. The charging unit price operation factor DB207 has fields including a charging unit price operation factor ID 803, an event 901, and a weight 902. A combination of values ​​in each field in the same row becomes an entry that specifies one unit price increase factor.

[0054] The event 901 is the cause of the occurrence of a charging unit price operation factor identified by the charging unit price operation factor ID 804 .

[0055] The weight 902 is a coefficient for varying the charging price 445 with the charging price operation factor specified by the charging price operation factor ID 804 .

[0056] <Charging Fee Calculation DB208> 10 is an explanatory diagram showing an example of the charging fee calculation DB 208. The charging fee calculation DB 208 has, as fields, a parking lot ID 401, a reference electricity unit price 1001, a minimum price 1002, a maximum price 1003, an applied charging unit price operation factor ID 1004, and a new charging unit price 1005.

[0057] The standard electricity unit price 1001 is the standard electricity unit price in the parking lot 102 .

[0058] The minimum price 1002 is the lower limit of the charging price 445 .

[0059] The maximum price 1003 is the upper limit of the charging price 445.

[0060] The applied charging unit price operation factor ID 1004 is the charging unit price operation factor ID 803 applied in the parking lot 102 .

[0061] The new charging unit price 1005 is the charging unit price 445 after the operation based on the applied charging unit price operation factor ID 1004. The new charging unit price 1005 is a result of multiplying the reference power unit price 1001 by each weight 902 of the applied charging unit price operation factor ID 1004.

[0062] For example, in the case of an entry in which the parking lot ID 401 is "P1", the applicable charging unit price operation factor ID 1004 is only "UF3". The weight 902 of "UF3" is "1.1". Therefore, the new charging unit price 1005 of "P1" is 15 [yen / kWh] x 1.1 = 16.5 [yen / kWh].

[0063] For an entry in which the parking lot ID 401 is "P2", the applied charging unit price operation factor ID 1004 is "UF1" and "UF3". The weight 902 of "UF1" is "1.3". Therefore, the new charging unit price 1005 of "P2" is 15 [yen / kWh] x 1.3 x 1.1 = 21.5 [yen / kWh].

[0064] <Operation example 1 of edge device 121> 11 is a flowchart showing a first operation example of the edge device 121. FIG. 11 shows an operation example of the edge device 121 when the electric vehicle 101 enters the parking lot 102.

[0065] (Step S1101) The edge device 121 acquires the vehicle ID 503 from the image data captured by the gate-side camera 123 .

[0066] (Step S1102) The edge device 121 acquires the entry detection data (lock flag) of the flapper 125.

[0067] (Step S1103) The edge device 121 acquires the time when the flapper 125 is locked as the entry time 602 .

[0068] (Step S1104) The edge device 121 acquires the parking space ID 441 and the charger ID 443 corresponding to the flapper 125 from the parking lot information 404 of the parking lot DB 202 .

[0069] (Step S1105) The edge device 121 acquires the vehicle ID 503 of the electric vehicle 101 that has entered the parking space 124 of the activated flapper 125 from image data captured by the parking space side camera 127.

[0070] (Step S1106) The edge device 121 transmits the vehicle ID 503, the lock flag, the entry time 602, the parking space ID 441, the charger ID 443, and the parking lot ID 401 that are matched in steps S1101 and S1105 as entry data to the charging management server 201. The entry time 602 and the parking space ID 441 are registered as record information 600 in the entry / exit record DB 204.

[0071] <Operation example 2 of edge device 121> 12 is a flowchart showing a second operation example of the edge device 121. FIG 12 shows an operation example of the edge device 121 when the electric vehicle 101 starts charging after entering the parking lot 102.

[0072] (Step S1201) The edge device 121 determines whether or not the start of charging has been detected. Specifically, for example, the edge device 121 determines whether or not the nozzle of the charger 126 is connected to the electric vehicle 101.

[0073] (Step S1202) The edge device 121 acquires the charger ID 443 and the charging start time 604 from the charger 126 .

[0074] (Step S1203) The edge device 121 transmits the parking lot ID 401, the charger ID 443, and the charging start time 604 as charging start data to the charging management server 201. The charging start time 604 is registered as record information 600 in the entry / exit record DB 204.

[0075] <Operation example 3 of edge device 121> Fig. 13 is a flowchart showing a third operation example of the edge device 121. Fig. 13 shows an operation example of the edge device 121 when charging is completed after the electric vehicle 101 enters the parking lot 102.

[0076] (Step S1301) The edge device 121 determines whether or not the end of charging has been detected. Specifically, for example, the edge device 121 determines whether or not the nozzle of the charger 126 has been detached from the electric vehicle 101.

[0077] (Step S1302) The edge device 121 acquires the charger ID 443 and the charging end time 605 from the charger 126 .

[0078] (Step S1303) The edge device 121 transmits the parking lot ID 401, the charger ID 443, and the charging end time 605 as charging end data to the charging management server 201. The charging end time 605 is registered as the record information 600 in the entry / exit record DB 204.

[0079] <Operation example 4 of edge device 121> 14 is a flowchart showing a fourth operation example of the edge device 121. FIG. 14 shows an operation example of the edge device 121 when the electric vehicle 101 leaves the parking lot 102.

[0080] (Step S1401) The edge device 121 acquires the exit detection data (unlock flag) of the flapper 125.

[0081] (Step S1402) The edge device 121 acquires the time when the flapper 125 is unlocked as the exit time 603 .

[0082] (Step S1403) The edge device 121 acquires the parking space ID 441 and the charger ID 443 corresponding to the flapper 125 from the parking lot information 404 of the parking lot DB 202 .

[0083] (Step S1404) The edge device 121 acquires the vehicle ID 503 of the electric vehicle 101 that is leaving the parking space 124 of the activated flapper 125 from the image data captured by the parking space side camera 127.

[0084] (Step S1405) The edge device 121 acquires the vehicle ID 503 of the electric vehicle 101 leaving the parking lot from image data captured by the gate-side camera 123.

[0085] (Step S1106) The edge device 121 transmits the vehicle ID 503, the unlocking flag, the exit time 603, the parking space ID 441, the charger ID 443, and the parking lot ID 401, which are matched in steps S1401 and S1405, as exit data to the charging management server 201. The exit time 603 is registered as record information 600 in the entry / exit record DB 204.

[0086] <Operation Example 1 of the Charging Management Server 201> FIG. 15 is a flowchart showing a first operation example of the charge managing server 201.

[0087] (Step S1501) The charging management server 201 acquires reservation status data from the reservation server 250. The reservation status data includes a parking lot ID 401, a reservation ID 501, a user ID 502, a vehicle ID 503, a reservation start time 504, a reservation end time 505, a previous location 506, a next location 507, and a predicted electricity consumption 508.

[0088] (Step S1502) The charging management server 201 registers the acquired reservation status data in the reservation information DB 203 .

[0089] <Operation Example 2 of Charging Management Server 201> FIG. 16 is a flowchart showing a second operation example of the charging management server 201.

[0090] (Step S1601) The charging management server 201 waits for reception of the storage data in step S1606. If the storage data is not received (step S1601: No), the process proceeds to END. If the storage data is received (step S1601: Yes), the process proceeds to step S1602.

[0091] (Step S1602) The charging management server 201 assigns a record ID 601 to the received storage data, and adds an entry to the storage / delivery record DB 204 .

[0092] (Step S1603) The charging management server 201 acquires the user ID 502 and the reservation ID 501 corresponding to the vehicle ID 503 from the reservation information DB 203 , and adds them to the entry of the entry / retrieval record DB 204 as an acquired user ID 606 and an acquired vehicle ID 607 .

[0093] (Step S1604) The charging management server 201 waits for reception of the charging start data in step S1203. If the charging start data is not received (step S1604: No), the process proceeds to END. If the charging start data is received (step S1604: Yes), the process proceeds to step S1605.

[0094] (Step S1605) The charging management server 201 adds the charging start time 604 to an entry in the entry / withdrawal record DB 204. Specifically, for example, the charging management server 201 identifies the parking space ID 441 corresponding to the charger ID 443 in the charging start data, identifies an entry in which the identified parking space ID 441 is located from the entry / withdrawal record DB 204, and adds the charging start time 604 to the identified entry.

[0095] (Step S1606) The charging management server 201 identifies an entry in the charger operation information DB 205 and updates the operation status 702. Specifically, for example, the charging management server 201 identifies the charger operation information 700 in the charger operation information DB 205 from the parking lot ID 401 of the charging start data, identifies the entry of the charger ID 443 of the charging start data from the charger operation information 700, and updates the operation status 702 from "0" to "1". The charging management server 201 also calculates and updates the remaining charging time 703. The remaining charging time 703 is set to the time from the current time to the reservation end time 505 of the electric vehicle 101 being charged by the charger 126, and decreases as time passes.

[0096] (Step S1607) The charging management server 201 waits for reception of the charging end data in step S1303. If the charging end data is not received (step S1607: No), the process proceeds to END. If the charging end data is received (step S1607: Yes), the process proceeds to step S1608.

[0097] (Step S1608) The charging management server 201 adds the charging end time 605 to an entry in the entry / unloading record DB 204. Specifically, for example, the charging management server 201 identifies the parking space ID 441 corresponding to the charger ID 443 in the charging end data, identifies an entry in which the identified parking space ID 441 is located from the entry / unloading record DB 204, and adds the charging end time 605 to the identified entry.

[0098] (Step S1609) The charging management server 201 identifies an entry in the charger operation information DB 205 and updates the operation status 702. Specifically, for example, the charging management server 201 identifies the charger operation information 700 in the charger operation information DB 205 from the parking lot ID 401 of the charging end data, identifies the entry of the charger ID 443 of the charging end data from the charger operation information 700, and updates the operation status 702 from "1" to "0." In addition, the charging management server 201 resets the remaining charging time 703 to 0.

[0099] If the remaining charging time 703 becomes 0 before receiving the charging end data, the charging management server 201 may instruct the edge device 121 that controls the charger 126 to end charging.

[0100] (Step S1610) The charge management server 201 waits for reception of the delivery data in step S1406. If the delivery data is not received (step S1610: No), the process proceeds to END. If the delivery data is received (step S1610: Yes), the process proceeds to step S1611.

[0101] (Step S1611) The charging management server 201 identifies an entry in the parking entry / exit record DB 204 from the parking space ID 441 included in the received exit data, and registers the exit time 603 .

[0102] <Charging unit price calculation process> FIG. 17 is a flowchart showing an example of a charging price calculation process performed by the charging management server 201.

[0103] (Step S1701) The charging management server 201 acquires the reservation information 500 from the reservation information DB 203 .

[0104] (Step S1702) The charging management server 201 identifies a parking lot subject to charging price manipulation from the reservation information 500 and the delivery route plan. The delivery route plan is acquired from the reservation server 250. The delivery route plan is plan data indicating a delivery route of the electric vehicle 101, and includes, for example, the route 100 shown in FIG. 1 and the vehicle ID 503 and user ID 502 of the electric vehicle 101 traveling on the route 100.

[0105] The charging management server 201 identifies the position information 402 of the waypoint P4 where the parking lot 102 is located on the route 100 from the parking lot DB 202, and identifies the parking lot 102 at the waypoint P4 as a parking lot subject to charging price manipulation. Note that the charging management server 201 may also identify parking lots 102 located within a predetermined distance from each of the points P1 to P5 on the route 100 as parking lots subject to charging price manipulation.

[0106] (Step S1703) The charging management server 201 acquires the reference electricity unit price 1001 corresponding to the parking lot ID 401 of the parking lot that is the target of charging price manipulation from the charging fee calculation DB 208.

[0107] (Step S1704) The charging management server 201 judges whether there is a parking lot ID 401 of an unselected charging price operation target parking lot. If there is a parking lot ID 401 of an unselected charging price operation target parking lot (step S1704: Yes), the process proceeds to step S1705. If there is no parking lot ID 401 of an unselected charging price operation target parking lot (step S1704: No), the process proceeds to END.

[0108] (Step S1705) The charging management server 201 refers to the charging unit price operation factor DB 207 and accepts the selection of the charging price operation factor. Specifically, for example, the charging management server 201 displays the charging unit price operation factor ID 803, the event 901, and the weight 902 of the charging unit price operation factor DB 207 on a display screen and waits for a selection from the user. When the selection from the user is accepted, the process proceeds to step S1706.

[0109] (Step S1706) The charging management server 201 calculates a new charging price 1005 by multiplying the reference electricity price 1001 by the weight 902 of the selected charging price operation factor.

[0110] (Step S1707) The charging management server 201 judges whether the new charging unit price 1005 is between the minimum price 1002 and the maximum price 1003. If the new charging unit price 1005 is not between the minimum price 1002 and the maximum price 1003 (step S1707: No), the process returns to step S1705. If the new charging unit price 1005 is between the minimum price 1002 and the maximum price 1003 (step S1707: Yes), the process proceeds to step S1708.

[0111] (Step S1708) The charging management server 201 outputs the new charging price 1005 in a displayable manner.

[0112] (Step S1709) The charging management server 201 updates the new charging unit price 1005 in the charging fee calculation DB 208, and returns to step S1704.

[0113] Specifically, for example, the charging management server 201 overwrites the new charging unit price 1005 to the charging price 445 of the charger ID 443. As a result, the new charging unit price 1005 is reflected in the charger 126.

[0114] <Electricity cost calculation process> FIG. 18 is a flowchart showing an example of a procedure of a power cost calculation process performed by the charging management server 201.

[0115] (Step S1801) The charging management server 201 judges whether or not there is an unselected record ID 601. If there is no unselected record ID 601 (step S1801: No), the process returns to step S1801. If there is an unselected record ID 601 (step S1801: Yes), the process proceeds to step S1802.

[0116] (Step S1802) The charging management server 201 selects an entry of an unselected record ID 601 from the incoming / outgoing record DB 204 .

[0117] (Step S1803) The charging management server 201 acquires the cruising distance (the distance from the parking lot 102 to the next point 507). The charging management server 201 calculates the cruising distance based on the position information 402 of the parking lot 102 and the position information on the map of the next point 507. The charging management server 201 may acquire the distance by accessing a map server (not shown) capable of calculating the distance between two points.

[0118] (Step S1804) The charging management server 201 acquires the battery capacity at the time of leaving the depot. Specifically, for example, the battery capacity at the time of leaving the depot is calculated by the rated output of the charger x the charging time. For example, in the entry with the actual ID 601 of "a41" shown in Fig. 6, since the charging time (charging end time 605-charging start time 604) is 48 minutes, if the charging output 444 is rated at 50 kW, then 50 x 48 ÷ 60 = 40 kW has been charged.

[0119] (Step S1805) The charging management server 201 calculates the electricity cost. Specifically, for example, the charging management server 201 calculates the electricity cost by dividing the cruising distance by the battery capacity at the time of departure.

[0120] (Step S1806) The charging management server 201 determines whether the difference between the estimated and actual electricity consumption is within an acceptable range. Specifically, for example, the charging management server 201 determines whether the difference between the electricity consumption calculated in step S1805 and the estimated electricity consumption 508 is within an acceptable range. If it is within the acceptable range (step S1806: Yes), the charging management server 201 proceeds to step S1807. If it is not within the acceptable range (step S1806: No), the charging management server 201 proceeds to step S1808.

[0121] (Step S1806) The charging management server 201 outputs information indicating that there is no effect on the electricity cost in a displayable manner together with the electricity cost.

[0122] (Step S1807) The charging management server 201 outputs information indicating that there is an impact on the electricity cost in a displayable manner together with the electricity cost.

[0123] In this way, according to this embodiment, the charging price 446 of the charger 126 can be manipulated depending on the operation status. Therefore, since the charging price 446 varies depending on the parking lot 102, the user can be guided to a parking lot 102 with a low charging price 446 by setting a route that passes through a point with a low charging price 446, for example.

[0124] The present invention is not limited to the above-described embodiments, and includes various modified examples and equivalent configurations within the spirit of the appended claims. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those having all of the configurations described. Also, a part of the configuration of one embodiment may be replaced with a configuration of another embodiment. Also, a configuration of another embodiment may be added to a configuration of one embodiment. Also, a part of the configuration of each embodiment may be added, deleted, or replaced with another configuration.

[0125] Furthermore, each of the aforementioned configurations, functions, processing units, processing means, etc. may be realized in hardware, for example by designing some or all of them as an integrated circuit, or may be realized in software by a processor interpreting and executing a program that realizes each function.

[0126] Information such as programs, tables, files, etc. that realize each function can be stored in a storage device such as a memory, a hard disk, or an SSD (Solid State Drive), or in a recording medium such as an IC (Integrated Circuit) card, an SD card, or a DVD (Digital Versatile Disc).

[0127] In addition, the control lines and information lines shown are those considered necessary for the explanation, and do not necessarily show all the control lines and information lines necessary for implementation. In reality, it can be considered that almost all components are connected to each other. [Explanation of symbols]

[0128] 100 routes 101 Electric Vehicle 102 Parking Lot 121 Edge Devices Gate 122 123 Gate side camera 124 Parking spaces 125 Flapper 126 Charger 127 Parking space side camera 200 Charging unit price calculation system 201 Charging management server

Claims

1. A charging management device having a processor that executes a program and a storage device that stores the program, The processor, An acquisition process for acquiring a base unit price of a charging price; A selection process of accepting a selection of any one of an operation factor group of the reference unit price based on an operation status of a charger installed in a parking lot; a calculation process of calculating a charging unit price of the charger based on the reference unit price and the operation factor selected by the selection process; A charging management device comprising:

2. The charge management device according to claim 1, The group of operation factors includes an increase factor that increases the base unit price, A charging management device characterized by:

3. The charge management device according to claim 1, The group of operation factors includes a reduction factor that reduces the base unit price. A charging management device characterized by:

4. The charge management device according to claim 1, The processor, a setting process for setting the charging unit price calculated by the calculation process to a charging unit price when the charger is used in the parking lot; A charging management device comprising:

5. The charge management device according to claim 4, In the setting process, when the charging unit price calculated by the calculation process is within an allowable range, the processor sets the charging unit price calculated by the calculation process as the charging unit price when using the charger installed in the parking lot. A charging management device characterized by:

6. The charge management device according to claim 4, The processor, Executing a process of identifying the parking lot based on the route; In the selection process, the processor accepts a selection of any one of the operation factors from the group of operation factors for the charger installed in the parking lot identified by the identification process; In the setting process, the processor sets the charging unit price calculated in the calculation process as a charging unit price when using the charger installed in the parking lot identified in the identification process. A charging management device characterized by:

7. A charge management method executed by a charge management device having a processor that executes a program and a storage device that stores the program, The processor, An acquisition process for acquiring a base unit price of a charging price; A selection process of accepting a selection of any one of the operation factors from a group of operation factors capable of manipulating the base unit price acquired by the acquisition process; A calculation process of calculating a charging unit price based on the reference unit price and the operation factor selected by the selection process; A charge management method comprising the steps of:

Images