WO2024038911A1 - Information processing device and system - Google Patents

Abstract

The present invention corrects inequality in a usage fee between users that is caused by a difference in the energy output units that are used by the users. Provided is an information processing device that manages energy usage fees, the information processing device having: an acquisition unit 102 that acquires selected output unit information indicating a selected output unit, which is selected from among a plurality of types of energy output units 20A to 20C, when energy is supplied to an energy supply target 30 belonging to a user by the selected output unit; and a usage fee calculation unit 105 that calculates a usage fee to be charged to the user. The usage fee calculation unit calculates the usage fee on the basis of the selected output unit information acquired by the acquisition unit.

Description

Information processing equipment and systems

The present invention relates to an information processing device and system that manage usage charges for energy such as electricity.

Conventionally, systems for managing electricity usage charges through outlets have been known. For example, Patent Document 1 describes a power supply gate device that controls power supply, a server device (information processing device) that manages usage fees according to the amount of power supplied from the power supply gate device, and a power supply gate device that controls power supply. A system is disclosed that includes a mobile outlet (energy output section) that connects between a gate device and an electric vehicle (energy supply target). After the power from the power supply gate device is output from the mobile outlet and supplied to the electric vehicle, the current power supply amount (energy supply amount) detected by the power usage totalizer of the mobile outlet is transferred from the mobile outlet to the server device. The information is transmitted, and the server device calculates the power usage fee from the received power supply amount.

Japanese Patent Application Publication No. 2002-325357

Conventionally, when supplying energy to a user's energy supply target, the usage fee charged to the user is calculated from the amount of energy supplied. However, with such a usage fee calculation method, inequality in usage fees may occur among users.

An information processing device according to one aspect of the present invention is an information processing device that manages energy usage charges, and supplies energy to a user's energy supply target by a selection output unit selected from a plurality of types of energy output units. and a usage fee calculation unit that calculates a usage fee to be charged to the user. The usage fee is calculated based on the selected output unit information acquired by the acquisition unit.
In the information processing device, the types of the energy output unit may include a type that is connected by wire to the energy supply target and a type that is wirelessly connected to the energy supply target.
Furthermore, in the information processing device, the types of the energy output unit may include a plurality of types in which the shapes of terminals connected to the terminal to which energy is supplied differ from each other.
Further, the information processing device may include a provision fee calculation unit that calculates a provision fee to be paid to a provider of energy supplied to the energy supply target, and the provision fee calculation unit The provision fee may be calculated based on the selected output unit information acquired by the acquisition unit.

Further, a system according to another aspect of the present invention is a system for managing energy usage charges, and includes the information processing device and a transmitting device that transmits the selected output section information to the information processing device. .

According to the present invention, when supplying energy to an energy supply target, it is possible to correct the inequality in usage charges between users due to differences in the energy output units used by each user.

FIG. 1 is an explanatory diagram for explaining the entire service management system according to the embodiment. FIG. 2 is an explanatory diagram showing an example of the main configuration of the service management system. FIG. 3A is an explanatory diagram showing an example of an image attached to the connection I/F of the embodiment. FIG. 3B is an explanatory diagram showing an example of an image attached to the connection I/F of the embodiment. FIG. 3C is an explanatory diagram showing an example of an image attached to the connection I/F of the embodiment. FIG. 4 is a block diagram showing an example of the configuration of the main functions of the service management server in the service management system. FIG. 5 is a flowchart showing an example of service management processing in the service management server. FIG. 6A is an explanatory diagram showing an example of a charging service that charges a running vehicle. FIG. 6B is an explanatory diagram showing an example of a charging service that charges a running vehicle.

Hereinafter, one embodiment of the present invention will be described with reference to the drawings.
The system according to this 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, for example, owned or managed by a provider that provides energy in an energy supply service. The supplied energy may be, for example, primary energy in the form of oil, natural gas, coal, etc., or secondary energy in the form of electricity, hydrogen, gasoline, light oil, heavy oil, city gas, alcohol, etc. .

The energy supply target to which energy is supplied is, for example, an electric moving body driven by a motor equipped with a battery. The moving object may be a moving object that moves on the ground such as an electric vehicle or a fuel cell vehicle, a moving object that moves in the air such as a drone, or a moving object such as a ship that moves on water such as the sea. Good too. The moving object may be a vehicle with four or more wheels, a tricycle, a two-wheeled vehicle (motorcycle, bicycle), a truck, a bus, a private car, a business vehicle, or the like. The energy supply target is, for example, something used, owned, or managed by a user of the energy supply service. The energy supply target may be leased from a leasing company, or may be owned by a business other than the user. Moreover, the energy supply target may be electric equipment or electronic equipment such as portable or installed home appliances, office equipment, and communication terminal devices.

In the following embodiments, as an example, the energy to be supplied is electrical energy, and the energy output unit that outputs the energy is composed of multiple types of connection interfaces (hereinafter referred to as "connection I/F"), and the energy is The target of energy supply is a vehicle or a battery built into the vehicle, and a service management system that manages a charging service (energy supply service) that charges the vehicle battery with the power output from each connection I/F. Let me explain the case.

FIG. 1 is an explanatory diagram showing a service management system 10 according to this embodiment.
This service management system 10 provides connections selected from a plurality of types of connection I/Fs 20 (20A to 20C) within an area of a parking lot 80 having a parking space where a plurality of vehicles 30-1 to 30-3 can be parked. It manages a charging service that charges a vehicle battery using an I/F (selection I/F as a selection output unit). The entrance/exit 81 is one place where the vehicles 30-1 to 30-3 enter and exit the parking lot 80. A gate device 82 is installed at an entrance 81 of the parking lot 80.

In the parking lot 80, charging stations 25-1 to 25-5 each having a plurality of types of connection I/Fs 20 are installed near each parking space. In the example of FIG. 1, five charging stations 25-1 to 25-5 are installed in the parking lot 80, but the number of charging stations installed in the parking lot is arbitrary. There may be more than one.

The five charging stations 25-1 to 25-5 in the parking lot 80 receive power via power lines from the power distribution equipment 210 of the same power company, which is an energy provider (Step A), and are managed by the power company. The amount of power supplied is measured by a single power meter 83. Therefore, in this embodiment, the configuration is such that the amount of power supplied from the five charging stations 25-1 to 25-5 cannot be measured separately for each charging station.

Additionally, this power meter 83 measures the amount of power supplied to the charging stations 25-1 to 25-5 as well as the gate device 82 and various power usage equipment 85 that use power. Therefore, in this embodiment, the configuration is such that it is not possible to distinguish and measure the amount of power supplied by the charging stations 25-1 to 25-5 and the amount of power supplied by the other power utilization facilities 82 and 85. .

The power supply amount (power amount data) measured by the power meter 83 is sent to the power management device 200 of the power company (step B). For example, if the watt-hour meter 83 is equipped with a communication function, such as a smart meter, the watt-hour data is transmitted to the power management device 200 of the electric power company via a communication line.

