Information processing device, system and method
Patent Information
- Application Number
- JP2021025630
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-02-19
- Publication Date
- 2025-02-27
- Estimated Expiration
- 2041-02-19
AI Technical Summary
【0008】 本発明によれば、エネルギー供給対象へのエネルギーの提供やエネルギー供給対象によるエネルギーの利用を管理できるエネルギー出力部の数の増大や設置エリアの拡充を容易にすることができる。
Smart Images

Figure 0007636777000005 
Figure 0007636777000006 
Figure 0007636777000007
Abstract
Description
[Technical field]
[0001] The present invention relates to an information processing device, a system, and a method for managing an energy supply service that supplies energy such as electric power. [Background technology]
[0002] Conventionally, a system for managing an electric power supply service via an outlet has been known. For example, Patent Document 1 discloses a system including an electric power supply gate device that controls the supply of electric power, a server device (information processing device) that manages the usage fee for the electric power supplied from the electric power supply gate device, and a mobile outlet (energy output unit) that connects the electric power supply gate device and an electric vehicle (energy supply target). The mobile outlet is provided with a power usage integrator (detection unit) for measuring how much electric power the electric vehicle has used. After the electric power from the electric power supply gate device is output from the mobile outlet and supplied to the electric vehicle, the current amount of electric power supply detected by the power usage integrator (energy supply information) is transmitted from the mobile outlet to the server device, and the server device calculates the usage fee for the electric power from the received amount of electric power supply. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2002-325357 A Summary of the Invention [Problem to be solved by the invention]
[0004] In recent years, there has been a demand for an increase in the number of energy output units capable of managing the provision of energy to energy supply targets such as electric vehicles and the use of energy by the energy supply targets, and an expansion of the installation area in which the energy output units are installed. However, due to various constraints, it is difficult to increase the number of energy output units and expand the installation area. [Means for solving the problem]
[0005] An information processing device according to one aspect of the present invention is an information processing device that manages an energy supply service, and includes a provider registration information acquisition unit that acquires provider registration information including information of a provider who owns or manages an energy output unit that can be used for the energy supply service and information of the energy output unit, a user registration information acquisition unit that acquires user registration information including information of a user who uses, owns or manages an energy supply target that can use energy supplied by the energy supply service and information of the energy supply target, a storage unit that stores the provider registration information in association with output unit identification information for identifying the energy output unit, and stores the user registration information in association with supply target identification information that identifies the energy supply target and information of a mobile terminal device used by the user when using the energy supply service, and a storage unit that stores the user registration information in association with supply target identification information that identifies the energy supply target and information of a mobile terminal device used by the user when using the energy supply service, when use of the energy supply service is started, the energy supply service provided by the energy supply provider from the energy output unit of the provider to the energy supply target of the user when the energy supply service is used; a payment processing unit that refers to information stored in the memory unit and performs necessary processing to pay the provider a fee for providing the energy supply service from the energy output unit to the energy supply target based on the energy supply information acquired by the supply information acquisition unit; and a billing processing unit that refers to information stored in the memory unit and performs necessary processing to bill the user for the usage fee for the energy supply service from the energy output unit to the energy supply target based on the energy supply information acquired by the supply information acquisition unit. In the information processing device, the energy output unit may receive energy from an energy supplier to whom the provider pays an energy fee based on the combined amount of energy supplied from the energy output unit to the energy supply target and energy supplied from sources other than the energy output unit to other supply targets other than the energy supply target, and supply the energy to the energy supply target. In addition, in the information processing device, the supply information acquisition unit may acquire, as the energy supply information, at least user side identification information of the party that uses energy, provider side identification information of the party that provides energy, and variable parameter information that varies the supply fee and the usage fee. In the information processing device, the supply information acquisition unit may receive and acquire the variable parameter information from a management device that manages the energy supply target. In the information processing device, the supply information acquisition unit may receive and acquire the variable parameter information from the energy supply target. In the information processing device, the supply information acquisition unit may receive and acquire the variable parameter information from an energy output device including the energy output unit. In the information processing device, the supply information acquisition unit may receive and acquire the use side identification information and the provider side identification information from a terminal device of the user.
[0006] A system according to yet another aspect of the present invention is a system for managing energy supply services, and includes the above-mentioned information processing device and a transmitting device that transmits energy supply information acquired by the supply information acquisition unit of the information processing device to the information processing device.
[0007] A method according to yet another aspect of the present invention is a method for managing an energy supply service, comprising: acquiring provider registration information including information of a provider who owns or manages an energy output unit that can be used for the energy supply service and information of the energy output unit; acquiring user registration information including information of a user who uses, owns or manages an energy supply target that can use energy supplied by the energy supply service and information of the energy supply target; storing the provider registration information in association with output unit identification information for identifying the energy output unit; storing the user registration information in association with supply target identification information that identifies the energy supply target and information of a mobile terminal device used by the user when using the energy supply service; At the same time, receiving from the user's mobile terminal device usage start information including the output unit identification information corresponding to the energy output unit that supplies energy to the energy supply target; acquiring energy supply information regarding the energy supply to the energy supply target of the user from the energy output unit of the provider when the energy supply service is used; referring to the stored information based on the energy supply information, and performing necessary processing for paying the provider a fee for the provision of the energy supply service from the energy output unit to the energy supply target; and referring to the stored information based on the energy supply information, and performing necessary processing for charging the user a usage fee for the energy supply service from the energy output unit to the energy supply target. Effect of the Invention
[0008] According to the present invention, it is possible to easily increase the number of energy output units capable of managing the provision of energy to energy supply targets and the use of energy by energy supply targets, and to easily expand the installation area. [Brief description of the drawings]
[0009] [Figure 1]1 is an explanatory diagram for explaining an entire service management system according to an embodiment; [Diagram 2] FIG. 2 is an explanatory diagram showing an example of the main configuration of the service management system. [Diagram 3] 5A to 5C are explanatory diagrams showing examples of images attached to the outlet of the embodiment. [Figure 4] FIG. 2 is a block diagram showing an example of a configuration of main functions of a service management server in the service management system. [Diagram 5] 11 is a flowchart showing an example of a service management process in the service management server. [Figure 6] FIG. 13 is an explanatory diagram showing an example of a main configuration of a service management system according to a modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. The system according to the present embodiment is a system that manages an energy supply service from an energy output unit to an energy supply target. The energy output unit is owned or managed by, for example, a provider that provides energy in the energy supply service. The supplied energy may be, for example, primary energy in the form of petroleum, natural gas, coal, etc., or secondary energy in the form of electricity, hydrogen, gasoline, light oil, heavy oil, city gas, alcohol, etc.
[0011] The energy supply target to which energy is supplied is, for example, an electric mobile body driven by a motor equipped with a battery. The mobile body may be a mobile body that moves on the ground, such as an electric vehicle or a fuel cell vehicle, a mobile body that moves in the air, such as a drone, or a mobile body such as a ship that moves on water, such as the sea. The mobile body may be a vehicle with four or more wheels, a tricycle, a two-wheeled vehicle (motorcycle, bicycle), a truck, a bus, a private car, or a business vehicle. The energy supply target is, for example, one that is used, owned, or managed by a user in an energy supply service. The energy supply target may be one that is leased from a leasing company, or one that is owned by a business operator different from the user. In addition, the energy supply target may be an electric device or an electronic device, such as a portable or fixed-type home appliance, an office device, or a communication terminal device.
[0012] In the following embodiment, as an example, a service management system will be described that manages a charging service (energy supply service) in which the supplied energy is electrical energy, the energy output unit that outputs the energy is an outlet that outputs electrical energy, the energy supply target to which the energy is supplied is a vehicle or a battery built into the vehicle, and the charging service charges the vehicle's battery with power output from the outlet.
[0013] FIG. 1 is an explanatory diagram showing a service management system 10 according to the present embodiment. This service management system 10 manages a charging service in which the batteries of vehicles are charged from an outlet 20 within the area of a parking lot 80 having parking spaces capable of parking a plurality of vehicles 30-1 to 30-3. The place where the vehicles 30-1 to 30-3 enter and exit the parking lot 80 is an entrance / exit 81. A gate device 82 is installed at the entrance / exit 81 of the parking lot 80.
[0014] Within parking lot 80, charging stands 25-1 to 25-5 equipped with outlets 20 are installed near each parking space. In the example of Fig. 1, five charging stands 25-1 to 25-5 are installed within parking lot 80, but the number of charging stands installed within the parking lot is arbitrary, and may be one or more.
[0015] The five charging stations 25-1 to 25-5 in the parking lot 80 receive power via power lines from power distribution equipment 210 of the same power company, which is the energy provider (step A), and the amount of power supply is measured by a single watt-hour meter 83 managed by the power company. Therefore, in this embodiment, the amount of power supply supplied from the five charging stations 25-1 to 25-5 cannot be measured separately for each charging station.
[0016] Furthermore, this watt-hour meter 83 measures the amount of power supply used not only by charging stations 25-1 to 25-5, but also by gate device 82 and various power utilization facilities 85 that use power. Therefore, in this embodiment, the configuration is such that it is not possible to distinguish between the amount of power supply at charging stations 25-1 to 25-5 and the amount of power supply at other power utilization facilities 82 and 85 and measure them separately.
[0017] The amount of power supply (power amount data) measured by the watt-hour meter 83 is sent to the power management device 200 of the power company (step B). For example, if the watt-hour meter 83 has a communication function like a smart meter, the power amount data is transmitted to the power management device 200 of the power company via a communication line.
[0018] The power utilization facilities (charging stations 25-1 to 25-5, gate device 82, power utilization facility 85) whose power supply amount is measured by watt-hour meter 83 are managed by the parking lot manager (the person who installed outlet 20) who is the provider. Therefore, the power fee (energy fee) for the amount of power supplied by the power company and used by these power utilization facilities 25-1 to 25-5, 82, 85 is paid by the parking lot manager to the power company (Step C).
[0019] The electricity fee paid by the parking lot manager to the electric power company can be covered by, for example, the parking fee collected by the parking lot manager from the parking lot users who use the parking lot. This electricity fee includes the fee for the amount of electricity supplied from the charging stations 25-1 to 25-5 to the vehicle 30-1, but the parking lot users who use the parking lot also include non-users who do not use the charging stations 25-1 to 25-5 (such as users of cars without charging functions). Furthermore, even among users who use the charging stations 25-1 to 25-5, the amount of electricity supplied from the charging stations usually differs. Therefore, it is unfair and undesirable for the parking lot users to uniformly add the electricity fee paid by the parking lot manager to the parking lot user's parking fee and collect it.
[0020] The service management system of this embodiment manages a charging service that collects a usage fee from users who receive power supply from charging stations 25-1 to 25-5 and pays a fee (supply fee) for the amount of power supplied to the user to the parking lot manager (provider). According to this service management system, the parking lot manager can cover the power fee for the amount of power supplied from charging stations 25-1 to 25-5, out of the power fee paid to the power company, with the supply fee paid for the charging service.
[0021] Furthermore, in the service management system of this embodiment, a usage fee according to the amount of power supplied from charging stations 25-1 to 25-5 is charged to the users who receive power from charging stations 25-1 to 25-5. Therefore, an appropriate usage fee according to the amount of power supplied to the users can be collected from the users of charging stations 25-1 to 25-5.
[0022] FIG. 2 is an explanatory diagram showing an example of the main configuration of the service management system 10 according to the present embodiment. 2, the service management system 10 manages the provision and use of power (charging service) to a supply target to which power is supplied from an outlet 20. The supply target in this embodiment is a vehicle 30 that is charged with power from the outlet 20, or a battery 31 of the vehicle 30. Power is supplied from the outlet 20 via, for example, a wired power cable 40 and a plug 41. Power may be supplied from the outlet 20 wirelessly, for example, by electromagnetic induction, power supply by radio waves such as microwaves, or power supply by light such as laser light. Furthermore, the voltage (current) supplied from the outlet 20 may be either AC or DC.
[0023] The service management system 10 includes a service management server 100 as an information processing device that manages the provision and use (charging service) of power (electrical energy). The service management server 100 may be configured as a single computer device, may be configured to link multiple computer devices, or may be configured as a cloud system on a network.
[0024] The outlet 20 as an energy output unit capable of outputting electric power (electrical energy) may be a general-purpose outlet with no particular use, or a dedicated outlet with a particular use. The outlet 20 may also be an outlet that is not limited to a particular user, or an outlet that is available only to a particular user.
[0025] 3(a) to 3(c) are explanatory diagrams each showing an example of an image attached to the outlet 20 of the present embodiment. 3(a) is provided with a code image (e.g., a QR code (registered trademark) image) 21. The code image 21 may be a one-dimensional code image or a two-dimensional code image. The code image 21 is an image in which information such as the name of the outlet 20, its identification number, its installation location, and the person who installed it (the parking lot manager) is encoded.
[0026] The outlet 20 in Fig. 3(b) is provided with an image of letters (e.g., handwritten letters) 22 as an auxiliary identification image for the outlet 20, arbitrarily added by the parking lot manager or the like. Moreover, the outlet 20 in Fig. 3(c) is provided with an image of an illustration 23 as an auxiliary identification image, arbitrarily added by the parking lot manager or the like. The letters 22 or illustration 23 may be attached to the outlet 20. The letters 22 and illustration 23 for the outlet 20 may be drawn on a sticker member 24 by the parking lot manager or the like and affixed to the side of the outlet 20. The auxiliary identification image may be a design or mark in addition to letters and illustrations.
[0027] A terminal device 51 of a user 50 who wishes to use power supplied from the outlet 20 can communicate with the service management server 100 via a communication network 60 such as a mobile communication network or the Internet. The terminal device 51 includes an operation unit such as keys, buttons, or a touch panel, a display unit such as a liquid crystal display, and an imaging unit such as a camera that captures an image of the outlet's code or an identification aid image. The terminal device 51 can start and execute a predetermined power usage application (power usage app) that is pre-installed when operated by a user. The terminal device 51 may include a current position acquisition unit such as a GNSS receiver that acquires information on its own current position. The terminal device 51 may be, for example, a mobile station (also referred to as a "mobile device" or "user equipment (UE)") that can communicate via a fourth-generation, fifth-generation or later-generation mobile communication network.
[0028] The vehicle 30 can communicate with the service management server 100 of the service management company and the vehicle management server 300 of the vehicle manufacturer through the communication network 60 by the external communication unit 32 of the in-vehicle device. Note that the external communication unit 32 may be provided with a communication unit for communicating with the service management server 100 and a communication unit for communicating with the vehicle management server 300 separately.
[0029] The external communication unit 32 may be, for example, a remote control unit (TCU: telematic control unit) connected to an in-vehicle network (CAN: controller area network) via a gateway. The remote control unit (TCU) may have a short-range wireless communication function such as wireless LAN or Bluetooth (registered trademark) in addition to a communication function via the communication network 60. In addition to the remote control unit (TCU), a battery management system (BMS) that manages the battery 31 and one or more electronic control units (ECUs) that control each of the other parts are connected to the in-vehicle network (CAN).
[0030] Next, the flow of a charging service managed by the service management system 10 according to this embodiment will be described. Power usage information (e.g., battery identification information, power amount, charging start time, charging end time), which is energy supply information related to power supply for charging the battery 31, is transmitted, for example, from a battery management system (BMS) via a remote control unit (TCU) to a vehicle management server 300 of a vehicle manufacturer (step 1). In addition, vehicle identification information, which is user side identification information of the side that uses power, is transmitted, for example, from an electronic control unit (ECU) having a memory that stores basic information of the vehicle to the vehicle management server 300 via the remote control unit (TCU). The transmission of these pieces of information to the vehicle management server 300 is executed, for example, based on a timing specified by the vehicle management server 300, or based on a transmission request generated by an application running on the terminal device 51. The transmission request from the terminal device 51 may be received by the vehicle remote control unit (TCU) via short-range wireless communication such as wireless LAN or Bluetooth (registered trademark). The vehicle manufacturer's vehicle management server 300 accumulates power usage information of the vehicle 30 in association with the identification information of the vehicle 30, and manages the latest power usage information in almost real time.
[0031] On the other hand, when the user 50 parks the vehicle 30-1 in the parking lot 80 and charges the battery of the vehicle 30-1 from the outlet 20 of the charging station 25-1, the user 50 executes an electric power usage app on the terminal device 51 and reads a code image (e.g., an image of a QR code (registered trademark)) 21 (see FIG. 3(a)) attached to the outlet 20. Then, the user 50 operates the terminal device 51 to transmit the read data of the code image 21, which is the provider identification information of the side that provides the electric power, and the user identification information from the terminal device 51. The user identification information includes, for example, the identification information of the user 50 or the terminal device 51, and the identification information of the supply target to which the electric power is supplied from the outlet 20 (e.g., the identification information of the vehicle 30 or the battery 31). These pieces of information are received by the terminal communication unit 101 of the service management server 100 via the communication network 60 (step 2).
[0032] The user identification information, such as the identification information of the user 50 or the terminal device 51 and the identification information of the supply target (for example, the identification information of the vehicle 30 or the battery 31), is, for example, registered in advance in an electricity usage app of the terminal device 51. The read data of the code image 21, which is the provider identification information, may be, for example, image data of the code image 21 captured by the camera of the terminal device 51, or may be data obtained by decoding the image data. Also, instead of the read data of the code image 21, the provider identification information may be the auxiliary identification image 22 or 23 (see FIG. 3 ( b ) and Figure 3 Alternatively, the read data (see (c)) and the position information of the terminal device 51 may be used. The position information of the terminal device 51 is, for example, the position information (latitude, longitude, altitude) of the terminal device 51 measured by a GNSS receiver of the terminal device 51.
[0033] Examples of the provider identification information are not limited to those described above. For example, an RF tag storing the identification information of the outlet 20 may be provided in the charging stand 25 equipped with the outlet 20. In this case, the user 50 executes an electricity usage app on the terminal device 51, wirelessly communicates with the RF tag, and acquires the identification information of the outlet 20 stored in the RF tag. The user 50 then operates the terminal device 51 to transmit the identification information of the outlet 20, which is the provider identification information, from the terminal device 51 to the service management server 100 via the communication network 60.
[0034] In this embodiment, the above-mentioned use side identification information and provider side identification information are transmitted from the terminal device 51 of the user 50 to the service management server 100 via the communication network 60, but this is not limited to this. For example, a communication device such as an IoT communication module may be incorporated in the charging stand 25 equipped with the outlet 20, and the communication device may communicate with the terminal device 51 of the user 50 via the communication network to obtain the use side identification information and provider side identification information from the terminal device 51, and transmit this information to the service management server 100 via the communication network.
[0035] Next, the service management server 100 of the service management company receives the read data of the code image 21 from the terminal device 51 of the user 50, and also acquires power usage information including supply amount information, which is variable parameter information as energy supply information, from the vehicle management server 300 of the vehicle manufacturer (step 3). The supply amount information is information on the amount of power supplied from the outlet 20 to the vehicle 30, which is the supply target of the user 50.
[0036] Then, the service management server 100 performs the necessary process (charging process) to collect the usage fee for the amount of power supply related to charging the vehicle 30-1 from the user 50 based on the supply amount information included in the acquired power usage information (step 4). This allows the service management company operating the charging service to collect the usage fee for the amount of power supply related to charging the vehicle 30-1 from the user 50 (step 6).
[0037] The billing process (processing necessary for billing) performed by the service management server 100 is at least a part of a series of processes (including any known billing process) necessary to collect a usage fee for the amount of power supply related to charging the vehicle 30-1 from the user 50 based on the acquired supply amount information. Specific examples include processes including, for example, a process of calculating a usage fee for the amount of power supply related to charging the vehicle 30-1 from the acquired supply amount information, a process of taking procedures to bill the user for the usage fee, and a process of providing at least one of the supply amount information and the usage fee information to a management device managed by another business that collects the usage fee from the user.
[0038] Furthermore, when the service management server 100 receives the read data of the code image 21 from the terminal device 51 of the user 50 based on the acquired supply amount information, the service management server 100 performs the process required to pay the fee for the amount of power supply related to charging the vehicle 30-1 to the parking lot manager (preparation process for payment of the supply fee) (step 5). This allows the service management company operating the charging service to pay the fee for the amount of power supply related to charging the vehicle 30-1 to the parking lot manager (step 7).
[0039] The payment process (processing necessary for payment) performed by the service management server 100 is at least a part of a series of processes (including any known payment process) necessary to pay the parking lot manager a fee for the amount of power supply related to charging the vehicle 30-1 based on the acquired supply amount information. Specific examples include processes including, for example, a process of calculating a fee for the amount of power supply related to charging the vehicle 30-1 from the acquired supply amount information, a process of making a procedure for paying the fee to the parking lot manager (provider), and a process of providing at least one of the supply amount information and the information on the fee to a management device managed by another business that pays the fee to the parking lot manager.
[0040] In this embodiment, supply amount information on the amount of power supply (amount of energy supply) supplied from the outlet 20 (energy output unit) to the battery 31 (energy supply target) of the vehicle 30 is used as variable parameter information for varying the supply fee and the usage fee, but the present invention is not limited to this. For example, when the supply fee and the usage fee are varied according to the charging time (charging end time-charging start time), information on the charging time can be used as the variable parameter information. In this case, since there is no need for a detection unit for detecting the amount of power supply during charging, a service management system can be provided with a simple configuration.
[0041] Furthermore, for example, there is a mixture of outlets 20 that have different power supply speeds (amount of power supplied per unit time) to the vehicle 30. That is, some outlets 20 are capable of rapid charging, which is a faster power supply speed than the other outlets 20. In such a case, the supply fee and usage fee may be varied depending on the difference in the power supply speed (energy supply speed) during charging (for example, whether or not rapid charging is performed), and in this case, information on the power supply speed (amount of power supplied per unit time) can be used as variable parameter information.
[0042] In this case, inequalities between users due to differences in power supply speed (whether charging can be completed in a short time, etc.) can be corrected, and a charging service that gives a sense of equality to users can be provided. In addition, inequalities between parking lot managers due to differences in power supply speed (whether or not they use a quick-charging outlet that requires a large capital investment, etc.) can also be corrected, and a charging service that gives a sense of equality to parking lot managers can be provided. In particular, a path to appropriate investment recovery can be created for parking lot managers who have made large capital investments in outlets 20 that allow quick charging.
[0043] The power supply speed may differ depending on the configuration of the vehicle 30 or battery 31 to which the energy is supplied. Specifically, the power supply speed may differ depending on the vehicle's AC power consumption rate (electricity cost), battery capacity, remaining battery power, battery deterioration level (such as the mileage of the vehicle 30 or the period of use of the battery 31), charging efficiency, vehicle location (the area where the vehicle 30 charges), and, in the case of a plug-in hybrid vehicle, the remaining amount of gasoline. Therefore, this information may be acquired as variable parameter information to grasp the difference in the power supply speed, and the usage fee to be charged to the user and the supply fee to be paid to the parking lot manager may be calculated. Note that this information can be obtained, for example, by acquiring information on the type of the vehicle 30 (energy supply target) described later.
[0044] Furthermore, for example, the outlets 20 may include a mixture of outlets using different types of methods for generating the power (energy) to be output. These types include, for example, types recommended by national energy policies and types with low generation costs. In this way, when the outlets 20 include a mixture of outlets using different types of methods for generating the power (energy), the supply fee and usage fee may be varied depending on the type of power (energy) generation method, and in this case, information on the type of power (energy) generation method may be used as variable parameter information.
[0045] A specific example of the type of the generation method of the output power (energy) is whether the power source that generates the power is a type that generates power from fossil fuels such as oil and coal, or a type that generates power from natural energy such as wind power, solar power, and biomass (biological resources). In addition, the types of these fossil fuels and natural energy may be further differentiated (for example, in the case of natural energy, the types are differentiated into wind power, solar power, and biomass (biological resources)). The type can be determined, for example, by the presence or absence of a certificate (such as a green power certificate) issued by a specified certification organization. The type of the generation method of the output power (energy) is not limited to the type of power source, and may also be differentiated by the amount of CO2 (carbon dioxide) generated in the power generation process.
[0046] The type of power generation method corresponding to each outlet 20 can be associated in advance with each outlet 20, for example, based on an application by the parking lot manager. Specifically, information on the type of power generation method corresponding to the outlet 20 (for example, information on the presence or absence of a green power certificate) is stored in the storage unit 104 of the service management server 100 in association with provider identification information such as identification information of the outlet 20.
[0047] Also, for example, the outlet 20 in the system of this embodiment may have a different type of vehicle 30 (energy supply target) that receives the supply of power output from the outlet 20. The type may include, for example, the manufacturer and model of the vehicle 30, or the manufacturer and model of the battery 31 mounted on the vehicle 30. In this way, when the type of the vehicle 30 is different, the power supply speed may be different, or the cost for power supply (the facility cost of the outlet 20) may be different. In such a case, the supply fee and the usage fee may be changed depending on the type of the vehicle 30 (energy supply target) that receives the power supply, and at this time, information on the type of the vehicle 30 (energy supply target) can be used as variable parameter information. Note that the type of the vehicle 30 that receives the power supply from each outlet 20 can be determined by the service management server 100, for example, based on the vehicle identification information of the vehicle 30 transmitted from the external communication unit 32 of the vehicle 30.
[0048] FIG. 4 is a block diagram showing an example of a configuration of main functions of the service management server 100 according to the embodiment. In FIG. 4, the service management server 100 includes a terminal communication unit 101 and a server communication unit 102 as supply information acquisition units, a management processing unit 103, a storage unit (DB: database) 104, a charging processing unit 105, and a payment processing unit 106.
[0049] The terminal communication unit 101 communicates with the terminal device 51 of the user 50 via the communication network 60. The terminal communication unit 101 receives, for example, read data of the code image 21 transmitted from the terminal device 51, identification information of the user 50 or the terminal device 51, and identification information of a supply target to which power is supplied from the outlet 20 (for example, identification information of the vehicle 30 or the battery 31).
[0050] The read data of the code image 21 functions as identification information (provider identification information) of the parking lot manager who is the provider of the outlet 20 that supplied power to the vehicle 30 of the user 50, and the identification information of the user 50 or the terminal device 51 and the identification information of the supply target (for example, the identification information of the vehicle 30 or the battery 31) function as user identification information. Therefore, the terminal communication unit 101 functions as a supply information acquisition unit.
[0051] The server communication unit 102 communicates with the vehicle management server 300 of the vehicle manufacturer to which the target vehicle 30 is registered, via the communication network 60. The server communication unit 102 receives, for example, from the vehicle management server 300 via the communication network 60, at least supply amount information (variable parameter information) of the power usage information of the vehicle 30 stored in the vehicle management server 300.
[0052] The terminal communication unit 101 and the server communication unit 102 may be configured as an integrated communication device (for example, a mobile communication module).
[0053] The management processing unit 103 performs at least one of authentication of the user using the electricity (user authentication) and authentication of the supply target (e.g., vehicle 30 or battery 31) (supply target authentication) based on identification information of the user 50 or terminal device 51 and identification information of the supply target (e.g., identification information of the vehicle 30 or battery 31).
[0054] For example, the management processing unit 103 performs user authentication to confirm whether the user 50 is a legitimate user pre-registered in the service management system of this embodiment by comparing the identification information (user ID) of the user 50 received from the terminal device 51 with the identification information (user ID) of the user pre-registered in the service management server 100. In this case, if the user is a legitimate user, the use of the charging service may be permitted, and if the user is not a legitimate user, the use of the charging service may be restricted (for example, not permitted).
[0055] Also, for example, the management processing unit 103 may perform supply target authentication to confirm whether the supply target (e.g., the vehicle 30 or the battery 31) is a genuine supply target pre-registered in the service management system of this embodiment by comparing the identification information of the supply target (e.g., the identification information of the vehicle 30 or the battery 31) received from the terminal device 51 with the identification information of the supply target pre-registered in the service management server 100 (e.g., the identification information of the vehicle 30 or the battery 31). In this case, if the supply target is a genuine supply target, use of the charging service may be permitted, and if the supply target is not a genuine supply target, use of the charging service may be restricted (e.g., not permitted).
[0056] In addition, based on the identification information of the supply target (e.g., identification information of the vehicle 30 or the battery 31) received from the terminal device 51, the management processing unit 103 receives and acquires supply amount information of the supply target from the vehicle management server 300 of the vehicle manufacturer via the server communication unit 102 (step 3).
[0057] As described above, the supply amount information is information relating to the amount of electricity supplied from the outlet 20 to the vehicle 30 that is the supply target of the user 50. The supply amount information may be any information that can identify the amount of electricity supplied from the outlet 20 to the vehicle 30 that is the supply target of the user 50. In this embodiment, this supply amount information is included in the electricity usage information transmitted from the vehicle 30 to the vehicle management server 300, and is stored in the vehicle management server 300.
[0058] A specific example of supply amount information is, for example, information that can be detected by a detection unit 33 provided in the vehicle 30, and if the information corresponds to the amount of electricity (power supply amount) supplied from the outlet 20 and used to charge the battery 31, the detected information can be used as supply amount information.
[0059] Also, for example, if the detector 33 provided in the vehicle 30 can detect the remaining power of the battery 31, the information on the detected remaining power may be used as the supply amount information. In this case, for example, by subtracting the remaining power before charging from the remaining power after charging, the amount of power supplied from the outlet 20 and used to charge the battery 31 (power supply amount) can be obtained.
[0060] Furthermore, since many electric vehicles are equipped with a detection unit 33 that detects the state of charge (SoC) of the battery 31, the SoC data may be used as supply amount information. In this case, if the full charge capacity of the battery 31 is not known, it is not possible to ascertain the remaining power of the battery 31 from the SoC data. However, by storing a correspondence between the identification information of the battery 31 and the full charge capacity in the storage unit (DB) 104, it is possible to identify the full charge capacity from the identification information of the battery 31 and calculate the remaining power of the battery 31 from the SoC data of the battery 31.
[0061] The storage unit (DB) 104 stores information and data necessary for various processes performed by the service management server 100. Specifically, the read data of the code image as output unit identification information received by the terminal communication unit 101, the identification information of the user 50 or the terminal device 51, and the identification information of the supply target, and the supply amount information received by the server communication unit 102 are stored in association with each other. For example, as shown in Table 1, for each series of electricity usage transactions, one record is stored in which an outlet ID, a user ID, a terminal ID (e.g., IMEI), a vehicle ID, and an amount of electricity supply are associated with each other, and an electricity usage transaction table (electricity usage ledger) is formed as a whole.
[0062] [Table 1]
[0063] Moreover, the storage unit (DB) 104 stores various tables used for managing charging services via a plurality of outlets. For example, the storage unit (DB) 104 stores an outlet management table of Table 2, a user management table of Table 3, and a vehicle management table of Table 4. Note that Table 2 may be an example in which the read data of the identification auxiliary image 22 or 23 attached to the outlet 20 and the location information of the terminal device 51 are used instead of the read data of the code image 21. The storage unit (DB) 104 may further store an installer (provider) management table for managing an installer (provider) of the outlet 20, such as a parking lot manager. In the installer (provider) management table, for example, information such as the name or appellation and address of the installer (provider) is recorded using an installer ID as a key.
[0064] [Table 2]
[0065] [Table 3]
[0066] [Table 4]
[0067] New records are added to the outlet management table, user management table and vehicle management table, respectively, when a new outlet 20, user 50 (terminal device 51) and vehicle 30 (battery 31) for using the charging service provided by the service management server 100 of this embodiment are newly registered.
[0068] The storage unit (DB) 104 also stores a payment processing table in which provider information, such as an installer ID (identification information of the parking lot manager) and information (such as a payee's account number) used in a process (payment process) required to pay the parking lot manager a fee for the amount of power supply, is associated with information on the energy output unit, such as the name of the corresponding outlet and read data of a code image. A record is added to this payment processing table when a new installer (provider) of the outlet 20 is registered. By linking and referring to the payment processing table and the various tables described above, the charging service of this embodiment can perform a payment process for the amount of power supply to the installer (parking lot manager).
[0069] The storage unit (DB) 104 may also store a billing processing table in which user information, such as a user ID and information (such as billing information for the usage fee) used in processing required to collect a usage fee for the amount of power supply for charging the user's vehicle 30 (billing processing), is associated with information on the energy supply target related to the vehicle, battery, etc. A record is added to this billing processing table when a user 50 is newly registered in the charging service of this embodiment. By linking and referring to the billing processing table and the various tables described above, the charging service of this embodiment can perform billing processing for the amount of power supply to the user.
[0070] For example, when SoC data is used as the supply amount information, a battery information table indicating the correspondence between the identification information of the battery 31 and the full charge capacity is stored in the storage unit (DB) 104.
[0071] FIG. 5 is a flowchart showing an example of the service management process in the service management server 100 according to this embodiment. In FIG. 5, the service management process of this embodiment includes a preparation phase (S100) and an operation phase (S200).
[0072] In the advance preparation phase (S100), when an installer (provider) of the outlet 20, such as a parking lot manager, applies for the outlet registration for the charging service, the service management server 100 acquires and stores information about the application. For example, when an operator inputs data about the outlet 20 of the installer (parking lot manager), the service management server 100 creates the outlet management table of Table 2 and the payment processing table described above (S101). Specifically, when the above-mentioned outlet registration application is made, the operator inputs provider registration information including information about the provider and information about the energy output unit using an input device (provider registration information acquisition unit) such as a keyboard or touch panel for inputting data to the service management server 100. As a result, the service management server 100 stores in the database of the storage unit 104 a table that associates the provider registration information inputted via the input device with output unit identification information (such as an outlet ID) for identifying the energy output unit. By managing such a table, it is possible to perform appropriate payment processing for a supply fee according to the amount of power supplied from each of the outlets 20 (energy output units) for a plurality of providers.
[0073] The provider registration information acquisition unit in the service management server 100 may be configured to receive and acquire provider registration information transmitted from a terminal device of the provider via a communication network, instead of data input by an operator.
[0074] Furthermore, when a user 50 who uses a charging service (energy supply service) applies for use of the charging service using the terminal device 51, the service management server 100 receives and acquires new registration data (user-side registration information) including information on the user 50 and the terminal device 51 (user information) and information on the supply target (vehicle 30 and battery 31) (information on the energy supply target) from the terminal device 51. The terminal communication unit 101 that receives this new registration data functions as a provider-side registration information acquisition unit.
[0075] In the service management server 100, a table that associates the received user side registration information, supply target identification information (vehicle ID and battery ID) that identifies the energy supply target, and information (terminal ID) of the mobile terminal device used by the user when using the charging service is stored in the database of the storage unit 104. As a result, the user management table of Table 3, the vehicle management table of Table 4, and the above-mentioned billing processing table are created (S102).
[0076] Next, in the operation phase (S200), when the user 50 receives power supply from the registered outlet 20 to charge the battery 31 of the vehicle 30, first, the user operates the terminal device 51 to start an application (power use application) for using the charging service. Then, the terminal device 51 captures and reads the code image 21 including the identification information of the outlet 20, and selects "my car" from the menu selection displayed on the display screen of the terminal device 51. By this operation, the identification information of the user 50 (or the terminal device 51), the read data of the code image 21, and the identification information of the vehicle 30 (or the battery 31) preregistered in the terminal device 51 as "my car" are transmitted from the terminal device 51 to the service management server 100. As a result, the service management server 100 receives the identification information of the user 50 (or the terminal device 51), the read data of the code image 21, and the identification information of the vehicle 30 (or the battery 31) from the terminal device 51 of the user 50 (S201).
[0077] Next, the service management server 100 performs authentication processing for the combination of the identification information of the user 50 (or terminal device 51) and the vehicle 30 (or battery 31) based on the identification information of the user 50 (or terminal device 51) and the identification information of the vehicle 30 (or battery 31) received from the terminal device 51 (S202).
[0078] After completing the authentication process, the service management server 100 requests the vehicle management server 300 to provide SoC data (supply amount information) for the vehicle 30 based on the received identification information of the user 50 (or the terminal device 51) and identification information of the vehicle 30 (or the battery 31). As a result, the service management server 100 obtains the latest supply amount information (SoC data before charging) for the vehicle 30 from the vehicle management server 300 via the communication network 60 (S203).
[0079] Thereafter, the battery 31 of the vehicle 30 is charged with the power supplied from the outlet 20, and when charging is completed, the vehicle 30 transmits, either in response to a request from the terminal device 51 of the user 50 or autonomously, to the vehicle management server 300, information on the power usage (e.g., battery identification information, amount of power (SoC data), charging start time, charging end time) of the power supplied from the outlet 20 and used to charge the battery 31 of the vehicle 30. As a result, the SoC data after charging is registered in the vehicle management server 300.
[0080] Furthermore, when charging is completed, a charging completion notification including the identification information of the user 50 (or the terminal device 51) and the identification information of the vehicle 30 (or the battery 31) is transmitted from the user's terminal device 51 to the service management server 100. Upon receiving the charging completion notification, the service management server 100 requests the vehicle management server 300 to provide SoC data (supply amount information) for the vehicle 30 based on the identification information of the user 50 (or the terminal device 51) and the identification information of the vehicle 30 (or the battery 31). As a result, the service management server 100 obtains the latest supply amount information (post-charging SoC data) for the vehicle 30 from the vehicle management server 300 via the communication network 60 (S204).
[0081] In this way, the service management server 100 receives the SoC data before charging and the SoC data after charging, and refers to the battery information table in the storage unit (DB) 104 to obtain the full charge capacity of the battery 31. Then, it calculates the remaining power of the battery 31 before charging from the SoC data before charging and the full charge capacity, and calculates the remaining power of the battery 31 after charging from the SoC data after charging and the full charge capacity. Then, it subtracts the remaining power before charging from the remaining power after charging to calculate the amount of power supply used in this charging (S205).
[0082] Next, the service management server 100 refers to the outlet management table of Table 2 described above based on the read data of the code image, and identifies the identification information of the outlet 20. Furthermore, the service management server 100 stores the identification information (outlet ID) of the outlet 20, the identification information (user ID, terminal ID) of the user 50 or terminal device 51, the identification information of the supply target (vehicle ID or battery ID), and the current charging amount (amount of power supply) calculated in processing step S205 in association with each other in the storage unit (DB) 104 so as to be added to the power usage transaction table (power usage ledger) of Table 1 described above (S206).
[0083] The service management server 100 can manage the charging service that accompanies the supply of power via an outlet by referring to an electricity usage transaction table (electricity usage ledger) such as that shown in Table 1.
[0084] In this embodiment, the service management server 100 refers to the power usage transaction table (power usage ledger) to perform the necessary processing (billing processing) for charging at least one of the user 50, the supply target (vehicle 30 or battery 31) and the terminal device 51 for the usage fee for power usage by the vehicle 30 via the outlet 20 (S207). In this billing processing, for example, the total amount of power supply to each user in a predetermined period (e.g., one month) is calculated, and this is multiplied by the unit price of the usage fee to calculate the usage fee to be collected from each user. Then, the billing processing table in the memory unit 104 is referred to to perform the necessary billing processing for collecting the usage fee from each user.
[0085] At this time, the usage fee may be calculated taking into account variable parameter information other than the supply amount information (information on charging time (charging end time-charging start time), information on power supply speed (amount of power supplied per unit time), information on the type of power (energy) generation method, information on the type of vehicle 30 (energy supply target), etc.).
[0086] There are no particular limitations on the method of collecting the usage fee from the user, so long as the usage fee is collected according to the amount of power supplied from the outlet 20 to the user's vehicle 30. For example, a completely pay-per-use system may be used, or a flat-rate system in which a fixed fee is charged up to a specified amount of power supply. The business that collects the usage fee from the user may be a service management business that operates the service management server 100, or may be another business that collects the usage fee under a contract from the service management business.
[0087] Furthermore, in this embodiment, the service management server 100 refers to the power usage transaction table (power usage ledger) to perform the necessary processing (payment processing) to pay the installer of the outlet 20 (parking lot manager) the supply fee for power supply to the vehicle 30 via that outlet 20 (S208). In this payment processing, for example, the total amount of power supply corresponding to the outlet 20 of each installer in a predetermined period (e.g., one month) is calculated, and this is multiplied by the unit price of the supply fee to calculate the supply fee to be paid to each installer. Then, the service management server 100 refers to the payment processing table in the storage unit 104 to perform the necessary payment processing to pay the supply fee to each installer.
[0088] At this time, the supply fee may be calculated taking into account variable parameter information other than the supply amount information (such as information on charging time (charging end time - charging start time), information on power supply speed (amount of power supplied per unit time), information on the type of power (energy) generation method, and information on the type of vehicle 30 (energy supply target)).
[0089] As described above, in this embodiment, the service management server 100 performs, by the billing processing unit 105, a billing process required for billing the user 50 for the electricity usage fee calculated from the supply amount information (variable parameter information) received by the server communication unit 102. This allows the service management company operating the service management server 100 to provide a service of collecting an appropriate usage fee according to the amount of power received (power supply amount) from the user 50 who receives power supply from the outlet 20, which is an energy output unit registered in the charging service (energy supply service) of this embodiment.
[0090] Furthermore, in this embodiment, the service management server 100 performs a payment process required for paying the power supply fee, calculated from the supply amount information (variable parameter information) received by the server communication unit 102, to the parking lot manager, who is the provider, by the payment processing unit 106. This allows the service management company that operates the service management server 100 to provide a charging service (energy supply service) that allows the parking lot manager to receive an appropriate supply fee according to the amount of power supplied from the outlet 20 (power supply amount).
[0091] Furthermore, in this embodiment, as described above, the outlet 20 as the energy output unit may be a shared outlet (such as a general-purpose outlet) that can be used not only by predetermined specific users (users registered with the charging service) but also by unspecified general users (users not registered with the charging service (energy supply service) of this embodiment). Using such a shared outlet as the energy output unit of the service management system of this embodiment makes the procedures for obtaining permission for installation easier than when an outlet that can only be used by specific users is installed, and contributes to an increase in the number of energy output units that can be used in the charging service (energy supply service) and an expansion of the installation area.
[0092] However, a shared outlet is usually equipped with a watt-hour meter that detects the amount of power supplied from the outlet, but such a detection unit detects the amount of power supplied from the outlet collectively without distinguishing between users. Therefore, a system that detects the amount of power supplied from the outlet using a detection unit provided on the shared outlet side cannot detect the amount of power supplied by distinguishing specific users from general users, making it difficult to manage the supply and use of power (energy) provided to and used by specific users. Therefore, when using a shared outlet, it is necessary to understand the amount of power supplied from the outlet to specific users separately from that of general users.
[0093] According to this embodiment, the amount of power supplied from the outlet 20 to the vehicle 30 of the user 50 is grasped based on the supply amount information detected by the detection unit 33 provided in the vehicle 30. Therefore, even when a shared outlet is used, the amount of power supplied from the outlet 20 to the vehicle 30 of the user 50 (a specific user) can be grasped separately from other users (general users, etc.). Moreover, in this case, the installer of the shared outlet (parking lot manager, etc.) does not need to newly install equipment for detecting the amount of power supplied from the outlet to the specific user separately from other users (general users, etc.). Therefore, for the parking lot manager, even when a shared outlet is used in the charging service (energy supply service), the equipment cost (introduction cost) can be kept low.
[0094] In addition, in this embodiment, the use of outlets (energy output units) installed in common areas such as the common area of an apartment building or a parking lot of a shopping center as outlets (energy output units) that can be used in the charging service (energy supply service) contributes to an increase in the number of outlets (energy output units) that can be used in the charging service (energy supply service) of this embodiment and an expansion of the installation area. However, such common areas are often provided with a detection unit that detects the supply amount information of the power (energy) supplied within the common area, but such a detection unit detects the total amount of the supply amount of the power supplied within the common area. Therefore, it is difficult for the detection unit provided in the common area to grasp only the power supply amount supplied from the outlets installed in such a common area.
[0095] In this embodiment as well, the amount of electricity in the parking lot 80, which is a shared area including the outlet 20, the gate device 82, and various power utilization facilities 85, i.e., the total amount of the electricity supply amount supplied from the outlet 20 to the vehicle 30 of the user 50 and the other electricity supplies supplied to the gate device 82 and various power utilization facilities 85, is collectively measured by the power meter 83. The parking lot manager then pays the power fee according to this total amount to the power company. In this case, in order for the service management company to pay the parking lot manager (provider) a fee for the amount of electricity supplied from the outlet 20 to the vehicle 30 of the user 50, it is necessary for the service management company to grasp only the amount of electricity supplied from the outlet 20 to the vehicle 30 of the user 50, separately from the power meter 83.
[0096] According to this embodiment, power supply information (energy supply information) regarding the power supply supplied from the outlet 20 to the vehicle 30 of the user 50 is grasped based on power usage information (e.g., battery identification information, power amount, charging start time, charging end time) detected by the detection unit 33 provided in the vehicle 30. Therefore, even if only equipment (power meter 83) for collectively measuring the power amount of the parking lot 80 including the outlet 20, the gate device 82, and various power usage equipment 85 is provided, the amount of power supply supplied from the outlet 20 to the vehicle 30 of the user 50 can be grasped. Therefore, in this embodiment, the parking lot manager does not need to newly install equipment for detecting the amount of power supply supplied from the outlet 20 to the vehicle 30 of the user 50 when receiving the supply fee for the power used by the user 50 who received the power supply from the outlet 20. Therefore, the equipment cost (introduction cost) can be kept low for the parking lot manager when registering as an energy provider of the charging service (energy supply service).
[0097] Furthermore, the parking lot manager is not required to go through the complicated procedures to install the new equipment described above, and registration as an energy provider for the charging service (energy supply service) is promoted. For example, if the parking lot 80 is a common area of a condominium and the parking lot manager is the condominium management association, installing the new equipment described above in the common area requires procedures such as obtaining consent from many of the condominium owners, which is a very complicated procedure. According to this embodiment, such complicated procedures are not required, and therefore registration of the shared outlet 20 provided in the common area of the condominium as an outlet (energy output unit) for the charging service (energy supply service) is promoted.
[0098] Moreover, according to the service management system of this embodiment, the collection (billing) of the usage fee from the user and the payment of the provision fee to the provider (parking lot manager) are performed by the service management company that operates the charging service (energy supply service). Therefore, the provider (parking lot manager) does not need to prepare and manage the facilities necessary for collecting the usage fee from the user, or perform the necessary billing process, and the charging service (energy supply service) provided by the service management system of this embodiment is highly convenient for the parking lot manager. Therefore, since the provider (parking lot manager) can easily register as a provider, it is expected that the number of providers (parking lot manager) who register for the charging service (energy supply service) will increase, which will promote an increase in the number of energy output units (outlets 20) available to users and an expansion of the installation areas.
[0099] Moreover, the detection unit 33 that detects power usage information (for example, SoC data, battery identification information, power amount, charging start time, charging end time) for grasping power supply information (power supply amount) related to the power supply supplied from the outlet 20 to the vehicle 30 of the user 50 is equipment that is provided in most existing vehicles (energy supply target) 30. Therefore, the user 50 does not bear the cost burden of the detection unit 33.
[0100] Furthermore, in recent years, various information including power usage information (e.g., SoC data, battery identification information, power amount, charging start time, charging end time) detected by the detection unit 33 provided in the vehicle 30 is accumulated in the vehicle management server 300 of each vehicle manufacturer and used for various vehicle services. The service management server 100 of this embodiment does not acquire the power usage information detected by the detection unit 33 provided in the vehicle 30 from each vehicle 30 individually, but acquires the information from the vehicle management server 300 of the vehicle manufacturer. In this way, the service management server 100 can acquire the power usage information detected by the detection unit 33 provided in the vehicle 30 using existing devices and facilities, so there is no need to newly install devices for transmitting power usage information to the service management server 100 in each vehicle 30 of each user 50. This further reduces the cost burden on the user 50.
[0101] On the other hand, since it is assumed that there may be users who do not use a service in which power usage information detected by the detection unit 33 provided in the vehicle 30 is accumulated in the vehicle manufacturer's vehicle management server 300, a device that transmits power usage information to the service management server 100 may be newly installed in the vehicle 30 of the user 50. In this case, for example, a communication device serving as a transmitter that can obtain supply amount information (SoC data, etc.) detected by the detection unit 33 of the vehicle 30 and transmit it to the service management server 100 may be connected to an OBD2 (On Board Diagnosis second generation) connector provided in the vehicle 30.
[0102] In the present embodiment, the service management server 100 receives and acquires, as the supply target identification information, the identification information of the user 50 or the terminal device 51, and the identification information of the vehicle 30 that is the supply target to which power is supplied from the outlet 20, from the terminal device 51 of the user 50. However, the supply identification information may be acquired by other methods. For example, the gate device 82 installed at the entrance / exit of the parking lot 80 may be provided with a function for acquiring the identification information of the vehicle 30 entering / exiting the parking lot 80, and the service management server 100 may receive the identification information of the vehicle 30 as the supply target identification information from the gate device 82. In this case, for example, the license plate (vehicle registration number plate) of the vehicle 30 passing through the entrance / exit may be captured by an imaging device such as a camera installed in the gate device 82, and the vehicle registration number of the vehicle 30 recognized from the captured image may be acquired as the identification information. In addition, the identification information of the vehicle may be acquired from an on-board ETC (Electronic Toll Collection System) device installed in the vehicle.
[0103] In the above-described embodiment, information such as user identification information and provider identification information is transmitted to the service management server 100 using the terminal device 51 of the user 50, but the external communication unit 32 mounted on the vehicle 30 may be used instead of the terminal device 51. Also, in the above-described embodiment, information such as power usage information (power supply information) is transmitted using the external communication unit 32 mounted on the vehicle 30, but the terminal device 51 of the user 50 may be used instead of such an in-vehicle external communication unit 32.
[0104] In addition, the above-mentioned usage fee charged to the user and the supply fee paid to the provider such as the parking lot manager may be calculated by adding other variable parameter information instead of or in addition to the power usage information (power supply information). For example, even if the amount of power supply is the same, the usage fee or supply fee may be changed according to other variable parameter information. In addition to the above, examples of this variable parameter information include attributes of users (differences in fees paid for services, differences in service grades, differences in ages of users, differences in regions to which users belong, etc.) and attributes of the vehicle 30 to which energy is supplied (differences in vehicle manufacturers, differences in additional services related to the vehicle 30, etc.). In addition, examples of the variable parameter information include information on the type of energy output from the energy output unit (differences in energy sources, whether it is designated clean energy, etc.) and the type of energy output unit (differences in the supply speed of energy supplied from the energy output unit of the provider to the energy supply target of the user (rapid charging or not), etc.).
[0105] [Modifications] Next, a modification of the service management system in the above-described embodiment will be described. In the following description, differences from the above-described embodiment will be mainly described, and descriptions similar to those of the above-described embodiment will be omitted.
[0106] FIG. 6 is an explanatory diagram showing an example of a main configuration of a service management system according to this modified example. In the management system of this modified example, a detector for detecting supply amount information is installed in an electric power output device 400 serving as an energy output device including an outlet 20 serving as an energy output unit. Like the charging stand 25 of the above-described embodiment, this electric power output device 400 receives electric power supply from a power distribution facility 210 of an electric power company via a power line. The electric power output device 400 of this embodiment also functions as a power supply control device for controlling the supply of electric power to a battery 31 of a vehicle 30 via the outlet 20.
[0107] The power output device 400 includes a general-purpose plug 402 that is connected to a general-purpose outlet 26 on the power distribution facility 210 side (the power meter 83 side) shown in Fig. 1. The power output device 400 also includes an outlet 20 as an energy output unit, and can supply power to a battery 31 of a vehicle 30 by inserting a plug 41 into the outlet 20 for connection.
[0108] The power output device 400 also includes a switch unit 410 as an opening / closing means for opening and closing the path of power supply from the outlet 20 to the battery 31, a control unit 420 as a control means for controlling the switch unit 410, a network communication unit 430 as a communication means for communicating with the service management server 100 etc. via the communication network 60, and a power amount measuring unit 440 as a detection unit for detecting the amount of power supply during charging.
[0109] The switch section 410 can be configured, for example, by a switch having a normally open type relay contact.
[0110] The control unit 420 may be configured, for example, as a general-purpose microcomputer including a CPU or a dedicated IC circuit element. The control unit 420 may also be configured to include a storage unit as a storage means including a semiconductor memory such as a RAM or a ROM, a magnetic disk, and the like, to read out a predetermined program stored in the storage unit, and to execute transmission and reception processing of data and commands, data processing for user authentication, control of the switch unit, and the like according to the program. The control unit 420 may also be configured of a first control unit connected to the switch unit 410, and a second control unit controlled by the service management server 100 via the communication network 60. In this case, the first control unit and the second control unit are controlled, for example, via an API (Application Programming Interface).
[0111] The control unit 420 includes a timer as a timekeeping means. For example, when the timer receives an authentication result indicating that the authentication process has been successful from the service management server 100 or when the timer receives a connection request from the terminal device 51 via the communication network 60, the timer presets the usage time included in the connection request, controls the switch unit 410 to turn ON (relay closed), and starts the timer function at the same time as the start of power supply to the battery 31. Then, when the usage time expires and the time is up, the control unit 420 outputs a time-up signal. Based on this time-up signal, the control unit 420 controls the switch unit 410 to turn OFF (relay open), and ends power supply to the battery 31. The control unit 420 may also perform the authentication process performed by the service management server 100.
[0112] The network communication unit 430 functions as a transmission unit that transmits provider identification information such as an outlet ID and supply amount information (variable parameter information) such as the amount of power output from the outlet 20 to the battery 31 of the vehicle 30 to the service management server 100 or the like via the communication network 60. The network communication unit 430 may be configured to communicate via a wired communication line such as an optical line, or may be configured using a wireless communication module to communicate via a wireless communication line. The communication via a wireless communication line may be, for example, communication via a cellular mobile communication network such as the fourth or fifth generation, or communication via a wireless LAN such as WiFi.
[0113] The power amount measuring unit 440 functions as a detection unit that detects the amount of power (power supply amount) used to charge the battery 31 from the outlet 20. For example, an induction type watt-hour meter or an electronic watt-hour meter can be used as the power amount measuring unit 440. The power usage information (power supply information) detected by the power amount measuring unit 440 is sent to the control unit 420, and the control unit 420 transmits the power usage information (power supply information) from the network communication unit 430 to the service management server 100 via the communication network 60 at a predetermined timing.
[0114] In this modification, the service management server 100 can directly acquire, from the power output device 400, power usage information (power supply information) required for calculating the usage fee to be charged to the user 50 and the supply fee to be paid to the parking lot manager. Therefore, even without acquiring SoC data from the vehicle manufacturer's vehicle management server 300, it is possible to appropriately calculate the usage fee and supply fee according to the amount of power supplied from the outlet 20 to the battery 31. Therefore, according to this modification, as a result of not needing to cooperate with the vehicle manufacturer's vehicle management server 300, it is possible to provide a charging service that is easy to use even for users who do not use a service in which vehicle information such as power usage information is accumulated in the vehicle manufacturer's vehicle management server 300.
[0115] Moreover, in the present modified example, the parking lot manager (provider) can start the charging service just by inserting the universal plug 402 of the power output device 400 into the universal outlet 26 provided at the outlet installation location, such as the parking lot 80, where the outlet 20 serving as the energy output unit is to be installed, as in the above-described embodiment. Therefore, in the present modified example, as in the above-described embodiment, the registration of parking lot managers (providers) in the charging service (energy supply service) is promoted, and the number of energy output units (outlets 20) available to users and the expansion of installation areas are promoted.
[0116] The processing steps described in this specification and the components of the information processing device, gate device, vehicle-mounted device, terminal device, server, etc. can be implemented by various means. For example, these steps and components may be implemented by hardware, firmware, software, or a combination thereof.
[0117] For hardware implementation, means such as processing units used to realize the above steps and components in an entity (e.g., a computer device, a server, a gate device, an in-vehicle device in a vehicle, a terminal device (user device, mobile station, communication terminal), a hard disk drive device, or an optical disk drive device) may be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units, computers designed to perform the functions described in this specification, or combinations thereof.
[0118] Also, for firmware and / or software implementations, the means such as processing units used to realize the components may be implemented with programs (e.g., codes such as procedures, functions, modules, instructions, etc.) that execute the functions described herein. In general, any computer / processor readable medium tangibly embodying firmware and / or software codes may be used to implement the means such as processing units used to realize the steps and components described herein. For example, the firmware and / or software codes may be stored in a memory and executed by a computer or processor, for example in a controller. The memory may be implemented within the computer or processor, or may be implemented externally to the processor. Also, the firmware and / or software codes may be stored in a computer or processor readable medium, such as a random access memory (RAM), a read-only memory (ROM), a non-volatile random access memory (NVRAM), a programmable read-only memory (PROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a floppy disk, a compact disk (CD), a digital versatile disk (DVD), a magnetic or optical data storage device, etc. The code may be executed by one or more computers or processors and may cause the computers or processors to perform certain aspects of the functionality described herein.
[0119] The medium may be a non-transitory recording medium. The code of the program may be in any format as long as it can be read and executed by a computer, a processor, or another device or machine, and the format is not limited to a specific format. For example, the code of the program may be any of source code, object code, and binary code, or may be a mixture of two or more of these codes.
[0120] Moreover, the description of the embodiments disclosed herein is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. [Explanation of symbols]
[0121] 10: Service Management System 20: Outlet 21: Code image 22, 23: Identification aid images 25: Charging station 26: General-purpose outlet 30: Vehicle 31: Battery 32: External Communications Department 33: Detection section 40: Power cable 41: Plug 50: User 51: Terminal device 60: Communication network 80: Parking lot 81: Entrance / exit 82: Gate device 83: Electric energy meter 85:Electric power usage equipment 100: Service Management Server 101: Terminal communication unit 102: Server communication section 103: Management department 104: Storage section 105: Billing processing unit 106: Payment processing unit 200: Power management device 210: Power distribution equipment 300: Vehicle management server 400: Power output device 402: Universal plug 410: Switch section 420: Control section 430: Network Communication Department 440: Electric energy measurement section
Claims
1. An information processing device for managing an energy supply service, a provider-side registration information acquisition unit that acquires provider-side registration information including information on a provider who owns or manages an energy output unit that can be used for the energy supply service and information on the energy output unit; a user-side registration information acquisition unit that acquires user-side registration information including information of a user who uses, owns, or manages an energy supply object that can utilize the energy supplied by the energy supply service and information of the energy supply object; a storage unit which stores the provider registration information in association with output unit identification information for identifying the energy output unit, stores the user registration information in association with supply target identification information for identifying the energy supply target, and information on a terminal device used by the user when using the energy supply service, and forms a transaction table for storing records which, for each of a plurality of uses of the energy supply service, correspond to one another, the output unit identification information, the identification information of the user or the terminal device, the supply target identification information, and energy supply information relating to the supply of energy from the provider's energy output unit to the energy supply target of the user; a usage start information receiving unit that receives, from the user's terminal device at the start of use of the energy supply service, usage start information including the output unit identification information corresponding to the energy output unit that supplies energy to the energy supply target, identification information of the user or the terminal device, and identification information of the energy supply target; a supply information acquisition unit that acquires, when the energy supply service is used, energy supply information related to the energy supply to the energy supply target of the user from the energy output unit of the provider, and adds the output unit identification information, the identification information of the user or the terminal device, the identification information of the energy supply target, and the energy supply information to the transaction table of the storage unit in association with each other; a payment processing unit that refers to information in the transaction table stored in the storage unit based on the energy supply information acquired by the supply information acquisition unit, and performs processing required to pay the provider a fee for providing an energy supply service from the energy output unit to the energy supply target; a billing processing unit that refers to information in the transaction table stored in the storage unit based on the energy supply information acquired by the supply information acquisition unit, and performs processing required to bill the user for a usage fee for an energy supply service from the energy output unit to the energy supply target; 13. An information processing device comprising:
2. 2. The information processing device according to claim 1, The information processing device is characterized in that the energy output unit receives energy from an energy company to which the provider pays an energy fee based on the combined amount of energy supplied from the energy output unit to the energy supply target and energy supplied from sources other than the energy output unit to other supply targets other than the energy supply target, and supplies the energy to the energy supply target.
3. 3. The information processing device according to claim 1, The information processing device is characterized in that the supply information acquisition unit acquires, as the energy supply information, at least user side identification information of the party that uses energy, provider side identification information of the party that provides energy, and variable parameter information that varies the supply fee and the usage fee.
4. 4. The information processing device according to claim 3, The information processing device, wherein the supply information acquisition unit receives and acquires the variable parameter information from a management device that manages the energy supply target.
5. 4. The information processing device according to claim 3, The information processing apparatus is characterized in that the supply information acquisition unit receives and acquires the variable parameter information from the energy supply target.
6. 4. The information processing device according to claim 3, The information processing device, wherein the supply information acquisition unit receives and acquires the variable parameter information from an energy output device including the energy output unit.
7. 7. The information processing device according to claim 3, The information processing device, wherein the supply information acquisition unit receives and acquires the use side identification information and the provider side identification information from a terminal device of the user.
8. 8. The information processing device according to claim 1, An information processing device characterized by performing authentication processing for a combination of the user or the terminal device and the energy supply target based on identification information of the user or the terminal device and identification information of the energy supply target received from the user's terminal device.
9. 9. The information processing device according to claim 1, The energy supply target is an electric vehicle equipped with a rechargeable battery, the energy being electrical energy supplied to the battery; the energy output unit is an outlet that outputs electrical energy, The information processing device is a server that manages the provision of electric energy to the vehicle and the use of electric energy in the vehicle.
23. An information processing apparatus comprising:
10. 10. The information processing device according to claim 9, The energy supply information includes data on the state of charge (SoC) of the battery of the vehicle.
23. An information processing apparatus comprising:
11. 11. The information processing device according to claim 9, The information processing device is characterized in that the vehicle identification information is received and acquired from the terminal device, a gate device installed at the entrance / exit of a parking lot where the vehicle is parked, or an ETC (Electronic Toll Collection System) on-board device mounted on the vehicle.
12. A system for managing an energy supply service, comprising: An information processing device according to any one of claims 1 to 11, A system comprising: a transmitting device that transmits the energy supply information acquired by the supply information acquisition unit of the information processing device to the information processing device.
13. 1. A method for managing an energy supply service, comprising: acquiring provider registration information including information on a provider who owns or manages an energy output unit that can be used for the energy supply service and information on the energy output unit; Acquiring user-side registration information including information of a user who uses, owns, or manages an energy supply object that can utilize energy supplied by the energy supply service and information of the energy supply object; storing the provider registration information and output unit identification information for identifying the energy output unit in association with each other, and storing the user registration information, supply target identification information for identifying the energy supply target, and information on a terminal device used by the user when using the energy supply service in association with each other; forming a transaction table for storing records in which the output unit identification information, the identification information of the user or the terminal device, the supply target identification information, and energy supply information related to the energy supply from the energy output unit of the provider to the energy supply target of the user are associated with each other for each of the multiple uses of the energy supply service; receiving, from the user's mobile terminal device at the start of use of the energy supply service, usage start information including the output unit identification information corresponding to the energy output unit that supplies energy to the energy supply target, identification information of the user or the mobile terminal device, and identification information of the energy supply target; When the energy supply service is used, energy supply information regarding the energy supply to the energy supply target of the user is acquired from the energy output unit of the provider, and the output unit identification information, the identification information of the user or the mobile terminal device, the identification information of the energy supply target, and the energy supply information are added to the transaction table of the storage unit in association with each other; referring to the stored information in the transaction table based on the energy supply information, and performing a process required for paying the provider a fee for providing the energy supply service from the energy output unit to the energy supply target; based on the energy supply information, referencing the stored information in the transaction table and performing the necessary processing to charge the user for the use of the energy supply service from the energy output unit to the energy supply target.
Citation Information
Patent Citations
Mobile outlet, power supply gate apparatus, server apparatus and power-utilizing management system
JP2002325357A
Charging stand management system
JP2008065635A
Power supplying system for electric vehicle
JP2013178594A
Communication system, server device, terminal device, and program
JP2019079346A
Fee setting server, fee setting system and fee setting method for car-sharing fee
JP2019096058A