Charger use management system and management method

Abstract

To provide a charger use management system having higher convenience.SOLUTION: When a user connects a charging connector of a charger to a power supply port of an EV in a charging station, a charger management device 103 receives a connection signal from an EV control device 104. The charger management device scans a user terminal 105, receives a BD (Bluetooth Device) address sent from the user terminal, and transmits, as user terminal-related information, the BD address associated with the charger ID to a management server 101. The management server searches for a user associated with the same registration power supply target information as the received BD address from among a plurality of users recorded in user information. If the associated users are found, a user, among the found users, associated with the same registration target information as the BD address of the highest radio intensity is considered as a user having connected the charging connector to the power supply port of the EV. Then, charging is started.SELECTED DRAWING: Figure 15

Description

[Technical Field]

[0001] The present invention relates to a charger usage management system and a management method. [Background technology]

[0002] JP 2016-520283 A (Patent Document 1) is a background art in this technical field. This publication states, "A method for charging a battery pack of an electric vehicle, comprising: a step of accepting a first group of charging instructions for a first charging station input by a user, the accepting step being performed by a control unit of an on-board vehicle control system; a step of recording the first group of charging instructions for the first charging station in a memory; a step of determining that the electric vehicle is located at the first charging station, the determining step being performed by the control unit; and a step of charging the battery pack of the electric vehicle according to the first group of charging instructions in response to the determination, and charging the battery pack of the electric vehicle according to an initial group of charging instructions if the electric vehicle is located at another charging station that does not correspond to the first group of charging instructions" (see claim 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-520283 Summary of the Invention [Problem to be solved by the invention]

[0004] According to the technology of Patent Document 1, when a charging station cannot receive the first group of charging instructions or the initial group of charging instructions from the control unit of the on-board vehicle control system of the electric vehicle, the user needs to input instructions directly to the charging station in order to charge the electric vehicle. In view of such circumstances, a more convenient charger usage management system is desired.

[0005] Therefore, the present invention provides a more convenient charger usage management system. [Means for solving the problem]

[0006] In order to solve the above problems, for example, the configurations described in the claims are adopted. The present application includes a plurality of means for solving the above problems, and examples thereof include: a first management device that manages the usage status of the charger; and A second management device that manages charging of the electric vehicle from the charger, a detection unit that detects that a charging unit of the charger and a power supply unit of the electric vehicle are in a chargeable state; a charge initiation unit that initiates charging of the electric vehicle from the charger; a power supply target information acquisition unit that acquires power supply target information, which is at least one of information related to the electric vehicle and information related to a user of the electric vehicle; a second management device comprising: Equipped with When the detection unit detects that the charging unit of the charger and the power supply unit of the electric vehicle are in a chargeable state and when the power supply target information acquisition unit acquires the power supply target information, the second management device transmits the acquired power supply target information to the first management device; When the received power supply target information corresponds to pre-recorded registered power supply target information, the first management device transmits, to the second management device, charging start information that causes the charging start unit to start charging the electric vehicle from the charger. It is characterized by providing a charger usage management system. [Effects of the Invention]

[0007] According to the present invention, a more convenient charger usage management system can be provided. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 shows an example of the overall configuration of a charger usage management system 100. [Figure 2] Figure 2 shows an example of the hardware configuration of a management server. [Figure 3] FIG. 3 shows an example of the hardware configuration of the vehicle management device. [Figure 4] FIG. 4 shows an example of the hardware configuration of the charger management device. [Figure 5] FIG. 5 shows an example of the hardware configuration of an EV control device. [Figure 6] FIG. 6 shows an example of the hardware configuration of a user terminal. [Figure 7] FIG. 7 shows an example of user information. [Figure 8] FIG. 8 is an example of the charger management information. [Figure 9] FIG. 9 is an example of OEM user information. [Figure 10] FIG. 10 shows an example of a pre-user association flow related to the management server. [Figure 11] FIG. 11 shows an example of a flow of advance user association related to the charger management device. [Figure 12] FIG. 12 shows an example of a charger usage management flow related to the management server. [Figure 13] FIG. 13 is an example of a charger usage management flow related to the charger management device. [Figure 14] FIG. 14 is an example of a sequence diagram of advance registration according to an embodiment. [Figure 15] FIG. 15 is an example of a sequence diagram of auto check-in according to an embodiment. [Figure 16] FIG. 16 is an example of a sequence diagram of auto check-in according to another embodiment. [Figure 17] FIG. 17 is an example of a sequence diagram of advance registration according to another embodiment. [Figure 18]FIG. 18 is a sequence diagram illustrating an example of an auto check-in according to another embodiment. [Figure 19] FIG. 19 is an example of a sequence diagram of auto check-in according to another embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, embodiments will be described with reference to the drawings. In each drawing, components having the same functions may be designated by reference numerals and may not be described in detail.

[0010] FIG. 1 is a diagram illustrating an example of a configuration of a charger usage management system 100 according to an embodiment. In this embodiment, the present invention will be described using as an example a configuration in which a user of an electric vehicle (EV) registered in the charger usage management system 100 can avoid the complicated procedures at a charging station and simply connect the charging unit of the charger to the power supply unit of the EV so that charging is automatically started (hereinafter, sometimes referred to as "auto check-in").

[0011] [Charger usage management system] The charger usage management system 100 is configured to include one or more management servers 101 and one or more charger management devices 103. The charger usage management system 100 additionally includes one or more vehicle management devices 102, one or more EV control devices 104, and one or more user terminals 105. The management server 101 is an example of a first management device in the present technology. The vehicle management device 102 and the charger management device 103 are each an example of a second management device in the present technology.

[0012] One or more vehicle management devices 102 and one or more charger management devices 103 are each configured to be connectable to one or more management servers 101 via a network. One or more user terminals 105 are each configured to be connectable to one or more management servers 101 and one or more charger management devices 103 via a network. An EV control device 104 that controls an EV is configured to be connectable to one or more vehicle management devices 102 via a network. The network may be wired or wireless, and each terminal can send and receive information via the network.

[0013] The management server 101, vehicle management device 102, charger management device 103, EV control device 104, and user terminal 105 may each be a mobile device such as a smartphone, tablet, mobile phone, or personal digital assistant (PDA), or a wearable device such as glasses, a head-mounted device, a wristwatch, or clothing. These devices may also be stationary or mobile computers, or servers located on the cloud or a network. These devices may also function as virtual reality (VR) devices, augmented reality (AR) devices, or mixed reality (MR) devices. Alternatively, these devices may be a combination of multiple devices. For example, a combination of one smartphone and one wearable device may logically function as a single device. Other information processing devices may also be used.

[0014] Each of the above devices and terminals includes a processor that executes an operating system, applications, programs, etc.; a main storage device such as RAM (Random Access Memory); an auxiliary storage device such as an IC card, hard disk drive, SSD (Solid State Drive), or flash memory; a communication control unit such as a network card, wireless communication module, or mobile communication module; an input device such as a touch panel, keyboard, mouse, audio input device, or input device that detects motion by capturing images from a camera; and an output device such as a monitor, display, printer, audio output device, or oscillator. The input device may include a thermometer, a GPS, a gyro sensor, an acceleration sensor, or other sensor. The output device may be a device or terminal that transmits information to be output to an external monitor, display, printer, or device.

[0015] The main memory stores various programs and applications (software modules), and the processor executes these programs and applications to realize each functional element of the overall system. Each module may be an independent program or application, or may be implemented as a subprogram or function within a single integrated program or application. Each module may also be implemented as hardware (hardware modules) by integrating circuits or using a microcomputer. Furthermore, each module may be located on a single terminal (including a management server) or may be distributed across two or more terminals (including management servers) interconnected via a network.

[0016] In this specification, each module is described as a subject that performs processing, but in reality, the processing is carried out by a processor that processes various programs, applications, etc.

[0017] The auxiliary storage device stores various databases (DB). A "database" is a set of data that has been organized and collected so that it can accommodate any data manipulation (e.g., extraction, addition, deletion, overwriting, etc.) from a processor or an external computer. The auxiliary storage device is a functional element (storage unit) that stores one or more sets of data. There are no limitations on how the database is implemented; for example, it may be a database management system, spreadsheet software, or a text file such as XML or JSON.

[0018] [Administration Server] The management server 101 is an element that manages the entire charger usage management system 100. The management server 101 manages the usage status of the chargers.

[0019] FIG. 2 illustrates an example of the hardware configuration of the management server 101. The management server 101 is configured, for example, by a desktop PC or a server deployed on the cloud. The management server 101 includes a main storage device 201 and an auxiliary storage device 202. The management server 101 also includes the processor 203, input device 204, output device 205, and communication control unit 206 as described above.

[0020] The main memory device 201 stores programs and applications such as a management module 211, a power supply target information acquisition module 212, an authentication module 213, and a charging permission module 214. Each functional element of the management server 101 is realized by the processor 203 executing these programs and applications stored in the main memory device 201.

[0021] The auxiliary storage device 202 stores information necessary for the operation of the management server 101. The auxiliary storage device 202 stores, for example, user information 700, charger management information 800, etc. Details of this information will be described later.

[0022] Each functional element of the management server 101 will be described. The management module 211 manages the operation of the charger management device 103. The management module 211 cooperates with the EV management module 311 of the charger management device 103 to control the basic operation for auto check-in of the charger management device 103. The management module 211 also cooperates with the user execution module 611 of the user terminal 105 to control the basic operation for authentication of auto check-in by the user terminal 105.

[0023] The power supply target information acquisition module 212 acquires information about the power supply target that the charger is attempting to charge from the vehicle management device 102 or the charger management device 103. Specifically, the power supply target information acquisition module 212 acquires power supply target information, which is at least one of information related to the EV and information related to the user of the EV. The power supply target information acquisition module 212 also determines whether the acquired power supply target information corresponds to pre-recorded registered power supply target information.

[0024] The authentication module 213 is an element for receiving authentication for an EV user to charge the EV. The authentication module 213 cooperates with the user charging management module 612 of the user terminal 105 to perform authentication.

[0025] The charging permission module 214 transmits charging start information to the charger management device 103 .

[0026] [Vehicle management device] The vehicle management device 102 is a device managed by a service provider that provides connected services related to EVs, and is a device of the service provider that uses the charger usage management system 100. The vehicle management device 102 is configured, for example, by a server deployed on the cloud. The vehicle management device 102 communicates with an EV control device 104, which will be described later. In this embodiment, the vehicle management device 102 may also be referred to as an OEM server.

[0027] Connected services are EVs that connect with connected cars, which are equipped with information and communication technology (ICT) terminals, via information and communication to provide various services. Examples of connected services include emergency support services, battery management services, and services that provide access information to charging points. Service providers typically provide these services to users through paid or free mobile applications. The vehicle management device 102 is configured to be able to communicate with a user terminal 105 owned by the user of the connected car via the mobile application.

[0028] FIG. 3 illustrates an example of the hardware configuration of the vehicle management device 102. The vehicle management device 102 includes a main memory device 301 and an auxiliary memory device 302. The vehicle management device 102 also includes a processor 303, an input device 304, an output device 305, and a communication control unit 306 as described above.

[0029] The main memory device 301 stores programs and applications such as an EV management module 311, a power supply target information transmission module 312, and an authentication module 313. Each functional element of the vehicle management device 102 is realized by the processor 303 executing these programs and applications stored in the main memory device 301.

[0030] The auxiliary storage device 302 stores information necessary for the operation of the vehicle management device 102. For example, the auxiliary storage device 302 stores OEM user information 900, OEM service information 520, charging management information 530, etc. Details of this information will be described later. This information may be some or all of the information related to the vehicle management device 102, such as the OEM service information 520 and charging management information 530 stored in the EV control device 104 described later.

[0031] Each functional element of the vehicle management device 102 will be described. The EV management module 311 manages the operating status of the connected car. For example, the EV management module 311 cooperates with the driving control module 511 and the charging control module 512 of the EV control device 104 to control the operations performed to provide connected services.

[0032] The power supply target information transmission module 312 transmits power supply target information to the management server 101 when the charger usage management system 100 is used. The power supply target information transmission module 312, for example, acquires power supply target information from the OEM user information 900 and transmits it to the management server 101. If necessary, the power supply target information transmission module 312 can, for example, associate information about the charger 410 acquired from the EV control device 104 that corresponds to the power supply target information with the power supply target information and transmit it to the management server 101.

[0033] The authentication module 313 is an element for receiving authentication from the EV user for charging the EV. The authentication module 313 cooperates with the connected service module 613 of the user terminal 105 to perform authentication.

[0034] [Charger management device] The charger management device 103 is an element that manages charging from the charger to the electric vehicle. FIG. 4 illustrates an example of the hardware configuration of the charger management device 103.

[0035] The charger management device 103 is installed in, for example, a charging station. The charging station is provided with a parking area (not shown) for parking EVs, the charger management device 103, a charger 410, a Bluetooth (registered trademark) board 420, a power meter 111, an external power supply 112, and the like. The charger 410 of this embodiment has a built-in power meter 111 and is connected to the external power supply 112 via the power meter 111. The Bluetooth board 420 is provided in, for example, each charger 410. The Bluetooth board 420 is connected to the charger management device 103 by wire or wirelessly and is configured to be able to send and receive information to and from the charger management device 103. For example, one charger management device 103 may be provided for one charger 410, or one for two or more chargers 410.

[0036] Charger 410 may be any of various chargers capable of supplying power to an EV (more specifically, the EV's drive battery). Hereinafter, the EV's drive battery may be simply referred to as a battery or the like. For example, charger 410 is not limited to a normal charger with a rated output of less than approximately 10 kW (e.g., 3 to 6 kW), or a rapid charger with a rated output of approximately 10 kW or more (e.g., 50 kW). Charger 410 may be a contact charger (also called a wired charger, etc.) that charges by physically connecting the charger's charging unit to the EV's power supply unit via a power line, or a contactless charger (also called a wireless charger, etc.) that charges by contactlessly connecting the charger's charging unit to the EV's power supply unit using a charging coil or the like without using a power line.

[0037] The Bluetooth board 420 is a circuit board for performing communication in accordance with the Bluetooth (registered trademark) standard. The Bluetooth board 420 uses the 2.4 GHz band, which is an ultra-high frequency wave, and can connect to multiple surrounding Bluetooth boards. The Bluetooth board 420 may also be a package board equipped with a protocol stack that complies with the Bluetooth specifications.

[0038] The Bluetooth standard defines radio wave intensity levels as three classes (power classes), with the higher the radio wave intensity, the wider the radio wave coverage area. On the other hand, for the same class, the higher the radio wave intensity, the closer the Bluetooth terminal with which you are communicating is considered to be. The radio wave coverage distance is up to 100 m for Class 1, up to 10 m for Class 2, and up to 1 m for Class 3, and the power class of the Bluetooth board 420 in this embodiment is, for example, Class 2.

[0039] The charger management device 103 can be configured by, for example, a microcomputer. The charger management device 103 includes a main memory device 401 and an auxiliary memory device 402. The charger management device 103 also includes the processor 403, input device 404, output device 405, camera 406, and communication control unit 407 as described above. The communication control unit 407 includes a Bluetooth communication module that enables Bluetooth communication and can grasp the Bluetooth radio wave strength.

[0040] The main memory device 401 stores programs and applications such as a charger management module 411, a connector connection status detection module 412, a power supply target information acquisition module 413, and a charging start module 414. Each functional element of the charger management device 103 is realized by the processor 403 executing these programs and applications stored in the main memory device 401.

[0041] Each functional element of the charger management device 103 will be described. The charger management module 411 controls the basic operation of the charger management device 103. The charger management module 411 controls the basic operation of the charger management device 103 for charging that does not rely on auto check-in, for example.

[0042] Connector connection status detection module 412 detects that the charging unit of charger 410 and the power supply unit of the EV are in a chargeable state (i.e., detects connection). Connector connection status detection module 412 is an example of the detection unit of the present invention. Specifically, for example, if charger 410 is a contact charger, the charging cable of charger 410 includes a power transmission cable and a communication cable. Therefore, when the charging connector (an example of a charging unit) of charger 410 and the power supply port (also called an inlet, an example of a power supply unit) of the EV are properly fitted and connected, connector connection status detection module 412 can detect the connection of the connector by detecting the electrical connection between the charging connector and the power supply port.

[0043] Alternatively, for example, if charger 410 is a contactless charger, charger 410 and EV each have a coil for wireless power transmission. Connector connection status detection module 412 detects that a charging state has been achieved when the relative position of the power transmitting coil (an example of a charging unit) of charger 410 and the power receiving coil (an example of a power supply unit) of the EV becomes suitable for wireless power transmission. Regarding the detection of the charging state, the EV may detect a connection, transmit connection detection information by the EV to connector connection status detection module 412, and then receive the transmitted connection detection information, thereby allowing connector connection status detection module 412 to detect that a charging state has been achieved.

[0044] The power supply target information acquisition module 413 acquires power supply target information. The power supply target information is at least one of information related to the charger 410 and the EV in a chargeable state, and information related to the charger 410 and the user of the EV in a chargeable state. The information related to the EV may be any information that can identify the EV, such as a VIN code. The information related to the user of the EV may be any information that can identify the user of the EV, such as a BD (Bluetooth Device) address of the user terminal 105 owned by the user in this embodiment.

[0045] The charging start module 414 starts charging the charger 410 that is in a chargeable state. The charging start module 414 starts charging the electric vehicle from the charger 410.

[0046] The auxiliary storage device 402 stores information necessary for operation. For example, the auxiliary storage device 402 stores charger management information 800 and the like. Details of this information will be described later. This information may be part or all of the information related to the charger management device 103 among the charger management information 800 and the like stored in the management server 101.

[0047] [EV control device] The EV control device 104 is an EV electronic control unit (ECU) that is installed in the EV. The EV control device 104 is configured by, for example, a microcomputer, and controls the basic operations of the EV.

[0048] FIG. 5 illustrates an example of the hardware configuration of the EV control device 104. The EV control device 104 includes a main memory device 501 and an auxiliary memory device 502. The EV control device 104 also includes the processor 503, input device 504, output device 505, camera 506, and communication control unit 507 as described above.

[0049] The main memory device 501 stores programs and applications such as a driving control module 511 and a charging control module 512. The functional elements of the EV control device 104 are realized by the processor 503 executing these programs and applications stored in the main memory device 501.

[0050] Each functional element of the EV control device 104 will now be described. The driving control module 511 manages the operation of the EV. The driving control module 511 controls the driving operations of the EV, such as engine control, safety device control, and power steering control.

[0051] The charging control module 512 controls the operation of charging the EV battery. For example, the charging control module 512 detects connections between charging connectors of various charging methods and power ports, transmits charging permission signals, current commands, and battery information from the EV side to the charging connector side, and receives charging operation status information from the charger side.

[0052] Information used for operation is stored in the auxiliary storage device 502. For example, the auxiliary storage device 502 stores vehicle management information 510, OEM service information 520, charging management information 530, and the like. Vehicle management information 510 is various information used for driving an EV, such as vehicle information and driving history information. OEM service information 520 is various information used when receiving connected services in a connected car, which is one of the electric vehicles of this embodiment. Charging management information 530 is information related to the charging of the EV's driving battery, such as status information on the driving battery and battery charge / discharge information. This information may be some or all of the information related to the EV control device 104, such as the OEM user information 900, OEM service information 520, and charging management information 530 stored in the vehicle management device 102.

[0053] [User device] FIG. 6 shows an example of the hardware configuration of the user terminal 105. The user terminal 105 is, for example, a user terminal 105 used by a user who owns an EV, and in this embodiment is a smartphone. However, the user terminal 105 may be a mobile terminal such as a tablet or notebook PC in addition to a smartphone. The user terminal 105 includes a main memory device 601 and an auxiliary memory device 602. The user terminal 105 also includes the processor 603, input device 604, output device 605, camera 606, and communication control unit 607 as described above. The user terminal 105 is a Bluetooth device with a Bluetooth board in the communication control unit 607.

[0054] The main memory device 601 stores programs and applications such as a user execution module 611 and a user charging management module 612, and the processor 603 executes these programs and applications to realize each functional element of the user terminal 105.

[0055] The user execution module 611 controls basic operations for using the user terminal 105. The user execution module 611 manages basic operations of the user terminal 105 as a smartphone, such as Internet connection and Bluetooth communication, for example.

[0056] The user charging management module 612 controls basic operations for using the charger usage management system 100. The user charging management module 612 cooperates with the management module 211 of the management server 101 to control basic operations of the user terminal 105, for example, when registering a user in the charger usage management system 100 or authenticating auto check-in.

[0057] Information necessary for operation is stored in the auxiliary storage device 602. For example, user information 700, OEM user information 900, etc. are stored in the auxiliary storage device 602. This information may be part or all of the user information 700 stored in the management server 101 or the OEM user information 900 stored in the vehicle management device 102.

[0058] 7 to 9 show various types of information stored in the management server 101, the vehicle management device 102, the charger management device 103, or the like. Although not limited to this, it is assumed that some or all of this information is stored in a JSON format file. Some or all of this information may be configured to be stored in a relational database or a non-relational database. Furthermore, the implementation method of this various information is not limited to that shown in this embodiment. This various information may be realized in a form that is distributed and allocated to multiple database servers or cloud applications.

[0059] FIG. 7 is an example of user information 700. The user information 700 is information about a user who uses the charger usage management system 100. The user information 700 is typically stored in the auxiliary storage device 202. The user information 700 includes, for example, a user ID, a user name, a BD address, a VIN code, predetermined charging information, payment information, a charger ID, usage date and time information, usage fee information, password information, and authentication information such as personal identification information, and values ​​such as those shown as sample values ​​720 are input into the respective items 710.

[0060] A user ID is a code assigned to each user to identify them, and is automatically generated as a hash value, etc. Information about each user is basically linked to this user ID. The user name and payment information are the name or title of the user (including natural persons and corporations; the same applies below) and information related to payment, respectively. Authentication information (password information and identity verification information) is authentication information used to log in to the reservation app to reserve and use a charging space, and to verify the user's identity, and is not limited to password information, identity verification information, etc.

[0061] The BD address is information that can be acquired and recorded via a Bluetooth board during prior user association using the user terminal 105 (smartphone). The BD address is an example of registered power supply target information. The BD address is a 48-bit device-specific address used to identify a Bluetooth-enabled device.

[0062] The VIN code is information provided by the user through user registration and stored. The VIN code is an example of registered power supply target information. The specified charging information is the charging conditions for charging by auto check-in. The specified charging information is information set by the user through user registration. Note that the VIN code and specified charging information are additional information and are not necessarily required.

[0063] The charger ID, usage date and time information, and usage fee information are information received from the charger management device 103, and the contents thereof will be described later. The user information 700 is not limited to this example and may include, for example, other information.

[0064] FIG. 8 is an example of the charger management information 800. The charger management information 800 is information related to the charger management device 103, and is typically stored in the auxiliary storage device 402. The charger management information 800 includes, for example, a charger ID, information such as latitude and longitude as location information of the charger, usage date and time information, usage fee information, and the like, and values ​​such as those shown as sample values ​​820 are input into the respective field names 810.

[0065] The charger ID is a code assigned to each charger to identify it, and is automatically generated as a hash value, etc. The location information is information that indicates the location of the charger or charging station, and typically includes information about latitude and longitude.

[0066] The usage date and time information is information about the date and time when auto check-in by the charger usage management system 100 was used, and is acquired via the clock function of the processor 403. The usage fee information is information about the usage fee (including the charging fee) when auto check-in by the charger usage management system 100 was used, and is calculated by the charger management module 411, for example. The charger management information 800 is not limited to this example and may include, for example, other information.

[0067] FIG. 9 is an example of OEM user information 900. The OEM user information 900 is information about users who use connected services. The OEM user information 900 is typically stored in the auxiliary storage device 302. The OEM user information 900 includes, for example, a user ID, a user name, EV vehicle information, a VIN code, information such as latitude and longitude as EV location information, battery charging information, connector connection information, and the like, and values ​​such as those shown as sample values ​​920 are input into the respective items 910.

[0068] The user ID is a symbol assigned to each user to identify them, and is automatically generated as a hash value, etc. Information about each user is basically linked to this user ID. The user name is information about the name or title of the user (including natural persons and corporations; the same applies below). EV vehicle information is information about the name of the EV (body). The VIN code is the Vehicle Identification Number (VIN), and consists of 17 alphanumeric characters. The user name and VIN code are recorded, for example, when a user registers for a connected service.

[0069] The EV location information is location information obtained from a GPS installed in the EV. The battery charging information is information indicating the charging state of the battery (for example, State of Charge (SOC)). The connector connection information indicates information regarding the connection state between the EV's power inlet and the charger's charging connector, and is, for example, binary information indicating connected / disconnected. The EV location information, battery charging information, and connector connection information are acquired and stored by the vehicle management device 102 connecting to the EV control device 104. The OEM user information 900 is not limited to this example and may include, for example, other information.

[0070] [Charger usage management method] According to the charger usage management system 100 described above, by registering the user in advance, it is possible to avoid the complicated procedures at the charging station, and to realize auto-check-in, which allows charging of the EV to start automatically by simply connecting the charging unit of the charger and the power supply unit of the electric vehicle so that charging is possible.

[0071] 1. Automatic check-in using a regular EV First, the management of charger usage by advance user registration and auto check-in between the management server 101, charger management device 103, and user terminal 105 without going through the vehicle management device 102 will be explained. Below, for each process, the program processing flow will be explained in outline based on a flow diagram. After that, the details of each process and the data sent and received will be explained based on a sequence diagram.

[0072] 1-1A. Preliminary user association flow FIG. 10 shows an example of a preliminary user association flow 1000 related to the management server, and FIG. 11 shows an example of a preliminary user association flow 1100 related to the charger management device.

[0073] It is assumed that the user has downloaded a charger usage application provided by the charger usage management system 100 using the user terminal 105 (a smartphone in this example) and has registered information other than the registered power supply target information. This charger usage application is not limited to use for the auto check-in function, and may be, for example, an application for using the charging stations and chargers 410 registered in the charger usage management system 100. The charger usage application may, for example, be capable of performing procedures for using the charger 410 on the spot or making a reservation for use of the charger 410 in advance. The user registration information before advance user association with this electrical appliance usage application includes, for example, the user name, payment information, password information, and personal identification information among the information shown in the user information 700. The user registration information before advance user association does not include the registered power supply target information.

[0074] Charger 410 also complies with the CHAdeMO standard, which is popular in Japan and other countries. For example, a CHAdeMO-based quick charger has 10 pins at the connector, with the two largest pins connected to the power line, the other two pins connected to the CAN signal line, and the remaining pins connected to analog control lines used to check the connector connection and exchange charge / discharge control information. However, when CHAdeMO-based charger 410 is ready to charge an EV, it cannot directly obtain the identification information of the EV or the charger.

[0075] For this reason, for example, CHAdeMO chargers are not capable of so-called plug-and-charge or auto-charge, which automatically starts charging an EV simply by connecting the charger's charging section to the electric vehicle's power supply section. This also applies to chargers that comply with general charging connector standards such as SAE J1772 (IEC 62196-2 type 1), IEC 62196-2 type 2, and AC GB / T, with the exception of some special chargers.

[0076] The management server 101 also monitors the usage status of the charger and obtains usage information of the charger 410 from the charger management device 103 at predetermined time intervals. The charger management device 103 also transmits charger management information 800 and the like to the management server 101 every time a predetermined event occurs, such as connection with an EV.

[0077] Under these conditions, at a charging station, the user first uses a charger usage application on the user terminal 105 to initiate a charger usage procedure (smartphone operation) for a specific charger 410. After that, the user connects the charging connector of the charger 410 for which usage has been completed to the EV's power supply port. Note that the charging connector of the charger 410 is normally unlocked, and can be connected to the EV's power supply port without any special procedures. The usage procedure using the application may also be performed after the charging connector is connected.

[0078] The connector connection status detection module 412 of the charger management device 103 then detects that the charging connector of the charger 410 and the power supply unit of the EV are in a state where charging is possible (S1110). More specifically, for example, the charger 410 first inquires about the operation status of the EV via a CAN signal, and the EV then sends information about the charging conditions to the charger 410. The information about the charging conditions includes, for example, the SOC, charging current value, and maximum charging voltage. Next, the charger 410 transmits information about the charger to the EV. After that, a safety check is performed between the EV and the charger 410 via an analog control line, and it is confirmed that charging is possible. For example, the connector connection status detection module 412 can detect the charging possible state according to such a predetermined protocol.

[0079] Next, the user requests the start of charging by using the charger usage application on the user terminal 105 and selecting a "start charging" button, for example. This request signal includes, for example, information for identifying the charger (for example, a charger ID). When the management server 101 receives the request to start charging from the user terminal 105 (S1010), it transmits a request to start charging to the charger management device 103 (S1020).

[0080] When the charger management device 103 receives a charging start request from the management server 101 (S1120), the charging start module 414 starts charging the EV from the charger according to the normal procedure for managing the use of the charger 410 using a smartphone (S1130).

[0081] Charging by charger 410 may be automatically stopped, for example, when a predetermined charging time has elapsed. Charging by charger 410 may also be automatically stopped, for example, when a predetermined state of charge (SOC) is reached. Alternatively, charging may be stopped when the user performs a charging stop operation using a charger usage application.

[0082] At this time, the power supply target information acquisition module 413 of the charger management device 103 acquires the power supply target information (S1140). In this embodiment, the power supply target information acquisition module 413 acquires, as the power supply target information, information on detectable terminals present in the vicinity of the charger 410. Here, via the Bluetooth board 420, the BD address of the user terminal 105 is acquired as information on detectable terminals present in the vicinity of the charger 410.

[0083] The BD address of a Bluetooth terminal can be obtained, for example, by connecting at level 1 (no security, no user operation) of security mode 1 of the Bluetooth standard.

[0084] If there are multiple connectable devices near the charger 410, the BD address of the device with the strongest radio wave intensity can be acquired as the power supply target information, assuming that the user terminal 105 is located closest to the charger 410. If multiple terminals are detected, the power supply target information acquisition module 413 may acquire all or a predetermined number of BD addresses. The power supply target information acquisition module 413 can similarly acquire BD addresses for Bluetooth terminals other than smartphones as the user terminal 105.

[0085] The charger management device 103 transmits the power supply target information to the management server 101 (S1150). Here, the charger management device 103 transmits the power supply target information to the management server 101 together with the charger ID of the charger 410 that has become available for charge. The charger management device 103 transmits the acquired BD address to the management server 101 as the power supply target information.

[0086] The management server 101 receives the power supply target information and the charger ID (S1030). The management server 101 associates the received power supply target information with the user information that sent the charge request via the charger ID (S1040). Specifically, the management server 101 records the received power supply target information as registered power supply target information of the user information that sent the charger request related to the charger ID. This associates the user who uses the charger usage application with the user terminal 105 that the user uses. As a result, for example, user authentication can be performed by acquiring the BD address of the Bluetooth terminal based on the BD address as the registered power supply target information.

[0087] 1-1B. Preliminary user association sequence 14 is an example of a sequence diagram 1400 of advance registration according to one embodiment. Data transmitted and received between devices will be described in more detail with reference to this sequence diagram.

[0088] The sequence diagrams in this application are Unified Modeling Language (UML) sequence diagrams. In the diagrams, solid black arrows indicate the transmission of synchronous messages synchronized with the execution of the destination lifeline. Dotted black arrows indicate the transmission of response messages, which are return values ​​in response to a call from the destination to the sender. Boxes (activation boxes) provided along the lifelines extending vertically from each element 101 to 106 are execution specifications indicating that the element in question is in an execution state.

[0089] Furthermore, although not limited thereto, unless otherwise specified, communication between the management server 101 according to the present technology and the vehicle management device 102, charger management device 103, and user terminal 105 may be based on the OCPP (Open Charge Point Protocol), and other communications may be based on the HTTP (HyperText Transfer Protocol) protocol or the HTTPS (Hytertext Transfer Protocol Secure) protocol. In the case of OCPP, the management server 101 may transmit a charging start permission signal based on, for example, a communication protocol using Websocket (the same applies hereinafter).

[0090] As explained in the flow, the user first uses the charger usage application of the user terminal 105 at the charging station to start the charger usage procedure (smartphone operation) for a specific charger 410.

[0091] Then, in step 1, the user connects the charging connector of the charger 410 to the power inlet of the EV at the charging station (Connect). As a result, the charger management device 103 receives a connection signal from, for example, the EV (EV control device 104).

[0092] In step 2, the user 106 performs an operation to start charging (Start Charging) on ​​the smartphone (an example of the user terminal 105). Then, in step 3, the smartphone 105 transmits a request signal to start charging (Request to start charging) to the management server 101. This signal includes a charger ID that identifies the charger 410.

[0093] In step 4, the management server 101 sends a remote start processing signal for charging (Send RemoteStartTransaction) to the charger management device 103. Accordingly, in step 5, the charging start module 414 of the charger management device 103 starts charging the EV (EV control device 104).

[0094] In step 6, the power supply target information acquisition module 413 of the charger management device 103 scans the user terminal 105 (Scan a device). In step 7, the charger management device 103 receives the BD address sent from the user terminal 105 (BD address). In step 8, the charger management device 103 transmits the BD address to the management server 101 as information related to the user terminal 105 (BD address). At this time, the charger management device 103 transmits the BD address in association with a charger ID that identifies the charger 410.

[0095] The management server 101 receives the charger ID and the BD address in association with each other. In step 9, the management server 101 links the user who performed the charging start operation on the smartphone in step 2 with the received BD address via the charger ID, and records the link in the user information 700 (Link the BD address to the charging user). In other words, the BD address is recorded as registered power supply target information. This makes it possible to record in the user information 700 the unique information of the user terminal 105 that can be obtained at the charging station.

[0096] 1-2A. Charger usage management flow As described above, by linking the unique information of the user terminal 105, which can be obtained in advance at the charging station, to the user information 700, automatic check-in can be realized from the next time.

[0097] FIG. 12 shows an example of a charger usage management flow 1200 related to the management server 101, and FIG. 13 shows an example of a charger management device advance user association flow 1100 related to the charger management device 103.

[0098] First, the user connects the charging connector of the charger 410 to the power inlet of the EV at the charging station. At this time, the user does not need to operate the charger usage application. Then, the connector connection status detection module 412 of the charger management device 103 detects that the charging connector of the charger 410 and the power supply unit of the EV are in a state where charging is possible (S1210).

[0099] At this time, even if the charger management device 103 detects that the EV is in a chargeable state, it does not start charging. For example, even if the charger management device 103 receives a charging permission signal from the power supply unit of the EV, it does not start charging in accordance with the signal from the EV.

[0100] Then, the power supply target information acquisition module 413 of the charger management device 103 acquires the power supply target information (S1220). The power supply target information acquisition module 413 acquires the BD address of the user terminal 105 as information about detectable terminals present in the vicinity of the charger 410.

[0101] The charger management device 103 transmits the acquired power supply target information to the management server 101 (S1230). Here, the charger management device 103 transmits the acquired BD address together with the charger ID to the management server 101 as power supply target information.

[0102] The BD address of a Bluetooth terminal can be obtained, for example, by connecting at level 1 (no security, no user operation) of security mode 1 of the Bluetooth standard.

[0103] The management server 101 receives the power supply target information and the charger ID (S1310). If the received power supply target information corresponds to the pre-recorded registered power supply target information, the management server 101 transmits charging start information to the charger management device 103 (S1320). More specifically, the management server 101 compares the received power supply target information with the registered power supply target information. If the power supply target information corresponds to the registered power supply target information, the management server 101 determines that the user of the EV that is in a chargeable state with the charger management device 103 is the user linked to the registered power supply target information that corresponds to the power supply target information in the user information 700. This allows the management server 101 to confirm the user who uses auto check-in. The management server 101 then permits the charger management device 103 to charge the EV at the charger identified by the charger ID.

[0104] The charger management device 103 receives the charging start signal transmitted from the management server 101 (S1240). In response, the charging start module 414 of the charger management device 103 starts charging the EV (S1250).

[0105] This allows the user to use auto check-in, which automatically starts charging the EV, simply by connecting the charging unit of the charger and the power supply unit of the electric vehicle so that charging is possible, with the management server 101. Furthermore, when charging at a charging station, the user does not perform any special processing to use the charger usage management system 100, but the management server 101 can identify the user based on the power supply target information and can charge the user for the use of the charger 410.

[0106] Charging by charger 410 may be automatically stopped, for example, when a predetermined charging time has elapsed. Charging by charger 410 may also be automatically stopped, for example, when a predetermined state of charge (SOC) is reached. Alternatively, charging may be stopped when the user performs a charging stop operation using a charger usage application.

[0107] In addition, in the above step S1220, for example, if the power supply target information acquisition module 413 acquires multiple pieces of power supply target information, the power supply target information acquisition module 413 can transmit all of the information or a predetermined number of pieces of power supply target information with high radio wave strength to the management server 101 in step S1230, together with the radio wave strength information.

[0108] In this case, in step S1310, the management server 101 receives multiple pieces of power supply target information together with their radio wave strength information. Then, in step S1320, the management server 101 compares the received multiple pieces of power supply target information with the registered power supply target information and extracts the power supply target information that corresponds to the registered power supply target information. At this time, if there is only one piece of power supply target information that corresponds to the registered power supply target information, it can be determined that the user linked to the registered power supply target information that corresponds to that power supply target information is the user who will use auto check-in. On the other hand, if there is multiple pieces of power supply target information that correspond to the registered power supply target information, it can be determined that the user linked to the registered power supply target information that corresponds to the power supply target information with the highest radio wave strength among the multiple pieces of power supply target information is the user who will use auto check-in.

[0109] On the other hand, in the above step S1220, for example, if the power supply target information acquisition module 413 acquires information on multiple power supply targets, the power supply target information acquisition module 413 may assume that the user terminal 105 is located closer to the charger 410 than other Bluetooth devices and acquire the BD address of the device with the strongest radio wave intensity as the power supply target information. In this case, if the power supply target information acquisition module 413 detects multiple terminals, it may acquire all or a predetermined number of BD addresses and transmit them to the management server 101. The power supply target information acquisition module 413 can similarly acquire BD addresses for Bluetooth terminals other than smartphones as the user terminal 105.

[0110] Note that charging by the charger 410 may be configured to be performed based on, for example, predetermined charging conditions recorded in advance in the user information 700. For example, if predetermined charging conditions are recorded in the user information 700, the management server 101 may transmit the predetermined charging conditions together with transmitting charging start information to the charger management device 103 in S1320.

[0111] Furthermore, if the power supply target information acquisition module 413 is unable to acquire the power supply target information or if there is no registered power supply target information corresponding to the power supply target information received by the management server 101, it is not possible to identify the user who will use auto check-in. In this case, for example, a message can be displayed on the display of the charger management device 103 indicating that auto check-in is not available and that the user should carry out the conventional charger usage procedure using a charger usage application.

[0112] 1-2B. Charger usage management sequence 15 is an example of a sequence diagram 1500 of auto check-in according to one embodiment. Data transmitted and received between the devices will be described in more detail with reference to this sequence diagram.

[0113] First, in step 1, a user connects the charging connector of the charger 410 to the power supply port of the EV at the charging station. As a result, the charger management device 103 receives a connection signal from, for example, the EV (EV control device 104).

[0114] In step 2, the power supply target information acquisition module 413 of the charger management device 103 scans the user terminal 105 (Scan a device). In step 3, the charger management device 103 receives the BD address sent from the user terminal 105. In step 4, the power supply target information acquisition module 413 of the charger management device 103 transmits the BD address to the management server 101 as information related to the user terminal 105 (BD address). At this time, the charger management device 103 associates the BD address with a charger ID and transmits it.

[0115] If the power supply target information acquisition module 413 acquires multiple BD addresses, it transmits all of them or a predetermined number of BD addresses in descending order of radio wave intensity to the management server 101 together with radio wave intensity information.

[0116] In step 5, the management server 101 searches the multiple users recorded in the user information 700 to determine whether there is a user linked to the same registered power supply target information as the received power supply target information (BD address) (Retrieve the user linked to the BD address). If there is a user linked to the same registered power supply target information as the received power supply target information (BD address), the management server 101 considers the user linked to the same registered power supply target information as the power supply target information (BD address) with the strongest radio wave intensity to be the user who connected the charging connector of the charger 410 to the power supply port of the EV in step 1.

[0117] If the received power supply target information corresponds to the registered power supply target information, in step 6, the management server 101, on behalf of the user of the EV connected to the charger 410, sends a remote charging start processing signal for the charger 410 identified by the charger ID to the charger management device 103 (Send RemoteStartTransaction as the user).

[0118] In step 7, the charging start module 414 of the charger management device 103 starts charging the EV (Start Charging). This allows charging by automatic check-in using the charger usage management system 100.

[0119] 1-3. Charger usage management sequence FIG. 16 is an example of a sequence diagram 1600 of auto check-in according to another embodiment. A sequence diagram 1600 shown in Fig. 16 differs from the sequence diagram 1500 in Fig. 15 in that steps 6 to 9 relating to user authentication are inserted after step 5. Therefore, the explanation of steps common to Fig. 15 will be simplified.

[0120] First, in step 1, a user connects the charging connector of the charger 410 to the power supply port of the EV at the charging station. As a result, the charger management device 103 receives a connection signal from, for example, the EV (EV control device 104).

[0121] In step 2, the power supply target information acquisition module 413 of the charger management device 103 scans the user terminal 105 (Scan a device). In step 3, the charger management device 103 receives the BD address sent from the user terminal 105. In step 4, the power supply target information acquisition module 413 of the charger management device 103 transmits the BD address to the management server 101 as information related to the user terminal 105 (BD address). At this time, the charger management device 103 associates the BD address with a charger ID and transmits it.

[0122] If the power supply target information acquisition module 413 acquires multiple BD addresses, it transmits all of them or a predetermined number of BD addresses in descending order of radio wave intensity to the management server 101 together with radio wave intensity information.

[0123] In step 5, the management server 101 searches for a user linked to the same registered power supply target information as the received power supply target information (BD address) from the multiple users recorded in the user information 700. If the received power supply target information and the registered power supply target information correspond to each other, the management server 101 considers the user linked to the power supply target information with the strongest radio wave intensity to be the user who started charging.

[0124] If there is registered power supply target information corresponding to the power supply target information, in step 6, the management server 101 sends a notification signal to the user terminal 105 (smartphone) of the user in question that auto-check-in is available (Notify that user can use auto-check-in).

[0125] The user terminal 105 receives the notification signal (Notify that user can use auto-check-in). Based on this, in step 7, the user terminal 105 confirms with the user 106 whether charging can begin (Confirm that charging Can begin).

[0126] For this confirmation, the management server 101 may use, for example, a smartphone charger usage application on the user terminal 105 to display on the display a message indicating that auto check-in is available, a message confirming whether charging can be started, and an "Approve" button in step 6. The user terminal 105 may also use a smartphone push notification or the like to display this message and button.

[0127] Then, in step 8, if approval is obtained from the user 106 to the user terminal 105 (Accept), in step 9, a charging start request notification (Request start charging) is sent from the user terminal 105 to the management server 101. That is, for example, when the user selects the "Approve" button on their smartphone, it can be determined that approval has been obtained from the user to start charging by auto check-in.

[0128] Thereafter, in step 10, the management server 101 sends a remote start transaction signal for charging to the charger management device 103 on behalf of the user of the EV connected to the charger 410 (Send RemoteStartTransaction as the user).

[0129] Then, in step 11, the charging start module 414 of the charger management device 103 starts charging the EV (Start charging). This allows charging by auto check-in using the charger usage management system 100 with the user's approval.

[0130] Note that, in cases where the power supply target information acquisition module 413 is unable to acquire the power supply target information, where there is no registered power supply target information corresponding to the power supply target information received by the management server 101, or where approval is not obtained from the user in step 8, it is not possible to identify the user who will use auto check-in. If approval is not obtained from the user within a predetermined period of time, the user terminal 105 can, for example, transmit an error signal indicating that approval has not been obtained to the management server 101. In addition, in such cases, the management server 101 can, for example, display on the display of the charger management device 103 a message indicating that auto check-in is not available and that normal charging procedures should be carried out.

[0131] 2. Auto check-in using connected cars that use connected services Next, we will explain how to manage the use of chargers during auto check-in by connected cars that use connected services.

[0132] As a premise, the connected car is using a connected service and has registered OEM user information 900 with the connected service provider. When using the connected service, the vehicle management device 102 monitors the connected car and acquires the connected car's location information, driving information, vehicle management information, etc. at predetermined time intervals. In addition, the connected car (EV control device 104) is configured to transmit vehicle management information 510, OEM service information 520, charging management information 530, etc. to the vehicle management device 102 each time a predetermined event occurs, such as connection to a charger 410.

[0133] On the other hand, connected service providers conclude contracts with users to use the charger usage management system 100 so that users can more easily charge their vehicles when using connected services. Connected car users can use the charger usage management system 100 by, for example, using a specific charger usage application provided by the connected service provider.

[0134] For example, it is assumed that a user downloads a predetermined charger usage application provided by the charger usage management system 100 using the user terminal 105 (here, a smartphone) and registers information other than the registered power supply target information. This charger usage application is not limited to use for the auto check-in function, and may be, for example, an application for using the charging stations and chargers 410 registered in the charger usage management system 100. The charger usage application may be capable of, for example, performing on-the-spot usage procedures for the charger 410 or making advance reservations for use of the charger 410. The user registration information before advance user association with this electrical appliance usage application includes, for example, the user name, payment information, password information, and identity verification information among the information shown in the user information 700. The user registration information before advance user association does not include the registered power supply target information.

[0135] In addition, when a connected car charges using a charger 410 whose usage is managed by the charger usage management system 100, the vehicle management device 102 provides the management server 101 with information on the target device to be powered.

[0136] Auto check-in by a connected car using a connected service differs from the above-described auto check-in by an EV in that the power supply target information is acquired by the vehicle management device 102 of the provider of the connected service. In other words, the vehicle management device 102 performs part of the function of the charger management device in the present invention. Therefore, the explanation of steps that are common to steps already explained will be simplified.

[0137] 2-1. Preliminary user association sequence FIG. 17 is another example of a sequence diagram 1700 for advance registration.

[0138] At the charging station, the user first uses a charger usage application on the user terminal 105 to start a charger usage procedure (smartphone operation) for a specific charger 410. Note that the charger usage procedure using the charger usage application may be performed after step 1.

[0139] Then, in step 1, a user connects the charging connector of the charger 410 to the power supply port of the connected car at the charging station (Connect). As a result, the charger management device 103 receives a connection signal, for example, from the connected car (EV control device 104). The time when the connection signal is received is recorded in the charger management device 103. At this time, the charger management device 103 also receives information about the charging conditions of the EV (including, for example, SOC) from the EV control device 104, for example, via CAN communication when the charging connector is connected.

[0140] In step 2, the charger management device 103 transmits a connection notification signal indicating that the charger 410 has been connected to the management server 101 (Notify connection). At this time, the charger management device 103 also transmits information for identifying the connected car connected to the charger 410 to the management server 101 (Time, SOC, etc.). The management server 101 receives the connection notification signal and the information for identifying the connected car.

[0141] The information for identifying a connected car is not particularly limited as long as it can be used by the management server 101 to identify a connected car connected to the charger 410 in step 9, which will be described later. For example, it may be information about the time when the connected car connected to the charger 410, information transmitted by the connected car to the charger 410 via CAN communication, or a charger ID linked to the charger location information corresponding to the connected car's location information. The CAN communication information is not limited to this, but may be information about charging conditions such as the connected car's SOC, charging current value, and maximum charging voltage. Any one of these pieces of information may be used alone, or two or more pieces may be used in combination. In this embodiment, for example, the connection time and SOC are transmitted together as information for identifying a connected car.

[0142] In step 3, the user 106 performs an operation to start charging (Start Charging) using a charger usage application on a smartphone (an example of the user terminal 105). The smartphone 105 accepts the user's operation to start charging, and in step 4 transmits a request to start charging (Request to start charging) to the management server 101. This signal includes a charger ID that identifies the specified charger 410.

[0143] The management server 101 receives the charging start request and in step 5 sends a remote start processing signal for charging for the charger 410 identified by the charger ID to the charger management device 103 that manages the charger 410 (Send RemoteStartTransaction). When the charger management device 103 receives the remote start processing signal for charging, in step 6 the charging start module 414 of the charger management device 103 starts charging the connected car (Start Charging).

[0144] When charging starts, the connected car (EV control device 104) transmits a connection notification signal to the vehicle management device 102 in step 7 to notify that the charging session has started (Notify the session started). At this time, the connected car (EV control device 104) also transmits information for identifying the charger 410 connected to the connected car to the vehicle management device 102. The vehicle management device 102 receives the connection notification signal and the information for identifying the charger 410 (here, the connection time and SOC).

[0145] The information for identifying the charger 410 is not particularly limited as long as it can be used by the management server 101 to identify the charger 410 connected to the connected car in step 9, which will be described later. For example, the information can be matched with the information for identifying the connected car described above. Specifically, the information may include information about the time the connected car connected to the charger 410, information transmitted by the connected car to the charger 410 via CAN communication, connected car location information corresponding to the charger's location information, or connected car identification information linked to the connected car's location information. The CAN communication information is not limited to this, and may include, for example, information about the connected car's SOC, charging current value, maximum charging voltage, and other charging conditions. Any one of these pieces of information may be used alone, or two or more pieces may be used in combination. In this embodiment, the connection time and SOC are transmitted together as information for identifying the charger 410.

[0146] In step 8, the power supply target information transmission module 312 of the vehicle management device 102 transmits power supply target information to the management server 101. Specifically, the power supply target information transmission module 312 transmits the VIN code of the connected car recorded in the OEM user information 900 to the management server 101 as power supply target information corresponding to the connected car that transmitted the signal notifying that a charging session has started (VIN code). Furthermore, for example, in addition to the VIN code, the power supply target information transmission module 312 transmits to the management server 101 information for identifying the charger 410 to which the connected car is connected.

[0147] The management server 101 receives, from the vehicle management device 102, power supply target information (VIN code) and information for identifying the charger 410 (for example, connection time and SOC).

[0148] Then, in step 9, the management server 101 determines which charger 410 the user's connected car is to be charged at, based on the information received from the charger management device 103 in step 2 and the information received from the vehicle management device 102 in step 8. Specifically, the management server 101 compares, for example, the information for identifying the charger 410 received from the vehicle management device 102 in step 8 (e.g., the connection time and SOC) with the information for identifying the connected car received from the charger management device 103 in step 2. The management server 101 then determines that the charger 410 managed by the charger management device 103 that has transmitted the matching information for identifying the connected car is the charger 410 connected to the connected car corresponding to the power supply target information (VIN code). The management server 101 then links the power supply target information (VIN code) to the user 106 who has sent a charging start request for this charger 410 via the smartphone 105, and records it in the user information 700. That is, the management server 101 records the power supply target information (VIN code) sent from the vehicle management device 102 in the user information 700 as registered power supply target information corresponding to the user.

[0149] This allows the unique information of the connected car that uses the charging station to be recorded in the user information 700.

[0150] 2-2. Charger usage management sequence As described above, by linking the unique information of a connected car that can be obtained about the connected car using the charging station to user information 700 in advance, the connected car will be able to use auto check-in from the next time.

[0151] FIG. 18 is an example of a sequence diagram 1800 of auto check-in according to one embodiment. First, in step 1, a user connects the charging connector of the charger 410 to the power supply port of the connected car at the charging station. As a result, the charger management device 103 receives a connection signal, for example, from the connected car (EV control device 104). The time when the connection signal is received is recorded in the charger management device 103. At this time, the charger management device 103 also receives information about the charging conditions of the EV (including, for example, SOC) from the EV control device 104, for example, via CAN communication when the charging connector is connected.

[0152] In step 2, the charger management device 103 transmits a connection notification signal indicating that the charger 410 has been connected to the management server 101 (Notify connection). At this time, the charger management device 103 also transmits information for identifying the connected car connected to the charger 410 to the management server 101. The management server 101 receives the connection notification signal and the information for identifying the connected car.

[0153] The information for identifying a connected car is not particularly limited as long as it can be used by the management server 101 to identify a connected car connected to the charger 410 in step 5, which will be described later. For example, it may be information about the time when the connected car connected to the charger 410, information transmitted by the connected car to the charger 410 via CAN communication, or a charger ID linked to the charger location information corresponding to the connected car's location information. The CAN communication information is not limited to this, but may be information about charging conditions such as the connected car's SOC, charging current value, and maximum charging voltage. Any one of these pieces of information may be used alone, or two or more pieces may be used in combination. In this embodiment, for example, the connection time and SOC are transmitted together as information for identifying a connected car.

[0154] Also, in step 3, the connected car (EV control device 104) transmits a connection notification signal to the vehicle management device 102 indicating that the charger 410 has been connected (Notify connection). At this time, the connected car (EV control device 104) also transmits information for identifying the charger 410 connected to the connected car to the vehicle management device 102. The vehicle management device 102 receives the connection notification signal and information for identifying the charger 410 (here, the connection time and SOC).

[0155] The information for identifying the charger 410 is not particularly limited as long as it can be used by the management server 101 to identify the charger 410 connected to the connected car in step 5 described below. For example, it can be information that can be matched with the information for identifying the connected car described above. Specifically, it may be information about the time the connected car connected to the charger 410, information transmitted by the connected car to the charger 410 via CAN communication, or connected car identification information linked to the connected car's location information corresponding to the charger's location information. The CAN communication information is not limited to this, and may be, for example, information about the connected car's SOC, charging current value, maximum charging voltage, and other charging conditions. Any one of these pieces of information may be used alone, or two or more pieces may be used in combination. In this embodiment, the connection time and SOC are transmitted together as information for identifying the charger 410.

[0156] Step 2 and step 3 may be performed in any order, and either may be performed first, or they may be performed simultaneously.

[0157] In step 4, the power supply target information transmission module 312 of the vehicle management device 102 transmits the power supply target information to the management server 101. Specifically, the power supply target information transmission module 312 transmits, as the power supply target information, the VIN code (VIN code of the EV) corresponding to the connected car (EV control device 104) that transmitted the connection notification signal. Furthermore, for example, the power supply target information transmission module 312 transmits, in addition to the VIN code, information for identifying the charger 410 to which the connected car is connected to the management server 101.

[0158] The management server 101 receives, from the vehicle management device 102, power supply target information (VIN code) and information for identifying the charger 410 (for example, connection time and SOC).

[0159] Then, in step 5, the management server 101 determines which user is attempting to charge the connected car using the charger 410, based on the information received from the charger management device 103 in step 2 and the information received from the vehicle management device 102 in step 4. Specifically, the management server 101 searches for the received power supply target information (VIN code) among the registered power supply target information (VIN code) recorded in the user information 700 (Retrieve the user linked to the VIN code). If the user information 700 records registered power supply target information that matches the received power supply target information, it can be determined that the user linked to the registered power supply target information is attempting to start charging.

[0160] Furthermore, to confirm which charger 410 the user is attempting to use to charge the connected car, the management server 101 compares information for identifying the charger 410 (e.g., SOC) received from the vehicle management device 102 with information for identifying the connected car (e.g., SOC) received from the charger management device 103. The management server 101 can then determine that the charger management device 103 that transmitted the information for identifying the connected car (e.g., SOC) corresponding to the information for identifying the charger 410 (e.g., SOC) is the charger management device 103 for the charger 410 the user is attempting to start charging. In other words, the management server 101 determines that the charger 410 (charger management device 103) that transmitted information corresponding to the information for identifying the charger 410 received from the vehicle management device 102 is the charger 410 to which the connected car corresponding to the power supply target information (VIN code) transmitted from the vehicle management device 102 is connected.

[0161] If there are multiple pairs of information (e.g., SOC) for identifying the charger 410 received from the vehicle management device 102 and information (e.g., SOC) for identifying the connected car received from the charger management device 103 that match, the management server 101 also compares the connection times. Then, the charger management device 103 that sent the information for identifying the connected car with matching connection times and SOC is determined to be the charger management device 103 for the charger 410 with which the user is about to start charging.

[0162] If there is registered power supply target information corresponding to the power supply target information, it is determined that the user corresponding to the registered power supply target information can use auto check-in, and in step 6, the management server 101 sends a remote charging start processing signal to the charger management device 103 on behalf of the user of the EV connected to the charger 410 (Send RemoteStartTransaction as the user). Specifically, the management server 101 sends a remote charging start processing signal to the charger management device 103 that manages the charger 410 to which the EV corresponding to the power supply target information (VIN code) is connected.

[0163] The charger management device 103 receives a remote charging start processing signal from the management server 101. Then, in step 7, the charger management device 103's charge start module 414 starts charging the EV (Start charging).

[0164] This makes it possible for connected cars receiving connected services to be charged by auto check-in using the charger usage management system 100.

[0165] 2-3. Charger usage management sequence FIG. 19 is an example of a sequence diagram 1900 of auto check-in according to another embodiment. A sequence diagram 1900 shown in Fig. 19 differs from the sequence diagram 1800 in Fig. 18 in that steps 6 to 9 relating to user authentication are inserted after step 5. Therefore, the explanation of steps common to Fig. 18 will be simplified.

[0166] First, in step 1, a user connects the charging connector of the charger 410 to the power supply port of the connected car at the charging station. As a result, the charger management device 103 receives a connection signal, for example, from the connected car (EV control device 104). The time when the connection signal is received is recorded in the charger management device 103. At this time, the charger management device 103 also receives information about the charging conditions of the EV (including, for example, SOC) from the EV control device 104, for example, via CAN communication when the charging connector is connected.

[0167] In step 2, the charger management device 103 transmits a connection notification signal indicating that the charger 410 has been connected to the management server 101 (Notify connection). At this time, the charger management device 103 also transmits information for identifying the connected car connected to the charger 410 to the management server 101. The management server 101 receives the connection notification signal and the information for identifying the connected car.

[0168] Also, in step 3, the connected car (EV control device 104) transmits a connection notification signal (Notify connection) to the vehicle management device 102. At this time, the connected car (EV control device 104) also transmits information for identifying the charger 410 connected to the connected car to the vehicle management device 102. The vehicle management device 102 receives the connection notification signal and the information for identifying the charger 410 (here, the connection time and SOC).

[0169] In step 4, the power supply target information transmission module 312 of the vehicle management device 102 transmits the power supply target information to the management server 101. Specifically, the power supply target information transmission module 312 transmits, as the power supply target information, the VIN code (VIN code of the EV) corresponding to the connected car (EV control device 104) that transmitted the connection notification signal. Furthermore, for example, the power supply target information transmission module 312 transmits, in addition to the VIN code, information for identifying the charger 410 to which the connected car is connected to the management server 101.

[0170] The management server 101 receives, from the vehicle management device 102, power supply target information (VIN code) and information for identifying the charger 410 (for example, connection time and SOC).

[0171] Then, in step 5, the management server 101 determines which user is attempting to charge the connected car and at which charger 410, based on the information received from the charger management device 103 in step 2 and the information received from the vehicle management device 102 in step 4. Specifically, the management server 101 searches for the received power supply target information (VIN code) in the registered power supply target information (VIN code) recorded in the user information 700 (Retrieve the user linked to the VIN code). If the user information 700 contains registered power supply target information corresponding to the power supply target information, it determines that the user corresponding to the registered power supply target information is attempting to start charging.

[0172] In addition, the management server 101 determines that the charger 410 (charger management device 103) that sent information corresponding to the information identifying the charger 410 received from the vehicle management device 102 is the charger 410 to which the connected car corresponding to the power supply target information (VIN code) sent from the vehicle management device 102 is connected.

[0173] If there are multiple pairs of information (e.g., SOC) for identifying the charger 410 received from the vehicle management device 102 and information (e.g., SOC) for identifying the connected car received from the charger management device 103 that match, the management server 101 also compares the connection times. Then, the charger management device 103 that sent the information for identifying the connected car with matching connection times and SOC is determined to be the charger management device 103 for the charger 410 with which the user is about to start charging.

[0174] If there is registered power supply target information corresponding to the power supply target information, it is determined that the user corresponding to the registered power supply target information can use auto-check-in, and in step 6, the management server 101 sends a notification signal to the user terminal 105 (smartphone) of the user in question that auto-check-in is available (Notify that user can use auto-check-in).

[0175] The user terminal 105 receives the notification signal (Notify that user can use auto-check-in). Based on this, the user terminal 105 confirms with the user 106 whether charging can begin in step 7 (Confirm that charging can begin). For this confirmation, the user terminal 105 can use, for example, a charger usage application on a smartphone to display on the display a message indicating that auto-check-in is available, a message confirming whether charging can begin, and an "Approve" button. Alternatively, push notifications on the smartphone can be used.

[0176] If approval is obtained from the user 106 to the user terminal 105 in step 8 (Accept), then in step 9, a charging start request notification (Request start charging) is sent from the user terminal 105 to the management server 101. That is, for example, when the user 106 selects the "Approve" button on his / her smartphone, it can be determined that approval has been obtained from the user to start charging by auto check-in.

[0177] Thereafter, in step 10, the management server 101 sends a remote start transaction signal for charging to the charger management device 103 on behalf of the user of the EV connected to the charger 410 (Send RemoteStartTransaction as the user).

[0178] The charger management device 103 receives a remote start processing signal for charging (Send RemoteStartTransaction as the user) from the management server 101. Then, in step 11, the charge start module 414 of the charger management device 103 starts charging the EV (Start charging).

[0179] This makes it possible for connected cars receiving connected services to be charged by auto check-in with user authentication using the charger usage management system 100.

[0180] Note that auto check-in cannot be used if there is no registered power supply target information corresponding to the power supply target information in step 5, or if approval is not obtained from the user in step 8 (including if approval is not obtained within a predetermined time period). If approval is not obtained from the user within a predetermined time period in step 8, the user terminal 105 can, for example, instead of step 9, transmit an error signal indicating that approval was not obtained to the management server 101.

[0181] In this case, the management server 101 can, for example, display a message on the display of the charger management device 103 indicating that auto check-in is not available and that normal charging procedures should be carried out. Alternatively, the management server 101 can send an error signal to the vehicle management device 102 indicating that auto check-in is not available, etc.

[0182] The present invention is not limited to the above-described embodiments and includes various modifications. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and are not necessarily limited to those including all of the described configurations. Furthermore, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, it is possible to add, delete, or replace part of the configuration of each embodiment with other configurations.

[0183] (1) In the above embodiment, when a user uses the charger usage management system 100 without going through a service provider that provides connected services, the power supply target information acquisition module 413 is configured to acquire information related to the user of the EV as the power supply target information. However, the power supply target information acquisition module 413 may also be configured to acquire information related to the EV as the power supply target information. The information related to the EV may be, for example, identification information unique to the EV, such as a VIN code. The information related to the EV may be acquired, for example, by the power supply target information acquisition module 413 communicating with the EV's charging control ECV or by communicating with an on-board user terminal.

[0184] (2) In the advance user association flow of the above embodiment, the management server 101 independently accepts a charging start request (e.g., step 3 in FIG. 14 ) and independently transmits a remote start processing signal to the charger management device 103 (e.g., step 4 in FIG. 14 ). However, the management server 101 may be configured to accept an association request from the user terminal 105 in addition to the charging start request (e.g., in step 3 in FIG. 14 ) and transmit a remote start processing signal and a power supply target information acquisition request to the charger management device 103 (e.g., in step 4 in FIG. 14 ). For example, the charger usage application may be configured to simultaneously display a comment such as “Link your smartphone to enable auto check-in” and a selection box on the display of the user terminal 105 along with a “Start charging” button. Then, when the user selects this selection box and then selects the “Start charging” button, the management server 101 may accept a charging start request and an association request from the user terminal 105. This allows the user using the charger usage application to be notified of the use of the auto check-in function and encourages the user to use it.

[0185] Also, when the management server 101 has not received the above linking request, for example, in step 3 of FIG. 14, it may not perform the linking in step 9 or the like. For example, when the charger management device 103 receives the linking request, for example, it transmits a remote start processing signal and a power supply target information acquisition request in step 4 of FIG. 14. The charger management device 103 may perform scanning of the user terminal 105 in step 6 based on the power supply target information acquisition request. Also, when the management server 101 has not received the above linking request, for example, in step 3 of FIG. 14, it may transmit only the remote start processing signal in step 4 of FIG. 14. When the charger management device 103 does not receive the power supply target information acquisition request, it may not perform scanning of the user terminal 105 in step 6. Thereby, when the user does not wish to use the auto check-in function, it is possible to prevent the power supply target information from being linked to the user information in advance. Note that whether to issue the linking request may be separately set in the charger use application.

[0186] (3) In the above embodiment, when the power supply target information acquisition module 413 of the charger management device 103 acquires a plurality of power supply target information (BD addresses), the management server 101 regards the BD address with the highest radio wave intensity among the registered power supply target information and the corresponding power supply target information as the power supply target information. However, when the power supply target information acquisition module 413 acquires a plurality of BD addresses, the power supply target information acquisition module 413 may regard the BD address with the highest radio wave intensity as the power supply target information. In this case, all of the others or a predetermined number of BD addresses from the ones with stronger radio wave intensity may also be transmitted to the management server 101, or may not be transmitted.

[0187] (4) Note that, if there are multiple pieces of power supply target information that correspond to the registered power supply target information among the power supply target information acquired by the power supply target information acquisition module 413, the users corresponding to these pieces of power supply target information may be users of the charger usage management system 100 who were passengers in the EV. In this case, it may be possible for one or more of these multiple users to wish to pay the usage fee for the charging. Therefore, the charger usage management system 100 may be configured to allow the user terminal 105 to appropriately change the payer, the number of payers, the payment ratio / payment amount, etc. between the user deemed to be the power supply target information (the user corresponding to the BD address with the strongest radio wave strength) and other users (the users corresponding to the BD addresses with weaker radio wave strength). In this case, the system may be configured to obtain approval from one or more payers after the change.

[0188] (5) In the above embodiment, a case has been described in which a rapid charger conforming to the CHAdeMO system is used as the charger 410. However, the present technology is not limited to application to chargers conforming to the CHAdeMO system. For example, the charger 410 in the charger usage management system 100 may be a charger conforming to general charging connector standards such as SAE J1772 (IEC 62196-2 type 1), IEC 62196-2 type 2, or AC GB / T, or may be a charger capable of receiving vehicle identification information (e.g., a VIN code) from the EV or the EV control device 104.

[0189] (6) In the above embodiment, when a user uses the charger usage management system 100 through a service provider that provides connected services, the information identifying the charger and the information identifying the connected car includes CAN information. However, the information identifying the charger and the information identifying the connected car do not have to include CAN information. Furthermore, if the information identifying the charger and the information identifying the connected car does not include CAN information, for example, step 2 in FIGS. 17 to 19 , in which the charger management device 103 transmits a connection notification signal and information for identifying the connected car to the management server 101, may be omitted. In this case, the vehicle management device 102 may transmit, to the management server 101, information identifying the charger, such as location information of the connected car and connection time information, along with vehicle identification information (VIN code). Thus, in the pre-association, the management server 101 may register the vehicle identification information (VIN code) as registered power supply target information in the user information of the user who transmitted a charge request for the charger 410 whose location information corresponds to the location information of the connected car. Furthermore, during auto check-in, the management server 101 may identify the charger 410 having location information corresponding to the location information of the connected car as the charger 410 to which the connected car is connected.

[0190] (7) In the above embodiment, the user operates the charger through the user terminal 105. However, some or all of the operations of the charger may be performed by directly operating the charger or by using the charging operation function of the EV.

[0191] (8) The charger management device 103 may be configured to be able to access the user information 700. In this case, the charger management device 103 also has the functions of the management server 101, and the charger management device 103 alone can realize auto check-in.

[0192] (9) In the above embodiment, the power supply target information is a BD address that can be acquired via Bluetooth communication without authentication or encryption. However, the power supply target information and the method for acquiring the power supply target information at the charging station are not limited to this. For example, the power supply target information may include identification information (e.g., a terminal ID) of the user terminal 105 or location information (e.g., GPS location information) of the user terminal 105. Furthermore, the power supply target information may be acquired via other short-range wireless communication technologies such as WiFi, NFC, infrared communication, the Web, or ZigBee (registered trademark).

[0193] (10) In the above embodiment, in the auto check-in flow, if there is no registered power supply target information corresponding to the power supply target information received by the management server 101, for example, a message is displayed on the display of the charger management device 103 indicating that auto check-in is not available and that the user should carry out the conventional charger usage procedure using a charger usage application. If there is no registered power supply target information corresponding to the power supply target information, it is possible that (a) prior user association has not been performed, (b) prior user association has resulted in an error, or (c) the user has changed the user terminal 105. Therefore, when the user has carried out the conventional charger usage procedure using the charger usage application, the management server 101 may subsequently ask on the display of the user terminal 105 whether it is OK to register the user terminal 105 as a possessed terminal for use with auto check-in. If approval is obtained from the user, the management server 101 may transmit a signal to the charger management device 103 instructing it to acquire power supply target information (i.e., to scan the user terminal 105), and the power supply target information received in response may be recorded as the registered power supply target information of the user.

[0194] (11) Furthermore, the above-described configurations, functions, processing units, processing means, etc. may be partially or entirely implemented in hardware, for example, by designing them as integrated circuits. Furthermore, the above-described configurations, functions, etc. may be implemented in software by a processor interpreting and executing a program that implements each function. Information such as the program, table, and file that implements each function can be stored in a memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD.

[0195] (12) Also, the control lines and information lines shown are those considered necessary for explanation, and do not necessarily show all the control lines and information lines in the product. In reality, it can be assumed that almost all components are interconnected.

[0196] (13) In Fig. 1, the elements constituting the charger usage management system 100 are all connected via the same communication network. However, the elements constituting the charger usage management system 100 may be connectable via two or more different networks.

[0197] (14) Furthermore, one or more of the elements constituting the charger usage management system 100, namely, one or more management servers 101, one or more vehicle management devices 102, one or more charger management devices 103, one or more EV control devices 104, and one or more user terminals 105, may be installed in different countries. Furthermore, the management server 101, the vehicle management device 102, the charger management device 103, the EV control device 104, and the user terminal 105 may be configured by one or more terminals. Furthermore, any of these may be installed in different countries. The above-described embodiment discloses at least the configurations described in the claims. [Explanation of symbols]

[0198] 100...Charger usage management system, 101...Management server, 102...Vehicle management device, 103...Charger management device, 104...EV control device, 105...User terminal (smartphone), 211...Management module, 212...Power supply target information acquisition module, 213...Authentication module, 214...Charging permission module, 311...EV management module, 312...Power supply target information transmission module, 313...Authentication module, 410...Charger, 411...Charger management module, 412...Connector connection status detection module, 413...Power supply target information acquisition module, 414...Charging start module, 420...Bluetooth board, 511...Drive control module, 512...Charging control module, 611...User execution module, 612...User charging management module

Claims

1. A first management device that manages the usage state of the charger; and A second management device that manages charging of the electric vehicle from the charger, a detection unit that detects that a charging unit of the charger and a power supply unit of the electric vehicle are in a chargeable state; a charge initiation unit that initiates charging of the electric vehicle from the charger; a power supply target information acquisition unit that acquires power supply target information, which is at least one of information related to the electric vehicle and information related to a user of the electric vehicle; A second management device comprising: Equipped with When the detection unit detects that the charging unit of the charger and the power supply unit of the electric vehicle are in a chargeable state and when the power supply target information acquisition unit acquires the power supply target information, the second management device transmits the acquired power supply target information to the first management device; When the received power supply target information corresponds to pre-recorded registered power supply target information, the first management device transmits, to the second management device, charging start information that causes the charging start unit to start charging the electric vehicle from the charger. Charger usage management system.

2. A first management device that manages the usage state of the charger; a second management device including a charge initiation unit that initiates charging of the electric vehicle from the charger; and A third management device that manages the electric vehicle, a detection unit that detects that a charging unit of the charger and a power supply unit of the electric vehicle are in a chargeable state; a power supply target information acquisition unit that acquires power supply target information, which is at least one of information related to the electric vehicle and information related to a user of the electric vehicle; A third management device comprising: Equipped with When the detection unit detects that the charging unit of the charger and the power supply unit of the electric vehicle are in a chargeable state and when the power supply target information acquisition unit acquires the power supply target information, the third management device transmits the acquired power supply target information to the first management device; When the received power supply target information corresponds to pre-recorded registered power supply target information, the first management device transmits, to the second management device, charging start information that causes the charging start unit to start charging the electric vehicle from the charger. Charger usage management system.

3. The second management device is receiving information about a detectable terminal present in the vicinity of the charger when information indicating that a charging unit of the charger and a power supply unit of the electric vehicle are in a chargeable state is obtained; The received information regarding detectable terminals present in the vicinity of the charger is transmitted to the first management device as the power supply target information. The charger usage management system according to claim 1 .

4. when the second management device receives information about a plurality of terminals as detectable terminals present in the vicinity of the charger, the second management device transmits the information about the plurality of terminals together with their reception strengths to the first management device; When a plurality of pieces of information among the received information about the plurality of terminals correspond to a plurality of pieces of registered power supply target information recorded in advance, the first management device sets the registered power supply target information corresponding to the information about the terminal having the highest reception strength as registered power supply target information related to the electric vehicle. The charger usage management system according to claim 3 .

5. When the second management device receives information about a plurality of terminals as detectable terminals existing in the vicinity of the charger, the second management device transmits information about a terminal closest to the charger to the first management device as the power supply target information. The charger usage management system according to claim 3 .

6. When the received power supply target information does not correspond to the registered power supply target information, the first management device transmits, to the second management device, information indicating that charging of the electric vehicle from the charger will not be performed. The charger usage management system according to claim 1 or 2.

7. The first management device transmits information requesting approval for charging the electric vehicle from the charger to a terminal corresponding to the registered power supply target information, If the approval is given, the charging start information is transmitted to the second management device. The charger usage management system according to claim 1 or 2.

8. The third management device is Acquiring information about the electric vehicle and identification information about the charger in association with each other; When acquiring information indicating that a power supply unit of the electric vehicle has become capable of charging with a charging unit of the charger, transmitting the power supply target information and identification information of the charger to the first management device; the first management device regards the received power supply target information as power supply target information corresponding to a charger corresponding to the received charger identification information and the electric vehicle that has become in a chargeable state; The charger usage management system according to claim 2 .

9. The first management device acquires predetermined charging information, which is information on a predetermined charging condition associated with the registered power supply target information, in advance, and transmits the predetermined charging information together with the charging start information. The charger usage management system according to claim 1 or 2.

10. receiving power supply target information, which is at least one of information related to the electric vehicle and information related to a user of the electric vehicle, for the electric vehicle in which a charging unit of the charger and a power supply unit of the electric vehicle are in a chargeable state; transmitting charging start information that is information for starting charging of the electric vehicle from the charger when the received power supply target information corresponds to pre-recorded registered power supply target information; Management device.

11. transmitting information indicating that charging of the electric vehicle from the charger is not permitted when the received power supply target information does not correspond to pre-recorded registered power supply target information; The management device according to claim 9.

12. transmitting information requesting approval for charging the electric vehicle from the charger to a terminal corresponding to the registered power supply target information; If approved, transmit the charging start information. The management device according to claim 9.

13. Predetermined charging information, which is information regarding a predetermined charging condition associated with the registered power supply target information, is acquired in advance, and the predetermined charging information is transmitted together with the charging start information. The management device according to claim 9.

14. 1. A computer-implemented method comprising: receiving power supply target information, which is at least one of information related to the electric vehicle and information related to a user of the electric vehicle, for the electric vehicle in which a charging unit of the charger and a power supply unit of the electric vehicle are in a chargeable state; transmitting charging start information that is information for starting charging of the electric vehicle from the charger when the received power supply target information corresponds to pre-recorded registered power supply target information; Management method.

15. A program for causing a management device to execute each step of the management method according to claim 13.

16. a power supply target information acquisition unit that is connected to an electric vehicle and acquires power supply target information, which is at least one of information related to the electric vehicle and information related to a user of the electric vehicle; a detection unit that detects that a power supply unit of the electric vehicle is in a chargeable state with a charging unit of a charger; Equipped with When it is detected that a power supply unit of the electric vehicle is in a chargeable state with a charging unit of the charger, information related to a user of the electric vehicle is transmitted to another management device. Management device.

17. 1. A computer-implemented method comprising: When detecting that a power supply unit of the electric vehicle is in a chargeable state with a charging unit of the charger, acquiring power supply target information, which is at least one of information related to the electric vehicle and information related to a user of the electric vehicle; Transmitting the obtained power supply target information to another management device; Management method.

18. The power supply target information is a VIN code assigned to the electric vehicle. The management method according to claim 17.

19. A program for causing a management device to execute each step of the management method according to claim 17.

20. a detection unit that detects that a charging unit of the charger is in a state capable of charging with a power supply unit of the electric vehicle; a charge initiation unit that initiates charging of the electric vehicle from the charger; a power supply target information acquisition unit that acquires power supply target information, which is at least one of information related to the electric vehicle and information related to a user of the electric vehicle; Equipped with When acquiring information indicating that a charging unit of the charger is in a chargeable state with a power supply unit of the electric vehicle, receiving information regarding a detectable terminal present in the vicinity of the charger; The information regarding the detectable terminals present in the vicinity of the charger is transmitted to another management device as the power supply target information. Management device.

21. When receiving information about a plurality of terminals as detectable terminals existing in the vicinity of the charger, the information about the terminal closest to the charger is transmitted to the other management device as the power supply target information. The management device according to claim 20.

22. When information regarding a plurality of terminals that are present in the vicinity of the charger and that can be detected is received, the information regarding the plurality of terminals is transmitted to the other management device. The management device according to claim 20.

23. 1. A computer-implemented method comprising: When acquiring information indicating that a charging unit of the charger is in a chargeable state with a power supply unit of the electric vehicle, receiving information regarding a detectable terminal present in the vicinity of the charger; The information regarding the detectable terminals present in the vicinity of the charger is transmitted to another management device as power supply target information; starting charging of the electric vehicle from the charger based on charging start information received from the other management device.

24. The power supply target information is a Bluetooth device address of the terminal. The management method according to claim 21.

25. A program for causing a management device to execute each step of the management method according to claim 23.

Images