The power usage equipment (charging stations 25-1 to 25-5, gate device 82, power usage equipment 85) whose power supply amount is measured by the power meter 83 is provided by the parking lot manager (connection I/F 20 is managed by the installer). Therefore, the electricity fee (energy fee) for the amount of power supplied by the power company and used by these power usage facilities 25-1 to 25-5, 82, and 85 will be paid by the parking lot manager to the power company. (Step C).

The power fee paid by the parking lot manager to the electric power company can be covered by, for example, the parking lot fee collected by the parking lot manager from the parking lot users who use the parking lot. This electricity charge includes the charge for the amount of electricity supplied to the vehicle 30-1 from the charging stations 25-1 to 25-5, but some parking lot users charge This also includes non-users who do not use the stands 25-1 to 25-5 (such as users of cars without charging functions). Further, even for users who use the charging stations 25-1 to 25-5, the amount of power supplied from the charging stations usually differs. Therefore, it is unfair and undesirable for the parking lot users to uniformly collect the amount of electricity paid by the parking lot manager to the power company on top of the parking lot fees of the parking lot users.

The service management system of this embodiment collects usage fees from users who receive power supply from charging stations 25-1 to 25-5, and stores fees for the amount of power supplied to the users (provided fees). Manage charging services paid to parking lot managers (providers). According to this service management system, the parking lot manager pays the electricity fee for the amount of electricity supplied from the charging stations 25-1 to 25-5 to the electric power company for the amount of electricity supplied by the charging service. This can be covered by fees.

Furthermore, in the service management system of this embodiment, users who receive power supply from the charging stations 25-1 to 25-5 are charged a usage fee according to the content of the power supply service (charging service). Therefore, an appropriate usage fee can be collected from the users of the charging stations 25-1 to 25-5 according to the content of the power supply service to which the users receive power supply.

FIG. 2 is an explanatory diagram showing an example of the main configuration of the service management system 10 according to the present embodiment.
In FIG. 2, the service management system 10 provides and uses electric power (charging service) to a target to which electric power is supplied by a selection I/F selected from a plurality of types of connection I/Fs 20 (20A to 20C). to manage. The object of supply in this embodiment is the vehicle 30 or the battery 31 of the vehicle 30 that is charged with the power from the connection I/Fs 20A to 20C. The plurality of types of connection I/Fs 20 provided in the charging stand 25 are three types in this embodiment.

The first connection I/F is a type of wired interface that connects the charging stand 25 and the vehicle 30 or the battery 31 by wire, and is the outlet 20A to which the plug 41A of the wired power cable 40 of the vehicle 30 is connected and disconnected. Although this outlet 20A has the same terminal shape as a general-purpose household outlet whose purpose is not limited, it may be a dedicated outlet whose purpose is limited.

The second connection I/F is also a type of wired interface that connects the charging stand 25 and the vehicle 30 or the battery 31 by wire, and is a power supply plug 20B dedicated to the power receiving plug that is attached to and detached from the power receiving plug 41B of the vehicle 30. be. This power supply plug 20B is a wired interface like the above-mentioned outlet 20A, but the terminal shapes for connecting the charging stand 25 and the vehicle 30 or the battery 31 are different from each other.

In this embodiment, there is a difference in that the power supply speed through the power supply plug 20B is faster than the power supply through the above-mentioned outlet 20A under the same conditions. On the other hand, in this embodiment, the power supply plug 20B has a difference in that the equipment cost (introduction cost) is higher than the above-mentioned outlet 20A. Note that the voltage (current) supplied from these wired connection I/ Fs 20A and 20B may be alternating current or direct current.

The third connection I/F is a type of wireless interface that wirelessly connects the charging stand 25 and the vehicle 30 or the battery 31, and connects the wireless power receiving device 41C of the vehicle 30 with radio waves such as electromagnetic induction and microwaves. This is a wireless power supply device 20C that performs wireless power supply such as power supply and power supply using light such as laser light.

Note that in this embodiment, the above-mentioned three types of connection I/Fs 20A to 20C are used, but the number of types of connection I/Fs 20 may be two or four or more types. Further, the wired connection I/F is not limited to the above-mentioned method, and the wireless connection I/F is not limited to the above-mentioned method, but any method may be adopted. The connection I/F 20 may be, for example, a dedicated coupler inlet used in a normal charger, a quick charger, or the like.

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 electric power (electrical energy). The service management server 100 may be configured as a single computer device, may be configured to have multiple computer devices working together, or may be configured as a cloud system on a network.

3A to 3C are explanatory diagrams each showing an example of an image attached to the connection I/F 20 of this embodiment. Although only the outlet 20A is shown as the connection I/F 20 in FIGS. 3A to 3C, the image attached to the connection I/F 20 shows the power supply plug 20B, which is another connection I/F in the same charging station 25. and the wireless power receiving device 41C are also attached. That is, the image on the charging stand 25 is common to the outlet 20A, the power supply plug 20B, and the wireless power receiving device 41C. Note that different images may be attached to the outlet 20A, the power supply plug 20B, and the wireless power receiving device 41C.

A code image (for example, an image of a QR code (registered trademark)) 21 is attached to the connection I/F 20 in FIG. 3A. 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, identification number, installation location, and installation entity (parking lot manager) of the connection I/F 20 is encoded.

An image of characters (for example, handwritten characters) 22 is attached to the connection I/F 20 in FIG. 3B as an identification auxiliary image of the connection I/F 20 arbitrarily attached by a parking lot manager or the like. Further, an image of an illustration 23 as an identification aid image arbitrarily added by a parking lot manager or the like is attached to the connection I/F 20 in FIG. 3C. The characters 22 or illustrations 23 may be attached to the connection I/F 20. The characters 22 and illustrations 23 of the connection I/F 20 may be drawn on a seal member 24 by a parking lot manager or the like and pasted on the side of the connection I/F 20. Note that the identification auxiliary image may be a pattern or a mark in addition to characters and illustrations.

The terminal device 51 of the user 50 who wants to use the power supplied from the connection I/F 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 section such as keys, buttons, and a touch panel, a display section such as a liquid crystal display, and an imaging section such as a camera that captures a code image of a connection I/F, an identification auxiliary image, and the like. The terminal device 51 can start and execute a pre-installed predetermined power usage application (power usage application) by a user's operation. The terminal device 51 may include a current location acquisition unit such as a GNSS receiver that obtains information about its current location. The terminal device 51 is, for example, a mobile station (also referred to as a "mobile device", "user equipment (UE)", etc.) that can communicate via a mobile communication network of the fourth generation or the fifth generation or later. Good too.

The vehicle 30 can communicate with the service management server 100 of the service management provider and the vehicle management server 300 of the vehicle manufacturer via the communication network 60 using the external communication unit 32 of the on-vehicle device. Note that the external communication unit 32 may separately include a communication unit that communicates with the service management server 100 and a communication unit that communicates with the vehicle management server 300.

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 a 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 (ECU) that control other parts are connected to the in-vehicle network (CAN). There is.

Next, the flow of the charging service managed using the service management system 10 according to this embodiment will be explained.
Power usage information (for example, battery identification information, electric power amount, charging start time, charging end time), which is energy supply information regarding power supply related to charging of the battery 31, is transmitted from a battery management system (BMS) to a remote control unit ( TCU) to the vehicle management server 300 of the vehicle manufacturer (step 1). In addition, vehicle identification information, which is user identification information on the side that uses electric power, is transmitted from an electronic control unit (ECU) having a memory that stores basic information of the vehicle to a remote control unit (TCU) for vehicle management. It is sent to server 300. The transmission of this information to the vehicle management server 300 is performed, for example, based on timing specified by the vehicle management server 300, or based on a transmission request generated by an application running on the terminal device 51. Ru. The transmission request from the terminal device 51 may be received by a remote control unit (TCU) of the vehicle, for example, via short-range wireless communication such as wireless LAN or Bluetooth (registered trademark). The vehicle management server 300 of the vehicle manufacturer stores the power usage information of the vehicle 30 in association with the identification information of the vehicle 30, and manages the latest power usage information almost in real time.

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 using the connection I/F 20 of the charging station 25-1, the user 50 The user executes the power usage application and reads the code image (for example, a QR code (registered trademark) image) 21 (see FIG. 3A) attached to the connection I/F 20. Then, the user 50 operates the terminal device 51 to transmit the reading data of the code image 21, which is the provider identification information of the power provider, 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 power is supplied by the connection I/F 20 (for example, 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).

The user side 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), may be registered in advance in the power usage application of the terminal device 51, for example. Ru. The read data of the code image 21, which is the provider identification information, may be, for example, image data obtained by capturing the code image 21 with a camera of the terminal device 51, or may be data obtained by decoding the image data. . In addition, as the provider identification information, instead of the read data of the code image 21, the read data of the identification auxiliary image 22 or 23 (see FIGS. 3B and 3C) attached to the connection I/F 20, and the read data of the terminal device 51 The location information may also be used. The location information of the terminal device 51 is, for example, the location information (latitude, longitude, altitude) of the terminal device 51 determined by the GNSS receiver of the terminal device 51.

Note that examples of provider identification information are not limited to those described above. For example, the charging stand 25 provided with the connection I/F 20 may be provided with an RF tag that stores identification information of the connection I/F 20. In this case, the user 50 executes the power usage application on the terminal device 51, wirelessly communicates with this RF tag, and acquires the identification information of the connection I/F 20 stored in the RF tag. Then, the user 50 operates the terminal device 51 to transmit the identification information of the connection I/F 20, which is the provider identification information, from the terminal device 51 to the service management server 100 via the communication network 60.

In the present embodiment, the user identification information and provider identification information described above are transmitted from the terminal device 51 of the user 50 to the service management server 100 via the communication network 60, but the present invention is not limited to this. For example, a communication device such as an IoT communication module is installed in the charging stand 25 equipped with the connection I/F 20, and the communication device communicates with the terminal device 51 of the user 50 via the communication network. The user identification information and provider identification information may be acquired and transmitted to the service management server 100 via a communication network.

Next, the service management server 100 of the service management company receives read data of the code image 21 from the terminal device 51 of the user 50, and also receives variable parameter information as energy supply information from the vehicle management server 300 of the vehicle manufacturer. Obtain power usage information including supply amount information (step 3). The supply amount information is information regarding the amount of power supplied by the connection I/F 20 to the vehicle 30 that is the supply target of the user 50.

In addition, the service management server 100 selects one of the three types of connection I/Fs 20A to 20C provided in the charging stand 25 corresponding to the read data of the code image 21, etc. to charge the vehicle 30-1 that is the supply target. Information indicating the selection I/Fs 20A to 20C to be used (selection output unit information) is received (step 4). In this embodiment, the charging station 25 is provided with a detection unit that detects the selection I/Fs 20A to 20C used for charging the vehicle 30-1 that is the supply target. For example, when the user performs an operation on the operation unit provided in the charging stand 25 to select the connection I/F 20 used for charging the vehicle 30, the selection I/F 20A to 20C is detected. Examples include those that detect

Then, the service management server 100 performs necessary processing to collect usage fees for the amount of power supplied for charging the vehicle 30-1 from the user 50 based on the amount of supply information included in the acquired power usage information. (Usage fee charging process) is performed (Step 5). At this time, in this embodiment, information ( Based on the selected output unit information), an additional charge corresponding to the selected I/F 20A to 20C (that is, the type of connection I/F 20 used for this charging) is determined, and a usage charge including the additional charge is calculated. Then, the service management company that operates the charging service collects a usage fee from the user 50 for the amount of power supplied for charging the vehicle 30-1 (including additional fees depending on the selected I/Fs 20A to 20C). (Step 7).

The billing process (processing necessary for billing) performed by the service management server 100 collects usage fees for the amount of power supplied for charging the vehicle 30-1 from the user 50 based on the acquired supply amount information. This process is at least part of a series of processes (including all known billing processes) necessary to do so. As a specific example, for example, a process of calculating a usage fee (including the above-mentioned additional fee) for the amount of power supplied for charging the vehicle 30-1 from the acquired supply amount information and information on the selection I/F; Processing to perform procedures for charging usage fees to users, processing to provide at least one of supply amount information and usage fee information to a management device managed by another business operator that collects the usage fees from users, etc. Examples include processing including.

In addition, when the service management server 100 receives the reading data of the code image 21 from the terminal device 51 of the user 50, the service management server 100 determines whether the vehicle 30-1 is charged or not based on the acquired supply amount information and selection I/F information. Processing (preparation for payment of provision fee) necessary to pay the parking lot manager a fee for supplying power (including additional fees depending on the selected I/Fs 20A to 20C) is performed (step 6). As a result, the service management company that operates the charging service can pay the parking lot manager the fee for providing electricity (including the above-mentioned additional fee) for the amount of power supplied for charging the vehicle 30-1 (step 8).

Payment processing (processing necessary for payment) performed by the service management server 100 is to pay the parking lot manager a fee for the amount of power supplied for charging the vehicle 30-1 based on the acquired supply amount information. This is at least a part of the series of processes necessary for this (including all known payment processes). As a specific example, for example, a process of calculating a charge for the amount of power supplied for charging the vehicle 30-1 from the acquired supply amount information and information of the selection I/F, Processing that includes procedures for payment to a parking lot operator), and processing that provides at least one of supply amount information and provision fee information to a management device managed by another business operator that pays the provided fee to the parking lot manager. can be mentioned.

In addition, in this embodiment, the amount of power supplied (energy supply target) supplied to the battery 31 (energy supply target) of the vehicle 30 by the connection I/F 20 (energy output unit) is used as variable parameter information for varying the provision fee and usage fee. supply amount information regarding the supply amount) is used, but is not limited to this. For example, when changing the provision fee or usage fee depending on the charging time (charging end time - charging start time), information on the charging time can be used as variable parameter information. In this case, since there is no need for a detection unit that detects the amount of power supplied during charging, it is possible to provide a service management system with a simple configuration.

In particular, in this embodiment, information indicating the types of connection I/Fs 20A to 20C (types of selection I/Fs 20A to 20C) used during charging is used as variable parameter information. The amount of additional charges (usage charges and provision charges) depending on the connection I/Fs 20A to 20C will vary as the equipment costs (introduction costs) and running costs of each connection I/F 20A to 20C are higher. You may decide to make it expensive.

In this case, it is possible to correct the inequality among users due to differences in the cost burden of the connection I/F used, and it is possible to provide a charging service that gives a sense of equality to the users. Further, it is possible to correct the inequality among parking lot managers due to differences in cost burdens of the connection I/Fs used, and it is possible to provide a charging service that gives a sense of equality to parking lot managers. In particular, it is possible to create an appropriate path for recovering the investment for the parking lot manager of the connection I/F 20 who has made a large capital investment.

Further, for example, if the power supply speed (power supply amount per unit time) to the vehicle 30 at each connection I/F 20A to 20C is different from each other, the amount of additional charge (usage fee The amount of the connection I/F 20A to 20C with a faster power supply speed may be higher or lower, or the amount may be set according to the power supply speed of the connection I/F 20A to 20C to be used. good.

In this case, it is possible to correct the inequality between users due to differences in power supply speeds (such as whether or not charging can be completed in a short time), and it is possible to provide a charging service that gives a sense of equality to users. . In addition, it is possible to correct inequality among parking lot managers due to differences in power supply speeds, and it is possible to provide a charging service that gives a sense of equality to parking lot managers.

Furthermore, the power supply speed may vary depending on the type, configuration, or state of the vehicle 30 and battery 31 to which energy is supplied. Specifically, the AC power consumption rate (electricity cost) of the vehicle, battery capacity, remaining battery level, degree of battery deterioration (mileage of the vehicle 30, usage period of the battery 31, etc.), charging efficiency, vehicle position (the vehicle 30 is For plug-in hybrid vehicles, the power supply speed may vary depending on the area where the battery is being charged (the area where the battery is being charged), the amount of gasoline remaining, etc. Therefore, such supply target information may be acquired as variable parameter information to understand the difference in power supply speed, and the usage fee to be charged to the user or the provision 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 (classification) of the vehicle 30 (energy supply target), which will be described later.

Furthermore, for example, some of the connection I/Fs 20 have different types of output power (energy) generation methods. This type includes, for example, types recommended by national energy policies, types with low production costs, and the like. In this way, if there are connection I/Fs 20 with different types of output power (energy) generation methods, the provision fee will be changed depending on the type of connection I/F 20 due to the difference in the type of power (energy) generation method. The usage fee may also be changed.

As a specific example of the type of generation method of the output power (energy), the power source that generates the power is one that generates power from fossil fuels such as oil or coal, or one that generates power from fossil fuels such as oil or coal, or one that uses wind power or solar power. , and those that distinguish whether electricity is generated from natural energy such as biomass (living resources). Further, it may be possible to further differentiate the types of these fossil fuels and natural energies (for example, in the case of natural energy, to distinguish between wind power, sunlight, and biomass (biological resources)). The type can be determined, for example, based on the presence or absence of a certificate (such as a green power certificate) issued by a predetermined certification authority. The type of generation method of the output power (energy) is not limited to the type of power source as described above, and may be a method that distinguishes the amount of CO ₂ (carbon dioxide) generated in the power generation process.

Note that the type of power generation method corresponding to each connection I/F 20 can be associated in advance for each connection I/F 20, for example, based on an application from a parking lot manager. Specifically, the type of power generation method corresponding to each connection I/F 20 is stored in the storage unit 104 of the service management server 100 in association with provider identification information such as identification information of each connection I/F 20. Information (for example, information on the presence or absence of a green power certificate) is stored.

Further, for example, the connection I/F 20 in the system of the present embodiment may have a different type (type) of the corresponding vehicle 30 (energy supply target). This type includes, for example, the manufacturer and model of the vehicle 30, or the manufacturer and model of the battery 31 installed in the vehicle 30. In this way, when the types of corresponding vehicles 30 are different, the power supply speed may be different, and the cost for power supply (equipment cost of the connection I/F 20) may be different. In such a case, the provision fee or the usage fee may be varied depending on the type of the connection I/F 20 depending on the type of the corresponding vehicle 30 (energy supply target). Note that the type of vehicle 30 that each connection I/F 20 supports may be determined by the service management server 100 based on the vehicle identification information of the vehicle 30 transmitted from the external communication unit 32 of the vehicle 30, for example. Can be done.

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 section 101 as a supply information acquisition section, a server communication section 102, a management processing section 103, a storage section (DB: database) 104, a billing processing section 105, and a payment processing section 105. A processing unit 106 is provided.

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, for example, reads data of the code image 21 transmitted from the terminal device 51, identification information of the user 50 or the terminal device 51, identification information of the supply target to which power is supplied by the connection I/F 20 (e.g. , identification information of the vehicle 30 or the battery 31), etc.

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 connection I/F 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-side identification information. Therefore, the terminal communication section 101 functions as a supply information acquisition section.

The server communication unit 102 communicates via the communication network 60 with the vehicle management server 300 of the vehicle manufacturer to which the vehicle 30 to be supplied is registered. The server communication unit 102 receives, for example, at least supply amount information (variable parameter information) of the power usage information of the vehicle 30 stored by the vehicle management server 300 from the vehicle management server 300 via the communication network 60. do.

Note that 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).

The management processing unit 103 performs authentication ( At least one of authentication (user authentication) and authentication of the supply target (for example, vehicle 30 or battery 31) (supply target authentication) is performed.

For example, the management processing unit 103 compares the identification information (user ID) of the user 50 received from the terminal device 51 and the identification information (user ID) of the user registered in advance in the service management server 100. By doing so, user authentication is performed to confirm whether the user 50 is an authorized user registered in advance in the service management system of this embodiment. In this case, use of the charging service may be permitted when the user is an authorized user, and use of the charging service may be restricted (for example, use may be prohibited) when the user is not an authorized user.

Further, for example, the management processing unit 103 uses the identification information of the supply target (for example, the identification information of the vehicle 30 or the battery 31) received from the terminal device 51 and the identification information of the supply target registered in advance in the service management server 100. (for example, identification information of the vehicle 30 or battery 31), it is possible to determine whether the supply target (for example, the vehicle 30 or battery 31) is a regular supply target registered in advance in the service management system of this embodiment. Supply target authentication may be performed to confirm the following. In this case, use of the charging service may be permitted when the charging service is an authorized supply target, and use of the charging service may be restricted (for example, usage may be prohibited) when the charging service is not an authorized supply target.

Furthermore, the management processing unit 103 receives information from the vehicle management server 300 of the vehicle manufacturer via the server communication unit 102 based on the identification information of the supply target (for example, identification information of the vehicle 30 or the battery 31) received from the terminal device 51. , receives and acquires the supply amount information of the supply target (step 3).

As described above, the supply amount information is information regarding the supply amount of power supplied to the vehicle 30, which is the supply target of the user 50, by the connection I/F 20. The supply amount information may be any information that can specify the amount of power supplied by the connection I/F 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 power usage information transmitted from the vehicle 30 to the vehicle management server 300, and is stored in the vehicle management server 300.

A specific example of the supply amount information is, for example, information that can be detected by the detection unit 33 provided in the vehicle 30, and is information that is information that can be detected by the detection unit 33 provided in the vehicle 30, and the amount of power (power If the information corresponds to the supply amount), the detected information can be used as the supply amount information.

Furthermore, for example, if the detection unit 33 provided in the vehicle 30 is capable of detecting the remaining amount of power in the battery 31, information on the detected remaining amount of power may be used as the supply amount information. In this case, for example, the amount of power supplied by the connection I/F 20 and used to charge the battery 31 (power supply amount) can be obtained by subtracting the remaining amount of power before charging from the remaining amount of power after charging. can.

Moreover, since many electric vehicles are equipped with a detection unit 33 that detects the state of charge (SoC) of the battery 31, SoC data may be used as supply amount information. In this case, unless the full charge capacity of the battery 31 is known, the remaining power level of the battery 31 cannot be determined from the SoC data. However, by storing the correspondence between the identification information of the battery 31 and the full charge capacity in the storage unit (DB) 104, the full charge capacity can be specified from the identification information of the battery 31, and the SoC data of the battery 31 can be stored. The remaining amount of power of the battery 31 can be calculated from .

The storage unit (DB) 104 stores information and data necessary for various processes performed by the service management server 100. Specifically, the reading data of the code image as the 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 identification information received by the server communication unit 102. The supply amount information and selection I/F information are stored in association with each other. For example, as shown in Table 1, for each series of power usage transactions, the connection I/FID, user ID, terminal ID (for example, IMEI), vehicle ID, power supply amount, and selection I/F type correspond to each other. One record attached is stored, and a power usage transaction table (power usage ledger) is formed as a whole.

Note that the connection I/FID of this embodiment is common to the three types of connection I/Fs 20A to 20C provided in the same charging stand 25, so the type of selected I/F is stored separately; If the I/FID is individually associated with each of the three types of connection I/Fs 20A to 20C provided in the same charging station 25, the type of selected I/F can be identified from the connection I/FID. , there is no need to separately store the type of selection I/F.

Additionally, the storage unit (DB) 104 stores various tables used for managing charging services. For example, the storage unit (DB) 104 stores a connection I/F management table shown in Table 2, a user management table shown in Table 3, and a vehicle management table shown in Table 4. Note that Table 2 may be an example in which the reading data of the identification auxiliary image 22 or 23 attached to the connection I/F 20 and the position information of the terminal device 51 are used instead of the reading data of the code image 21. . Furthermore, the storage unit (DB) 104 may further store an installer (provider) management table for managing the installer (provider) of the connection I/F 20, such as a parking lot manager. In the installer (provider) management table, information such as the name, address, etc. of the installer (provider) is recorded, for example, using the installer ID as a key.

The connection I/F management table, the user management table, and the vehicle management table are the connection I/F 20, the user 50 (terminal device 51), and the user 50 (terminal device 51) for using the charging service provided by the service management server 100 of this embodiment, respectively. A new record is added when a new vehicle 30 (battery 31) is registered.

In addition, the storage unit (DB) 104 contains the installer ID (identification information of the parking lot manager) and the processing (payment processing) necessary to pay the provision fee for the amount of electricity supplied to the parking lot manager. A payment processing table is stored that associates provider information such as used information (payee's account number, etc.) with energy output unit information such as the name of the corresponding connection I/F and code image read data. . A record is added to this payment processing table when a new installer (provider) of the connection I/F 20 is registered. By linking and referring to the payment processing table and the various tables described above, in the charging service of this embodiment, it is possible to process the payment process for the amount of electricity supplied to the installer (parking lot manager). can.

The storage unit (DB) 104 also contains information such as a user ID and information ( A billing processing table may be stored in which user information such as usage fee billing destination information is associated with information on energy supply targets regarding vehicles, batteries, 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, in the charging service of this embodiment, it is possible to perform billing processing for the usage fee for the amount of power supplied to the user.

For example, when using SoC data as the supply amount information, a battery information table showing the correspondence between identification information of the battery 31 and full charge capacity is stored in the storage unit (DB) 104.

FIG. 5 is a flowchart illustrating an example of service management processing in the service management server 100 according to the present embodiment.
In FIG. 5, the service management process of this embodiment includes a preliminary preparation phase (S100) and an operation phase (S200).

In the advance preparation phase (S100), when the service management server 100 receives an application for connection I/F registration to the charging service from the installer (provider) of the connection I/F 20, such as a parking lot manager, the service management server 100 performs information related to the application. Retrieve and store information. For example, when the operator inputs data regarding the connection I/F 20 of the installer (parking lot manager), the service management server 100 inputs the connection I/F management table of Table 2 and the payment processing table described above. Create (S101). Specifically, when there is an application for connection I/F registration, the operator performs a process for inputting provider registration information including information of the provider and information of the energy output unit into the service management server 100. Data is input using an input device (provider-side registration information acquisition unit) such as a keyboard or touch panel. As a result, the service management server 100 creates a table that associates the provider registration information input via the input device with the output unit identification information (connection I/FID, etc.) for identifying the energy output unit. It is stored in the database of the storage unit 104. By managing such a table, it is possible to perform appropriate payment processing for multiple providers according to the amount of power supplied by each connection I/F 20 (energy output unit). .

Note that the provider registration information acquisition unit in the service management server 100 is configured to receive and acquire provider registration information transmitted from a provider's terminal device via a communication network instead of data input by an operator. Good too.

Further, when a user 50 who uses a charging service (energy supply service) applies for the use of a charging service using a terminal device 51, the service management server 100 sends an application to the user 50 and the terminal device 51 from the terminal device 51. New registration data (user side registration information) including information (user information) and information on supply targets (vehicle 30 and battery 31) (information on energy supply targets) is received and acquired. The terminal communication unit 101 that receives this new registration data functions as a provider registration information acquisition unit.

The service management server 100 uses the received user side registration information, supply target identification information (vehicle ID and battery ID) that identifies the energy supply target, and information on the mobile terminal device used by the user when using the charging service (terminal ID) is stored in the database of the storage unit 104. As a result, the user management table shown in Table 3, the vehicle management table shown in Table 4, and the above-mentioned billing processing table are created (S102).

Next, in the operation phase (S200), when the user 50 receives power supply from the registered connection I/F 20 to charge the battery 31 of the vehicle 30, the user 50 first operates the terminal device 51 to provide the charging service. Start an application (power usage application) to use the power. Then, the terminal device 51 captures and reads the code image 21 including the identification information of the connection I/F 20, and selects "My Car" from the menu selection displayed on the display screen of the terminal device 51. Through this operation, the identification information of the user 50 (or terminal device 51), the read data of the code image 21, and the identification of the vehicle 30 (or battery 31) pre-registered as "my car" in the terminal device 51 are obtained. Information is transmitted from the terminal device 51 to the service management server 100. Thereby, the service management server 100 receives the identification information of the user 50 (or terminal device 51), the read data of the code image 21, and the identification information of the vehicle 30 (or battery 31) from the terminal device 51 of the user 50. Receive (S201).

Next, the service management server 100 uses the identification information of the user 50 (or terminal device 51) received from the terminal device 51 and the identification information of the vehicle 30 (or battery 31) to Authentication processing is performed for the combination of the identification information 51) and the vehicle 30 (or battery 31) (S202).

In addition, the user 50 selects one of the three types of connection I/Fs 20A to 20C provided in the charging stand 25 from the operating unit of the charging stand 25 used when charging the battery 31 of the vehicle 30. Perform an operation to select the connection I/F 20A to 20C used for charging. The charging stand 25 that has received this operation transmits information (selected output unit information) indicating the selected connection I/Fs 20A to 20C (selected I/F) to the service management server 100, and the service management server 100 receives this information. Receive (S203).

On the other hand, after completing the authentication process, the service management server 100 sends a message to the vehicle management server 300 based on the received identification information of the user 50 (or terminal device 51) and the identification information of the vehicle 30 (or battery 31). SoC data (supply amount information) regarding the vehicle 30 is requested. As a result, the latest supply amount information (SoC data before charging) regarding the vehicle 30 is acquired from the vehicle management server 300 to the service management server 100 via the communication network 60 (S204).

Thereafter, the battery 31 of the vehicle 30 is charged by the selected connection I/F (selection I/F), and when the charging is completed, the vehicle 30 is activated by a request from the terminal device 51 of the user 50 or autonomously. The power usage information (for example, battery identification information, electric energy (SoC data), charging start time, charging end time) supplied by the connection I/F 20 and used to charge the battery 31 of the vehicle 30 is stored in the vehicle management. Send to server 300. As a result, the SoC data after charging is registered in the vehicle management server 300.

Further, when charging is completed, a charging completion notification including identification information of the user 50 (or terminal device 51) and identification information of the vehicle 30 (or battery 31) is sent from the user's terminal device 51 to the service management server 100. sent to. Upon receiving the charging completion notification, the service management server 100 sends the vehicle to the vehicle management server 300 based on the identification information of the user 50 (or terminal device 51) and the identification information of the vehicle 30 (or battery 31). Request SoC data (supply amount information) for 30. As a result, the latest supply amount information (SoC data after charging) regarding the vehicle 30 is acquired from the vehicle management server 300 to the service management server 100 via the communication network 60 (S205).

In this way, the service management server 100 that has received the SoC data before charging and the SoC data after charging refers to the battery information table in the storage unit (DB) 104 to obtain the full charge capacity of the battery 31. . Then, the remaining power of the battery 31 before charging is calculated from the SoC data before charging and the full charge capacity, and the remaining power of the battery 31 after charging is calculated from the SoC data after charging and the full charge capacity. . Thereafter, the remaining amount of power before charging is subtracted from the remaining amount of power after charging to calculate the amount of power supplied for this charging (S206).

Next, the service management server 100 refers to the connection I/F management table of Table 2 described above based on the read data of the code image, and specifies the identification information of the connection I/F 20. Furthermore, the service management server 100 stores identification information of the connection I/F 20 (connection I/FID), identification information of the user 50 or terminal device 51 (user ID, terminal ID), and identification information of the supply target ( (vehicle ID or battery ID), the current charging amount (power supply amount) calculated in processing step S206, and the type of connection I/F (selection I/F) used for current charging obtained in processing step S203. are associated with each other and stored in the storage unit (DB) 104 so as to be added to the power usage transaction table (power usage ledger) in Table 1 described above (S207).

The service management server 100 can manage charging services that involve the supply of power via the connection I/F by referring to the power usage transaction table (power usage ledger) as shown in Table 1.

In this embodiment, the service management server 100 refers to the power usage transaction table (power usage ledger) to determine whether the user 50 or the supply target ( The process (charging process) necessary for charging at least one of the vehicle 30 or the battery 31) and the terminal device 51 is performed (S208). In this billing process, for example, the total amount of electricity supplied by each user during a predetermined period (for example, 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, with reference to the billing table in the storage unit 104, the billing process necessary to collect usage fees from each user is performed.

At this time, variable parameter information other than supply amount information (information on charging time (charging end time - charging start time), information on power supply speed (power supply amount per unit time), power (energy) generation method , information on the type of vehicle 30 (energy supply target), etc.) may be taken into account to calculate the usage fee.

The method of collecting the usage fee from the user is particularly limited if the usage fee includes an additional fee depending on the type of connection I/F 20 (selection I/F) used to charge the user's vehicle 30. There are no restrictions. When collecting usage fees according to the amount of power, a completely metered system may be used, or a flat rate system may be used in which a fixed amount is charged until a specified amount of power is supplied. The business that collects usage fees from users may be a service management business that operates the service management server 100, or another business that collects usage fees upon commission from the service management business. There may be.

In addition, in this embodiment, the service management server 100 refers to the power usage transaction table (power usage ledger) to inform the installer (parking lot manager) of the connection I/F 20 of the connection I/F 20. Processing (payment processing) necessary for paying the fee for providing electric power to the vehicle 30 via the vehicle 30 is performed (S209). In this payment process, for example, the total amount of power supplied corresponding to each installer's connection I/F 20 during a predetermined period (for example, one month) is calculated, this is multiplied by the unit price of the provision fee, and the amount is sent to each installer. Calculate the provision fee to be paid. Then, with reference to the payment processing table in the storage unit 104, the payment processing necessary to pay the provision fee to each installer is performed.

At this time, variable parameter information other than supply amount information (information on charging time (charging end time - charging start time), information on power supply speed (power supply amount per unit time), power (energy) generation method , information on the type of vehicle 30 (energy supply target), etc.) may be taken into account to calculate the provision fee.

As described above, in this embodiment, the service management server 100 uses the charging processing unit 105 to include the connection I/O used for charging in the power usage fee calculated from the supply amount information (variable parameter information) received by the server communication unit 102. Necessary charging processing is performed to charge the user 50 a usage fee including an additional fee depending on the type of F (selection I/F). As a result, the service management business operator who operates the service management server 100 receives power from the user 50 who has received power from the connection I/F 20, which is an energy output unit registered in the charging service (energy supply service) of this embodiment. , it is possible to provide a service that collects an appropriate usage fee according to the type of connection I/F 20 (selection I/F) used to charge the vehicle 30 of the user.

In the present embodiment, the service management server 100 uses the payment processing unit 106 to add the connection I/O used for charging to the electricity supply fee calculated from the supply amount information (variable parameter information) received by the server communication unit 102. The necessary payment processing is performed to pay the provision fee including the additional fee according to the type of F (selection I/F) to the parking lot manager who is the provider. As a result, the service management company that operates the service management server 100 can charge the parking lot at an appropriate fee according to the type of connection I/F 20 (selection I/F) used to charge the user's vehicle 30. It is possible to provide a charging service (energy supply service) that the administrator can receive.

In addition, in this embodiment, as described above, the connection I/F 20 as an energy output unit is used not only for a predetermined specific user (user registered in the charging service) but also for the specific user. This includes shared connection I/Fs (general-purpose connection I/Fs, etc.) that can also be used by unspecified general users (users who are not registered with the charging service (energy supply service) of this embodiment). But that's fine. Using such a shared connection I/F as the energy output unit of the service management system of this embodiment requires more permission for installation than when installing a connection I/F that can only be used by a specific user. This simplifies the procedure and contributes to increasing the number of energy output units that can be used in charging services (energy supply services) and expanding the installation area.

However, a shared connection I/F is usually equipped with a power meter that detects information on the amount of power supplied from the connection I/F; Information on the amount of power supplied from /F is detected all at once without distinguishing between users. Therefore, in a system that detects supply amount information using a detection unit provided on the shared connection I/F side, it is not possible to detect supply amount information by distinguishing specific users from general users. It is difficult to manage the provision and use of electricity (energy) provided to and used by people. Therefore, when using a shared connection I/F, it is necessary to distinguish the amount of power supplied from the connection I/F to a specific user from that of general users.

According to the present embodiment, it is possible to grasp the amount of power supplied from the connection I/F 20 to the vehicle 30 of the user 50 based on the amount information detected by the detection unit 33 provided in the vehicle 30. be. Therefore, even when using a shared connection I/F, the amount of power supplied from the connection I/F 20 to the vehicle 30 of the user 50 (specific user) is shared with other users (general users, etc.). It is possible to distinguish and understand. Furthermore, in this case, the installer of the shared connection I/F (parking lot manager, etc.) may transfer the amount of power supplied from that connection I/F to a specific user to other users (general users). There is no need to install new equipment to distinguish and detect the Therefore, for the parking lot manager, even when using a shared connection I/F in the charging service (energy supply service), the equipment cost (introduction cost) can be kept low.

In addition, in this embodiment, as a connection I/F (energy output unit) that can be used in a charging service (energy supply service), a connection I/F installed in a common area such as a common area of an apartment or a parking lot of a shopping center is used. Using the /F (energy output unit) also contributes to increasing the number of connection I/Fs (energy output units) that can be used in the charging service (energy supply service) of this embodiment and expanding the installation area. However, such common areas are often equipped with a detection unit that detects information on the amount of power (energy) supplied within the common area; This is to detect the total amount of power supplied within the area. Therefore, it is difficult for a detection unit provided in a common area to grasp only the amount of power supplied from a connection I/F installed in such a common area.

Also in this embodiment, the amount of power in the parking lot 80, which is a common area including the connection I/F 20, the gate device 82, and various power usage equipment 85, is the amount of power supplied from the connection I/F 20 to the vehicle 30 of the user 50. The power meter 83 measures the total amount of power supply and other power supplies supplied to the gate device 82 and various power utilization equipment 85 at once. Then, the parking lot manager pays the electric power company a fee corresponding to this total amount. In this case, in order for the service management company to pay the parking lot manager (provider) a charge for the amount of power supplied to the vehicle 30 of the user 50 from the connection I/F 20, the power meter 83 must be used. It is necessary to separately grasp only the amount of power supplied from the connection I/F 20 to the vehicle 30 of the user 50.

According to the present embodiment, power supply information (energy supply information) regarding the power supply supplied from the connection I/F 20 to the vehicle 30 of the user 50 is converted into power usage information (energy supply information) detected by the detection unit 33 provided in the vehicle 30. For example, the information is determined based on battery identification information, electric energy, charging start time, charging end time). Therefore, even if the parking lot 80 including the connection I/F 20, the gate device 82, and various power usage equipment 85 is equipped with only equipment (power meter 83) that measures the amount of electricity in a lump, it can be used from the connection I/F 20. The amount of power supplied to the vehicle 30 of the person 50 can be grasped. Therefore, in this embodiment, the parking lot manager, when receiving the provision fee for the power usage of the user 50 who received the power supply from the connection I/F 20, There is no need to install new equipment to detect the amount of power supplied to the system. Therefore, for the parking lot manager, the equipment cost (introduction cost) can be kept low when registering as an energy provider for the charging service (energy supply service).

Further, for the parking lot manager, there is no need for the complicated procedures for installing new equipment as described above, and registration as an energy provider in 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 management association of the condominium, installing new equipment as described above in the common area requires a lot of sectional ownership in the condominium. Procedures such as obtaining consent from individuals are required, which is extremely complicated. According to the present embodiment, such a complicated procedure is not necessary, so that the charging service (energy supply service) connection I/F ( Registration as an energy output unit) will be promoted.

Furthermore, according to the service management system of this embodiment, collection of usage fees from users (billing) and payment of the provision fees to providers (parking lot managers) are performed by operating the charging service (energy supply service). This is done by the service management company that provides the service. Therefore, the provider (parking lot management business) does not need to prepare and manage the facilities necessary to collect usage fees from users, or perform the necessary billing processing, so the service management system of this embodiment can be used. The provided charging service (energy supply service) is highly convenient for parking lot management businesses. Therefore, it is expected that the number of providers (parking lot management businesses) that register for charging services (energy supply services) will increase, as it is easy for providers (parking lot management businesses) to register as providers. This facilitates an increase in the number of energy output units (connection I/F 20) that can be used by users and an expansion of the installation area.

In addition, power usage information (for example, SoC data, battery identification information, power amount, charging start The detection unit 33 that detects the charging time (charging end time) is a facility that is included in most existing vehicles (energy supply target) 30. Therefore, the user 50 is not burdened with additional costs for the detection unit 33.

In addition, in recent years, various information including power usage information (for example, SoC data, battery identification information, electric power amount, charging start time, charging end time) detected by the detection unit 33 provided in the vehicle 30 is provided by each vehicle manufacturer. It is integrated into the vehicle management server 300 and used for various vehicle services. The service management server 100 of this embodiment does not acquire power usage information detected by the detection unit 33 provided in the vehicle 30 from each vehicle 30 individually, but acquires it from the vehicle management server 300 of the vehicle manufacturer. According to this, the service management server 100 can acquire the power usage information detected by the detection unit 33 provided in the vehicle 30 using existing equipment and facilities, so that There is no need to newly install a device that transmits power usage information to the service management server 100. Therefore, the cost burden on the user 50 is further reduced.

On the other hand, since it is assumed that there are users who do not use the service in which the power usage information detected by the detection unit 33 provided in the vehicle 30 is accumulated in the vehicle management server 300 of the vehicle manufacturer, the vehicle 30 of the user 50 A new device that transmits power usage information to the service management server 100 may be newly installed. In this case, for example, the OBD2 ( It may also be connected to a connector for On Board Diagnosis second generation).

Further, in this embodiment, the identification information of the user 50 or the terminal device 51 and the identification information of the vehicle 30 to which power is supplied from the connection I/F 20 are used as the supply target identification information. The service management server 100 receives and acquires the supply identification information from the terminal device 51, but 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 is provided with a function of acquiring identification information of the vehicles 30 entering and exiting the parking lot 80, and the service management server 100 receives the identification information from the gate device 82 as the supply target identification information. The identification information of the vehicle 30 may also be received. In this case, for example, the license plate (vehicle registration number plate) of the vehicle 30 passing through the entrance/exit is captured by an imaging device such as a camera provided in the gate device 82, and the vehicle registration number of the vehicle 30 is recognized from the captured image. can be obtained as identification information. In addition, the identification information of the vehicle may be acquired from an ETC (Electronic Toll Collection System) on-vehicle device mounted on the vehicle.

In the embodiment described above, the terminal device 51 of the user 50 is used to transmit information such as user identification information and provider identification information to the service management server 100; , an external communication unit 32 mounted on the vehicle 30 may be used. Further, in the embodiment described above, information such as power usage information (power supply information) is transmitted using the external communication unit 32 mounted on the vehicle 30. Alternatively, the terminal device 51 of the user 50 may be used.

In addition, the above-mentioned usage fees charged to users and provision fees paid to providers such as parking lot managers may be used instead of or together with electricity usage information (power supply information). , may be calculated by taking other variable parameter information into consideration. For example, even if the amount of power supplied is the same, the usage fee or provision fee may be changed depending on other variable parameter information. In addition to the above-mentioned information, this variable parameter information includes, for example, user attributes (differences in fees paid for services, differences in service grade, differences in age of users, differences in regions to which users belong, etc.), Examples include attributes of the vehicle 30 to which energy is supplied (differences in vehicle manufacturer, differences in additional services related to the vehicle 30, etc.). In addition, as variable parameter information, for example, information on the type of energy output from the energy output unit (different energy sources, whether it is specified clean energy, etc.), the type of energy output unit (from the provider's energy output unit, etc.), Differences in the supply speed of energy supplied to the user's energy supply target (quick charging or not) are also cited.

Furthermore, in this embodiment, a charging service is described in which the connection I/F 20 of a charging stand 25 installed in a parking lot is used to charge the battery 31 of a vehicle 30 parked in a parking space corresponding to the charging stand 25. However, a different charging service may be used. For example, as shown in FIGS. 6A and 6B, when vehicles 30-1 and 30-2 are running in a specific lane where charging is possible among lanes S1 to S3 of an expressway, etc., It may be a charging service that performs charging using connection I/Fs (energy output units) 20D and 20E that are installed wireless interfaces.

In the charging service illustrated in FIG. 6A, multiple types of connection I/ Fs 20D and 20E correspond to the same lane S-1, and the vehicle 30-1 corresponds to one of these connection I/Fs 20D and 20E. , 30-2, the vehicle can be charged by driving in this lane S1. The usage fee at this time may also include an additional fee depending on the type of connection I/ F 20D, 20E (selection I/F) used for charging, as in the embodiment described above.

In addition, in the charging service illustrated in FIG. 6B, different types of connection I/ Fs 20D and 20E correspond to the lanes S1 and S2, and the vehicle 30 corresponds to the connection I/ Fs 20D and 20E of the respective lanes S1 and S2. -1 and 30-2 can be charged by driving in the lanes S1 and S2. The usage fee at this time may also include an additional fee depending on the type of connection I/ F 20D, 20E (selection I/F) used for charging, as in the embodiment described above.

Note that the processing steps and components such as the information processing device, gate device, vehicle-mounted device, terminal device, and server described in this specification can be implemented by various means. For example, these steps and components may be implemented in hardware, firmware, software, or a combination thereof.

Regarding hardware implementation, the above steps and The processing units and other means used to implement the components may include one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processors (DSPDs), programmable logic devices, etc. (PLD), field programmable gate array (FPGA), processor, controller, microcontroller, microprocessor, electronic device, or other electronic unit designed to perform the functions described herein, computer , or a combination thereof.

Also, for firmware and/or software implementations, the means used to implement the components, such as processing units, may include programs (e.g., procedures, functions, modules, instructions) that perform the functions described herein. , etc.). In general, any computer/processor readable medium tangibly embodying firmware and/or software code may be used to implement the steps and components described herein. may be used for implementation. For example, the firmware and/or software code may be stored in memory and executed by a computer or processor, eg, in a controller. The memory may be implemented within the computer or processor, or external to the processor. The firmware and/or software code may also be stored in, for example, random access memory (RAM), read-only memory (ROM), non-volatile random access memory (NVRAM), programmable read-only memory (PROM), electrically erasable PROM (EEPROM), etc. ), flash memory, floppy disks, compact disks (CDs), digital versatile disks (DVDs), magnetic or optical data storage devices, etc. good. 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.

Additionally, the medium may be a non-temporary recording medium. Further, the code of the program may be read and executed by a computer, processor, or other device or apparatus, and its format is not limited to a specific format. For example, the code of the program may be a source code, an object code, or a binary code, or may be a mixture of two or more of these codes.

The description of the embodiments disclosed herein is also provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to this 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 this disclosure. Therefore, this disclosure is not 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.

10: Service management system 20A: Outlet (connection I/F)
20B: Power supply plug (connection I/F)
20C: Wireless power supply device (connection I/F)
20D, 20E: Connection I/F
21: Code images 22, 23: Identification auxiliary image 24: Seal member 25: Charging stand 30: Vehicle 31: Battery 32: External communication section 33: Detection section 40: Power cable 41A: Plug 41B: Power receiving plug 41C: Wireless power receiving device 50: User 51: Terminal device 60: Communication network 80: Parking lot 81: Entrance/exit 82: Gate device 83: Electric energy meter 85: Power usage equipment 100: Service management server 101: Terminal communication section 102: Server communication section 103: Management processing section 104: Storage section 105: Billing processing section 106: Payment processing section 200: Power management device 210: Power distribution equipment 300: Vehicle management server

Claims (5)

1. An information processing device that manages energy usage charges,
   an acquisition unit that acquires selected output unit information indicating a selected output unit selected from a plurality of types of energy output units when supplying energy to an energy supply target of a user;
   a usage fee calculation unit that calculates a usage fee to be charged to the user;
   The information processing device is characterized in that the usage fee calculation unit calculates the usage fee based on the selection output unit information acquired by the acquisition unit.
2. The information processing device according to claim 1,
   The information processing device is characterized in that the types of the energy output unit include a type that is connected by wire to the energy supply target and a type that is wirelessly connected to the energy supply target.
3. The information processing device according to claim 1,
   The information processing device is characterized in that the types of the energy output unit include a plurality of types in which the shapes of terminals connected to the terminal to which energy is supplied are different from each other.
4. The information processing device according to claim 1,
   comprising a provision fee calculation unit that calculates a provision fee to be paid to a provider of energy supplied to the energy supply target;
   The information processing device is characterized in that the provision fee calculation unit calculates the provision fee based on the selection output unit information acquired by the acquisition unit.
5. A system for managing energy usage charges,
   The information processing device according to any one of claims 1 to 4,
   A system comprising: a transmitting device that transmits the selected output unit information to the information processing device.

Images