Management device, management system, terminal device, and program

Abstract

To provide a management device, a management system, a terminal device, and a program that can determine a charging state of a charger for each type of a mobile object.SOLUTION: A management device according to an embodiment comprises an input unit and a storage unit. The input unit receives an input of success / failure information that indicates whether or not charging of a mobile object with a charger has been successful or failed, charger identification information for identifying the charger, and type identification information for identifying a type of the mobile object. The storage unit makes a storage device store a result of success or failure of charging of the mobile unit of the type identified by the type identification information with the charger identified by the charger identification information on the basis of the information input to the input unit such that the type of the charger used in the charging and the mobile unit charged are identifiable.SELECTED DRAWING: Figure 4

Description

Technical Field

[0001] The present invention relates to a management device, a management system, a terminal device, and a program.

Background Art

[0002] There are various services that provide the operating status of vehicle chargers.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, none of the services provide the charging status for each vehicle type. Therefore, when a charger cannot charge due to incompatibility with the vehicle type, the user of the service may lose the opportunity to charge even though the user's vehicle can actually be charged. Conversely, there may be a case where the user's vehicle cannot be charged with a charger that the service indicates can be charged.

[0005] The problem to be solved by the embodiments of the present invention is to provide a management device, a management system, a terminal device, and a program capable of grasping the charging status of chargers for each type of moving object.

Means for Solving the Problems

[0006] The management device according to the embodiment includes an input unit and a storage unit. The input unit receives input of success or failure information indicating whether charging of the moving body by the charger has succeeded or failed, charger identification information for identifying the charger, and type identification information for identifying the type of the moving body. Based on the information input to the input unit, the storage unit stores, in a storage device, the success or failure result of charging the moving body of the type identified by the type identification information with the charger identified by the charger identification information in such a manner that the charger used for charging and the type of the moving body to be charged are known.

Advantages of the Invention

[0007] The present invention can grasp the charging status of chargers for each type of moving body.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Modes for Carrying Out the Invention

[0009] Hereinafter, the management system according to the embodiment will be described with reference to the drawings. Note that the scales of the respective parts in the following drawings may be appropriately changed. In addition, the respective drawings used in the following description of the embodiment may show the configuration with omissions for the purpose of explanation. Also, in each drawing and this specification, the same reference numerals indicate the same elements.

[0010] FIG. 1 is a block diagram showing an example of the main configuration of the management system 1 according to the embodiment and the components included in the management system 1. Note that each component of the device may be built-in or externally attached. The management system 1 manages information on the success and failure of charging the vehicle 300 for each charger 400. In addition, the management system 1 provides a charger information service. The management system 1 includes, as an example, a server device 100, a terminal device 200, a vehicle 300, and a charger 400. Note that the management system 1 may include a part of these. The number of each device is not limited, but typically, the number of each of the terminal device 200, the vehicle 300, and the charger 400 is plural.

[0011] The server device 100 and the terminal device 200 are connected to the network NW. The network NW is typically a communication network including the Internet. The network NW is typically a communication network including a WAN (wide area network). The vehicle 300 may also be connected to the network NW. The charger 400 may also be connected to the network NW.

[0012] The server device 100 is a server that serves as the center of the management system 1. In addition, the server device 100 provides a charger information service. The server device 100 includes, as an example, a processor 110, a ROM (read-only memory) 120, a RAM (random-access memory) 130, an auxiliary storage device 140, and a communication interface 150. And a bus 160 etc. connect these parts. Note that the server device 100 is an example of a management device.

[0013] The processor 110 is the central part of a computer that performs processes such as operations and controls necessary for the operation of the server device 100, and performs various operations and processes. The processor 110 is, for example, a CPU (central processing unit), MPU (micro processing unit), SoC (system on a chip), DSP (digital signal processor), GPU (graphics processing unit), ASIC (application specific integrated circuit), PLD (programmable logic device), or FPGA (field-programmable gate array), etc. Alternatively, the processor 110 is a combination of a plurality of these. Also, the processor 110 may be a combination of these with a hardware accelerator or the like. The processor 110 controls each part in order to realize various functions of the server device 100 based on programs such as firmware, system software, and application software stored in the ROM 120 or the auxiliary storage device 140, etc. Also, the processor 110 executes the processes described later based on the program. Note that part or all of the program may be incorporated in the circuit of the processor 110.

[0014] The ROM 120 and the RAM 130 are the main storage devices of a computer centered around the processor 110. The ROM 120 is a non-volatile memory exclusively used for reading data. The ROM 120 stores, for example, firmware among the above programs. Also, the ROM 120 stores data used by the processor 110 when performing various processes, etc.

[0015] The RAM 130 is a memory used for reading and writing data. The RAM 130 is utilized as a work area or the like that stores data temporarily used by the processor 110 when performing various processes. The RAM 130 is typically a volatile memory.

[0016] The auxiliary storage device 140 is an auxiliary storage device of a computer centered around the processor 110. The auxiliary storage device 140 is, for example, an EEPROM (electric erasable programmable read-only memory), an HDD (hard disk drive), or a flash memory. The auxiliary storage device 140 stores, among the above programs, for example, system software and application software. Further, the auxiliary storage device 140 stores data used by the processor 110 to perform various processes, data generated by the processes in the processor 110, and various setting values. The data stored in the auxiliary storage device 140 includes, as an example, a charger DB (database) 141 and a user DB (database) 142. The auxiliary storage device 140 is an example of a storage device.

[0017] The charger DB 141 is a database that stores and manages information about the charger 400. The charger DB 141 includes, as an example, a charger table, a history table, and a success / failure table.

[0018] The charger table stores information about each charger 400 in association with the charger ID. The information includes position information indicating the installation position of the charger 400. The charger ID (identifier) is identification information uniquely assigned to each charger 400.

[0019] The history table is a table that stores the history of charging the vehicle 300 with the charger 400.

[0020] The success / failure table is a table that stores information regarding the success or failure of charging the vehicle 300 by each charger 400. Details of the success / failure table will be described later.

[0021] The user DB 142 is a database that stores and manages information about users (hereinafter simply referred to as "users") who use the charger information service and the vehicles 300 used by the users. The user DB 142 includes, as an example, a user table, a vehicle table, and an incentive table.

[0022] The user table is a table that stores the vehicles 300 used by each user. The user table stores by associating a user ID with a vehicle ID of the vehicle 300 used by the user specified by the user ID. The user ID is identification information uniquely assigned to each user. The vehicle ID is unique identification information for each vehicle. The vehicle ID may be identification information for Management System 1 or may be identification information used in other systems or the like. The identification information used in other systems or the like is, for example, a motor vehicle registration number, a vehicle number, a WCN (wireless call number), an in-vehicle device management number, or an ETC card number.

[0023] The vehicle table is a table that stores information about each vehicle 300. The information includes, as an example, the vehicle type of the vehicle 300. The vehicle table stores by associating a vehicle ID with a vehicle type for each vehicle 300. Note that the vehicle type is an example of the type of a moving body.

[0024] The incentive table is a table that stores the quantity of incentives given to each user. The incentive table stores the quantity by associating incentive information with the user ID, for example. The incentive information is information indicating the quantity of incentives given to the user. The server device 100 gives an incentive to a user who has provided information indicating the result of whether or not the vehicle 300 has been charged by the charger 400. The incentive is, for example, currency or electronic money. The incentive may be points. The incentive may be any one or more of currency, electronic money, and points.

[0025] The communication interface 150 is an interface for the server device 100 to communicate via a network NW or the like.

[0026] The bus 160 includes a control bus, an address bus, a data bus, etc., and transmits signals exchanged among the respective parts of the server device 100.

[0027] The terminal device 200 is, for example, a smartphone, a tablet terminal, a notebook PC, etc. The terminal device 200 may be an in-vehicle device of the vehicle 300. Also, a device such as a smartphone, a tablet terminal, or a notebook PC and the in-vehicle device of the vehicle 300 may cooperate to operate as the terminal device 200. The in-vehicle device is, for example, an ECU (electronic control unit), a car navigation system, or an ETC (electronic toll collection) in-vehicle unit, etc. The terminal device 200 includes, as an example, a processor 210, a ROM 220, a RAM 230, an auxiliary storage device 240, a first communication I / F (interface) 250, a second communication I / F 260, an input device 270, and an output device 280. And a bus 290 or the like connects these respective parts.

[0028] The processor 210 is the central part of a computer that performs processes such as operations and controls necessary for the operation of the terminal device 200, and performs various operations and processes. The processor 210 is, for example, a CPU, an MPU, an SoC, a DSP, a GPU, an ASIC, a PLD, or an FPGA, etc. Alternatively, the processor 210 is a combination of a plurality of these. Also, the processor 210 may be a combination of these with a hardware accelerator or the like. The processor 210 controls each part to realize various functions of the terminal device 200 based on programs such as firmware, system software, and application software stored in the ROM 220 or the auxiliary storage device 240, etc. Also, the processor 210 executes the processes described later based on the program. Note that part or all of the program may be incorporated in the circuit of the processor 210.

[0029] The ROM 220 and the RAM 230 are the main memory devices of a computer centered around the processor 210. The ROM 220 is a non-volatile memory used exclusively for reading data. The ROM 220 stores, for example, firmware among the above programs. Also, the ROM 220 stores data used by the processor 210 for performing various processes.

[0030] The RAM 230 is a memory used for reading and writing data. The RAM 230 is utilized as a work area for storing data temporarily used by the processor 210 for performing various processes. The RAM 230 is typically a volatile memory.

[0031] The auxiliary storage device 240 is an auxiliary storage device of a computer centered around the processor 210. The auxiliary storage device 240 is, for example, an EEPROM, an HDD, or a flash memory. The auxiliary storage device 240 stores, for example, system software and application software among the above programs. Also, the auxiliary storage device 240 stores data used by the processor 210 for performing various processes, data generated by the processing in the processor 210, and various setting values.

[0032] The first communication I / F 250 is an interface for the terminal device 200 to communicate with the vehicle 300 or the battery 310. The communication may be wired or wireless. Also, the communication may be performed via the network NW.

[0033] The second communication I / F 260 is an interface for the terminal device 200 to communicate via the network NW or the like. Note that the first communication I / F 250 may also serve as the second communication I / F 260.

[0034] The input device 270 receives operations by an operator of the terminal device 200 (hereinafter simply referred to as "operator"). The input device 270 is, for example, a keyboard, a keypad, a touch pad, a mouse, or a controller. Further, the input device 270 may be a device for voice input.

[0035] The output device 280 displays a screen for notifying various information to the operator or the like. The output device 280 is, for example, a display such as a liquid crystal display or an organic EL (electro-luminescence) display. Further, a touch panel can also be used as the input device 270 and the output device 280. That is, the display panel included in the touch panel can be used as the output device 280, and the pointing device by touch input included in the touch panel can be used as the input device 270.

[0036] The bus 290 includes a control bus, an address bus, a data bus, etc., and transmits signals exchanged between each part of the terminal device 200.

[0037] The vehicle 300 is an electric vehicle such as an automobile, a motorcycle, or an electric bicycle that can run by a battery 310 that can be charged by external power supply. The vehicle 300 is, for example, an EV (electric vehicle) or a PHEV (plug-in hybrid electric vehicle). The vehicle 300 includes the battery 310 as an example. Note that the vehicle 300 is an example of a moving body.

[0038] The battery 310 is, for example, a rechargeable secondary battery or a capacitor. The battery 310 is a power source that supplies power to each part of the vehicle 300.

[0039] The charger 400 is a charger that charges the battery 310 for the vehicle 300. The charger 400 is set, for example, at a charging station, a charging space, or a parking lot. That is, the charger 400 is a charger that can be used by an unspecified number of people.

[0040] Hereinafter, the operation of the management system 1 according to the embodiment will be described based on FIGS. 2 to 4 and the like. Note that the content of the processing in the following operation description is an example, and various processes capable of obtaining the same result can be appropriately used. FIGS. 2 and 3 are flowcharts showing an example of the processing by the processor 210 of the terminal device 200. The processor 210 executes the processing of FIGS. 2 and 3 based on a program stored in, for example, the ROM 220 or the auxiliary storage device 240. FIG. 4 is a flowchart showing an example of the processing by the processor 110 of the server device 100. The processor 110 executes the processing of FIG. 4 based on a program stored in, for example, the ROM 120 or the auxiliary storage device 140.

[0041] In step ST11 of FIG. 2, the processor 210 of the terminal device 200 determines whether to change the settings. The processor 210 determines to change the settings, for example, when an operation instructing a setting change is performed by an operator. If the processor 210 does not change the settings, it determines No in step ST11 and proceeds to step ST12.

[0042] In step ST12, the processor 210 determines whether the vehicle 300 has been charged. The processor 210 detects that the vehicle 300 has been charged by communicating with the vehicle 300 or the battery 310 via the first communication I / F 250. When the terminal device 200 is an in-vehicle device, the vehicle 300 for which it is determined whether charging has been performed is, for example, the vehicle 300 in which the terminal device 200 is mounted as an in-vehicle device. When the terminal device 200 is not an in-vehicle device, the vehicle 300 for which it is determined whether charging has been performed is, for example, the vehicle 300 that has been previously associated with the terminal device 200. Here, whether the vehicle 300 has been charged means regardless of whether the charging was successful or failed. If the processor 210 does not detect that the vehicle 300 has been charged, it determines No in step ST12 and proceeds to step ST13.

[0043] In step ST13, the processor 210 determines whether the operator inputs a charging result. For example, the processor 210 determines to input the charging result when an operation indicating that the operator inputs the charging result is performed. This operation is performed, for example, when the terminal device 200 does not have a function of detecting the charging of the vehicle 300 or when the detection fails. The input of the charging result will be described later. If the processor 210 determines not to input the charging result, it determines No in step ST13 and proceeds to step ST14.

[0044] In step ST14, the processor 210 determines whether a grant notification is received by the second communication I / F 260. If the processor 210 does not receive the grant notification, it determines No in step ST14 and returns to step ST11. Thus, the processor 210 enters a waiting state in which steps ST11 to ST14 are repeated until the settings are changed, the vehicle 300 is charged, the charging result is input, or the grant notification is received.

[0045] If the processor 210 determines to change the settings while in the waiting state of repeating steps ST11 to ST14, it determines Yes in step ST11 and proceeds to step ST15.

[0046] In step ST15, the processor 210 changes the settings based on the operation content by the operator. The setting content is stored in at least one of the auxiliary storage device 140 of the server device 100 and the auxiliary storage device 240 of the terminal device 200. The setting content includes, for example, a setting of whether to automatically transmit the charging result. The setting content includes, for example, information indicating which vehicle 300 the user is using and the vehicle type of the vehicle 300. After the process of step ST15, the processor 210 returns to step ST11.

[0047] When the processor 210 detects that the vehicle 300 has been charged while in a waiting state repeating steps ST11 to ST14, it determines Yes in step ST12 and proceeds to step ST16.

[0048] In step ST16, the processor 210 obtains the setting content from, for example, the auxiliary storage device 140 of the server device 100 or the auxiliary storage device 240 of the terminal device 200. Then, the processor 210 determines whether the setting content is set to automatically transmit the charging result. If the processor 210 is set to automatically transmit the charging result, it determines Yes in step ST16 and proceeds to step ST17.

[0049] In step ST17, the processor 210 generates result information. The result information is information for notifying the charging result. The result information includes, as an example, vehicle type identification information, charger identification information, date and time information, success or failure information, DC / AC information, and wireless information. If the charging fails, the result information may include reason information. If the charging is successful, the result information may include power information and power amount information. Note that when there is unknown information among the above-mentioned pieces of information, the processor 210 may generate result information including information indicating that the information is unknown. The processor 210 obtains each piece of information used for generating the result information from, for example, at least any one of the server device 100, the auxiliary storage device 240, the vehicle 300, and the charger 400. However, when another acquisition source is indicated in the following description, the processor 210 may obtain information from that acquisition source. The processor 210 obtains information from the server device 100 via, for example, the second communication I / F 260. The processor 210 obtains information from the vehicle 300 via, for example, the first communication I / F 250. The processor 210 obtains information from the charger 400 via, for example, the second communication I / F 260. Alternatively, the processor 210 obtains information from the charger 400 via the first communication I / F 250 and the vehicle 300.

[0050] The vehicle type specific information is information that enables the server device 100 to identify the vehicle type of the vehicle 300 that has been charged by the charger 400. The vehicle type specific information includes, for example, at least any one of the vehicle ID of the vehicle 300, the user ID of the user using the vehicle 300, and the vehicle type information. The vehicle type information is information indicating the vehicle type of the vehicle 300. Note that the vehicle type specific information is an example of the type specific information for identifying the type of the moving body.

[0051] The charger specific information is information that enables the server device 100 to identify the charger 400 that has charged the vehicle 300. The charger specific information is, for example, the position information indicating the installation position of the charger 400 or the charger ID. Note that the processor 210 acquires the position information using, for example, a GNSS (global navigation satellite system) such as GPS (Global Positioning System). Further, the processor 210 may acquire the position information using an indoor position information system.

[0052] The date and time information is information indicating the date and time when the charging was performed. Alternatively, the date and time information may be information indicating the date when the charging was performed.

[0053] The success or failure information is information indicating whether the charging was successful or not.

[0054] The DC / AC information is information indicating whether the power used for charging or intended to be used for charging is DC or AC.

[0055] The wireless information is information indicating whether the charging of the vehicle 300 is wireless charging (WPT (wireless power transfer)) or wired charging.

[0056] Failure information is information indicating the reason for the charging failure. Examples of reasons for charging failure include the vehicle 300 and the charger 400 not meeting the specifications, the software versions of the vehicle 300 or the charger 400 being old, abnormalities in the vehicle 300, abnormalities in the charger 400, and abnormalities in the electrical system supplying power to the charger 400. Note that an abnormality includes a failure.

[0057] Power information is information indicating the magnitude of the power used for charging.

[0058] Power quantity information is information indicating the quantity of power charged.

[0059] In step ST18, the processor 210 instructs the second communication I / F 260 to transmit the result information generated in step ST17 to the server device 100. In response to this transmission instruction, the second communication I / F 260 transmits the result information to the server device 100. The transmitted result information is received by the communication interface 150 of the server device 100.

[0060] If the processor 210 is not set to automatically transmit the charging result, it determines No in step ST16 and proceeds to step ST19.

[0061] In step ST19, the processor 210 generates an image corresponding to the notification screen. Then, the processor 210 instructs the output device 280 to display the generated image. In response to the display instruction, the output device 280 displays the notification screen.

[0062] The notification screen is a screen for notifying the operator that the charging of the vehicle 300 has been performed. As an example, the notification screen includes an input button and an end button. The input button is a button for the operator to operate when inputting the charging result. The end button is a button for operating to end the display of the notification screen without inputting the charging result.

[0063] In step ST20, the processor 210 determines whether the operator inputs the charging result. For example, when the input button is operated, the processor 210 determines that the charging result is input. For example, when the end button is operated, the processor 210 determines that the charging result is not input. If the processor 210 determines that the charging result is not input, it determines No in step ST20 and returns to step ST11. On the contrary, if the processor 210 determines that the charging result is input, it determines Yes in step ST20 and proceeds to step ST21.

[0064] Also, if the processor 210 determines that the charging result is input when it is in the waiting state of repeating steps ST11 to ST14, it determines Yes in step ST13 and proceeds to step ST21.

[0065] In step ST21, the processor 210 generates an image corresponding to the input screen. Then, the processor 210 instructs the output device 280 to display the generated image. Upon receiving the display instruction, the output device 280 displays the input screen.

[0066] The input screen is a screen for inputting the result of charging the vehicle 300 by the charger 400. As an example, the input screen can input vehicle type identification information, charger identification information, date and time information, success or failure information, DC / AC information, wireless information, reason information, power information, and power amount information. The input screen includes input fields for inputting each of these pieces of information. Also, as an example, the input screen includes a send button. The send button is a button for the operator to operate when instructing the terminal device 200 to send each piece of information input on the input screen.

[0067] The processor 210 may automatically input information into each input field on the input screen. For each piece of information to be input into each such input field, the processor 210 obtains it from at least one of, for example, the server device 100, the auxiliary storage device 240, the vehicle 300, and the charger 400. Here, the information input by the processor 210 is limited to information that is not unclear. However, the processor 210 may input a default value as an example of an entry or the like into the input field on the input screen.

[0068] The operator does not need to input information into all input fields. However, when transmitting the information input on the input screen, the input screen may require input for vehicle type identification information, charger identification information, and success or failure information.

[0069] In step ST22, the processor 210 determines whether to transmit each piece of information input on the input screen to the server device 100. The processor 210 determines to transmit, for example, when the transmit button displayed on the input screen is operated. If the processor 210 determines not to transmit the respective pieces of information, it determines No in step ST22 and repeats the process of step ST22. On the other hand, if the processor 210 determines to transmit the respective pieces of information, it determines Yes in step ST22 and proceeds to step ST23.

[0070] In step ST23, the processor 210 generates result information using the information input on the input screen. After generating the result information, the processor 210 instructs the second communication I / F 260 to transmit the result information to the server device 100. In response to this transmission instruction, the second communication I / F 260 transmits the result information to the server device 100. The transmitted result information is received by the communication interface 150 of the server device 100. After the process of step ST23, the processor 210 returns to step ST11.

[0071] As described above, the processor 210 functions as an example of a transmission unit that transmits charger identification information for identifying a charger and type identification information for identifying the type of the mobile body by performing the processing of step ST18 or step ST23 in cooperation with the second communication I / F 260. Further, the processor 210 functions as an example of a transmission control unit that controls the communication device to transmit the charger identification information and the type identification information by controlling the second communication I / F 260 to perform the processing of step ST18 or step ST23.

[0072] On the other hand, in step ST41 of FIG. 4, the processor 110 of the server device 100 determines whether result information has been received by the communication interface 150. If the processor 110 does not receive the result information, it determines No in step ST41 and proceeds to step ST42.

[0073] In step ST42, the processor 110 determines whether a status request has been received by the communication interface 150. If the processor 110 does not receive the status request, it determines No in step ST42 and returns to step ST41. Thus, the processor 110 enters a waiting state in which steps ST41 and ST42 are repeated until the result information or the status request is received.

[0074] If the result information is received while the processor 110 is in the waiting state of repeating steps ST41 and ST42, it determines Yes in step ST41 and proceeds to step ST43.

[0075] As described above, the processor 110 functions as an example of an input unit that receives, in cooperation with the communication interface 150, result information to receive inputs of success / failure information indicating whether charging of the mobile body by the charger was successful or failed, charger identification information for identifying the charger, and type identification information for identifying the type of the mobile body. Further, the processor 110 functions as an example of an input control unit that controls the communication interface 150 to receive result information, thereby controlling the communication device to receive inputs of success / failure information indicating whether charging of the mobile body by the charger was successful or failed, charger identification information for identifying the charger, and type identification information for identifying the type of the mobile body.

[0076] In step ST43, the processor 110 identifies the vehicle type indicated by the vehicle type identification information in the result information received in step ST41. When the vehicle type identification information includes vehicle type information, the processor 110 identifies the vehicle type indicated by the vehicle type information as the vehicle type indicated by the vehicle type identification information. When the vehicle type identification information includes a user ID, the processor 110 refers to the user table to obtain the vehicle ID associated with the user ID. Then, the processor 110 refers to the vehicle table to obtain the vehicle type associated with the vehicle ID. Thereby, the processor 110 identifies the vehicle type indicated by the vehicle type identification information. When the vehicle type identification information includes a vehicle ID, the processor 110 refers to the vehicle table to obtain the vehicle type associated with the vehicle ID. Thereby, the processor 110 identifies the vehicle type indicated by the vehicle type identification information.

[0077] In step ST44, the processor 110 identifies the charger 400 indicated by the charger identification information in the result information received in step ST41. When the charger identification information includes a charger ID, the processor 110 identifies the charger 400 by obtaining the charger ID. When the charger identification information includes location information, the processor 110 refers to the charger table to identify the charger 400 that is closest in location to the location information. Then, the processor 110 obtains the charger ID of the charger 400.

[0078] In step ST45, the processor 110 updates the history table and adds a history using the result information received in step ST42, the vehicle type specified in step ST43, and the information of the charger 400 specified in step ST44.

[0079] FIG. 5 is a diagram showing an example of the history table T1. The processor 110 adds one row to the history table T1, for example, and writes various information to the added row. Note that the processor 110 may leave a blank for unknown information. In FIG. 5, the blank is indicated by "-".

[0080] Note that when the reason indicated by the reason information is a specific reason, the processor 110 may skip the processing from step ST45 to step ST48 without updating the history table T1. The specific reason is, for example, an abnormality of the vehicle 300 or a failure of the vehicle 300.

[0081] In step ST46, the processor 110 updates the success / failure table T2 using the updated content of the history table T1.

[0082] FIG. 6 is a diagram showing an example of the success / failure table T2. As an example, the success / failure table T2 associates a combination of a charger ID and a vehicle type with success / failure aggregation information and reliability.

[0083] The success / failure aggregation information includes, for example, the number of successes, the number of failures, the number of trials, and the success probability. The success / failure aggregation information associated with the combination of the charger ID and the vehicle type indicates the aggregation result of the success or failure of charging the vehicle type by the charger 400 specified by the charger ID. The number of successes is the number of successful charges. The number of failures is the number of failed charges. The number of trials is the sum of the number of successes and the number of failures. (Success probability) = (Number of successes) ÷ (Number of trials). The success / failure aggregation information may include the failure probability. (Failure probability) = (Number of failures) ÷ (Number of trials). Also, the success / failure aggregation information may include at least any one of the number of successes, the number of failures, the success probability, and the failure probability.

[0084] Note that the processor 110 may calculate the number of successful times, the number of failed times, the number of trial times, and the success probability by using only the charging history performed during a predetermined period of direct return in the history table T1.

[0085] The processor 110 calculates the reliability using the number of trial times. The reliability is a value that increases as the number of trial times in the most recent predetermined period is higher. The reliability is a value indicating how reliable the success / failure aggregation information is. The smaller the number of trial times, the larger the error in the success probability and the failure probability. The reliability indicates the degree of this error. Note that the predetermined period may be the entire period.

[0086] From the above, the processor 110 functions as an example of a storage unit that stores, in the storage device, the success / failure result of charging the mobile body of the type specified by the type specification information with the charger specified by the charger specification information based on the information input to the input unit by performing at least one of step ST45 and step ST46 so that the charger used for charging and the type of the mobile body to be charged are known.

[0087] Further, the processor 110 functions as an example of an aggregation unit that calculates a reliability in which the value increases as the number of times of charging the mobile body of the type specified by the type specification information with the charger specified by the charger specification information increases by calculating the reliability.

[0088] Further, the processor 110 functions as an example of an aggregation unit that calculates at least one of the success probability and the failure probability of charging the mobile body of the type specified by the type specification information with the charger specified by the charger specification information by calculating at least one of the success probability and the failure probability.

[0089] In step ST47, the processor 110 updates the incentive table to give an incentive to the user who is the source of the result information. That is, the processor 110 adds the quantity of the newly given incentive to the quantity of the incentive indicated by the incentive information associated with the user ID included in the vehicle type identification information in the result information received in step ST41. Note that when the user ID is unknown, the processor 110 may skip the processes of step ST47 and step ST48.

[0090] The quantity of the given incentive may be fixed or may vary according to conditions. Also, the quantity of the incentive may be 0 depending on conditions. The processor 110 may determine the quantity of the incentive according to, for example, the time difference between the history added in step ST45 and the history with the latest date and time before the said history among the histories associated with the vehicle type specified in step ST44 and the charger ID of the charger 400 specified in step ST45. For example, the processor 110 increases the quantity of the incentive when the said difference is equal to or more than a predetermined value. For example, when the said difference is less than a predetermined value, the processor 110 sets the quantity of the incentive to 0. For example, the processor 110 increases the quantity of the incentive as the said difference is larger. Note that the date and time in the history with the latest date and time before the history added in step ST45 is an example of the date and time when charging was performed in the latest success or failure result stored in the storage device before the input of the success or failure information.

[0091] For the incentive given to each user, the processor 110 transfers it to the user's account, for example, in real time or in a lump sum at a later date. Alternatively, the processor 110 may give at least any one of currency, electronic money, and points to the user by other methods.

[0092] From the above, the processor 110 functions as an example of a giving unit that gives an incentive to the source of the information input to the input unit by performing the process of step ST47.

[0093] In step ST48, the processor 110 generates a grant notice. The grant notice includes information indicating the quantity of the incentive granted in step ST47. The grant notice is information for notifying the quantity. After generating the grant notice, the processor 110 instructs the communication interface 150 to transmit the grant notice to the terminal device 200. Upon receiving this transmission instruction, the communication interface 150 transmits the grant notice to the terminal device 200. The transmitted grant notice is received by the second communication I / F 260 of the terminal device 200. After the process of step ST48, the processor 110 returns to step ST41.

[0094] On the other hand, when the processor 210 of the terminal device 200 receives a grant notice while in the waiting state of repeating steps ST11 to ST14 in FIG. 2, it determines Yes in step ST14 and proceeds to step ST24.

[0095] In step ST24, the processor 210 generates an image corresponding to the grant screen. Then, the processor 210 instructs the output device 280 to display the generated image. Upon receiving the display instruction, the output device 280 displays the grant screen. After the process of step ST24, the processor 210 returns to step ST11.

[0096] The grant screen is a screen for notifying the operator of the quantity of the incentive included in the grant notice received in step ST14. The grant screen includes, as an example, an image indicating the quantity.

[0097] The management system 1 can view success / failure aggregation information and the like. The viewing of success / failure aggregation information and the like will be described with reference to FIGS. 3 and 4.

[0098] In step ST31 of FIG. 3, the processor 210 of the terminal device 200 generates an image corresponding to. Then, the processor 210 instructs the output device 280 to display the generated image. Upon receiving the display instruction, the output device 280 displays.

[0099] The browsing input screen is a screen for inputting information necessary for browsing such as success / failure aggregation information. As an example, the browsing input screen can input vehicle type identification information and charger identification information. The browsing input screen includes input fields for inputting each of these pieces of information. Note that the processor 210 may automatically input information into each input field of the browsing input screen. Also, as an example, the browsing input screen includes a send button. The send button is a button for an operator to operate when instructing the terminal device 200 to send each piece of information input into the browsing input screen.

[0100] In step ST32, the processor 210 determines whether to send each piece of information input into the browsing input screen to the server device 100. The processor 210 determines to send, for example, when the send button displayed on the browsing input screen is operated. If the processor 210 determines not to send the respective pieces of information, it determines No in step ST32 and repeats the process of step ST32. On the other hand, if the processor 210 determines to send the respective pieces of information, it determines Yes in step ST32 and proceeds to step ST33.

[0101] In step ST33, the processor 210 generates an information request. The information request includes, as an example, vehicle type identification information and charger identification information input on the browsing input screen. The information request is information that requests the success / failure aggregation information, reliability, and the latest charging history specified by the vehicle type identification information and the charger identification information to be transmitted. After generating the information request, the processor 210 instructs the second communication I / F 260 to transmit the information request to the server device 100. In response to this transmission instruction, the second communication I / F 260 transmits the information request to the server device 100. The transmitted information request is received by the communication interface 150 of the server device 100.

[0102] On the other hand, when a situation request is received while the processor 110 of the server device 100 is in a waiting state repeating steps ST41 and ST42 in FIG. 4, it determines Yes in step ST42 and proceeds to step ST47.

[0103] In step ST49, the processor 110 identifies the vehicle type indicated by the vehicle type identification information in the information request received in step ST42 in the same manner as in step ST43.

[0104] In step ST50, the processor 110 identifies the charger 400 indicated by the charger identification information in the information request received in step ST42 in the same manner as in step ST44.

[0105] In step ST51, the processor 110 refers to the success / failure table T2 to obtain the success / failure aggregation information and reliability. The success / failure aggregation information and the reliability are the success / failure aggregation information and reliability associated with the charger ID of the charger 400 identified in step ST44 and the vehicle type identified in step ST43. Also, the processor 110 refers to the history table T1 to obtain the latest charging history. The charging history is the one with the latest date and time among the histories associated with the charger ID of the charger 400 identified in step ST44 and the vehicle type identified in step ST43.

[0106] In step ST52, the processor 110 generates charging information. The charging information includes the success / failure aggregation information, reliability, and history obtained in step ST51. The charging information is information for notifying the success / failure aggregation information, the reliability, and the history. Note that the history does not include the vehicle ID and the user ID. After generating the charging information, the processor 110 instructs the communication interface 150 to transmit the charging information to the terminal device 200 that is the source of the situation request. In response to this transmission instruction, the communication interface 150 transmits the charging information to the terminal device 200. The transmitted charging information is received by the second communication I / F 260 of the terminal device 200. After the process of step ST52, the processor 110 returns to step ST41.

[0107] As described above, the processor 110, in cooperation with the communication interface 150, performs the process of step ST42 and transmits the success / failure aggregation information, and in response to receiving the charger identification information and the type identification information from the terminal device, functions as an example of a communication unit that transmits at least any one of the number of successful charges, the number of failed charges, the success probability, and the failure probability to the moving body of the type specified by the type identification information using the charger specified by the charger identification information. Further, the processor 110, in cooperation with the communication interface 150, performs the process of step ST42 and transmits the history, and in response to receiving the charger identification information and the type identification information from the terminal device, functions as an example of a communication unit that transmits the latest success / failure result of charging the moving body of the type specified by the type identification information using the charger specified by the charger identification information.

[0108] On the other hand, in step ST34 of FIG. 3, the processor 210 of the terminal device 200 waits for the charging information to be received by the second communication I / F 260. If the charging information is received, the processor 210 determines Yes in step ST34 and proceeds to step ST35.

[0109] In step ST35, the processor 210 generates an image corresponding to the charging screen. Then, the processor 210 instructs the output device 280 to display the generated image. In response to the display instruction, the output device 280 displays the charging screen. After the processing of step ST35, the processor 210 returns to step ST31.

[0110] The charging screen is a screen for notifying the operator of the content of the success / failure aggregation information, the reliability, and the history included in the charging information received in step ST33. As an example, the charging screen includes an image indicating the success / failure aggregation information, the reliability, and the history.

[0111] According to the management system 1 of the embodiment, the server device 100 receives the input of success / failure information, charger identification information, and vehicle type identification information. Then, the server device 100 of the embodiment stores the success / failure aggregation information of charging so that the charger 400 used for charging and the vehicle type of the vehicle 300 to be charged can be known. Thereby, the server device 100 of the embodiment can grasp the success / failure status of charging for each vehicle type of each charger 400. Also, by using the server device 100 of the embodiment, the user can know the success / failure status of charging for each vehicle type of each charger 400.

[0112] Also, according to the management system 1 of the embodiment, the server device 100 receives the charger identification information and the vehicle type identification information from the terminal device 200. Then, in response to this reception, the server device 100 of the embodiment transmits the success / failure aggregation information of charging to the vehicle type specified by the vehicle type identification information at the charger 400 specified by the charger identification information to the terminal device 400. Thereby, the user can know the success / failure aggregation information of charging from a specific charger 400 to a specific vehicle type.

[0113] Also, according to the management system 1 of the embodiment, the server device 100 receives charger identification information and vehicle type identification information from the terminal device 200. Then, in response to this reception, the server device 100 of the embodiment transmits to the terminal device 400 the latest success or failure result of charging the vehicle type specified by the vehicle type identification information with the charger 400 specified by the charger identification information. Thereby, the user can know the latest success or failure result of charging a specific vehicle type with a specific charger 400.

[0114] Also, according to the management system 1 of the embodiment, the server device 100 obtains a reliability that increases as the number of trials increases. Thereby, the user can grasp how reliable the success or failure aggregation information is.

[0115] Also, according to the management system 1 of the embodiment, the server device 100 calculates at least one of a success probability and a failure probability. Thereby, the user can know the probability at which the charger 400 can charge.

[0116] Also, according to the management system 1 of the embodiment, the server device 100 gives an incentive to the user who is the sender of the result information. The incentive serves as a motivation for the user to transmit the result information.

[0117] Also, according to the management system 1 of the embodiment, the server device 100 determines the quantity of the incentive according to the date and time of the history. If the quantity of the incentive increases when the date and time of the latest history is old, the user can be made to use the charger 400 with a small number of history records.

[0118] The above embodiments can also be modified as follows. In the above embodiment, the server device 100 transmits the latest charging history to the terminal device 200. However, the server device 100 may transmit N charging histories counted from the latest to the terminal device 200. N is an integer of 1 or more. The value of N is determined based on, for example, an operation by an operator. Alternatively, the value of N may be determined by an administrator or designer of the management system 1, etc.

[0119] The terminal device 200 may be one that cannot automatically transmit the charging result. Also, the terminal device 200 may be one that can only transmit the charging result automatically.

[0120] In the above embodiment, the case of charging the vehicle 300 has been described as an example. However, the management system of the embodiment is also applicable to the case of charging a moving body other than the vehicle 300. Examples of moving bodies other than the vehicle 300 include bicycles, airplanes, and ships. In the case of a moving body other than the vehicle 300, the management system of the embodiment may use a model or a ship type, etc. instead of the vehicle type. A model or a ship type, etc. is an example of the type of a moving body. As described above, the server device of the embodiment can grasp the charging status of chargers for each type of moving body.

[0121] The moving body of the embodiment may be driverless.

[0122] In the above embodiment, part of the processing performed by the terminal device 200 may be performed by the server device 100. In the above embodiment, part of the processing performed by the server device 100 may be performed by the terminal device 200.

[0123] A device different from the server device 100 may include the storage device of the embodiment.

[0124] Each device of the embodiment may be composed of a plurality of devices.

[0125] The processor 110 and the processor 210 may implement part or all of the processing realized by the program in the above embodiment by the hardware configuration of the circuit.

[0126] The program that implements the processing of the embodiment is transferred, for example, in a state stored in a non-temporary computer-readable storage medium in the device. However, the device may be transferred in a state where the program is not stored. And the program may be transferred separately and written into the device. The transfer of the program at this time can be realized, for example, by recording it on a removable non-temporary computer-readable storage medium or by downloading via a network such as the Internet or a LAN.

[0127] As described above, the embodiments of the present invention have been described, but they are shown as examples and do not limit the scope of the present invention. The embodiments of the present invention can be implemented in various modes without departing from the gist of the present invention.

Explanation of Reference Numerals

[0128] 1 Management system 100 Server device 110, 210 Processors 120, 220 ROM 130, 230 RAM 140, 240 Auxiliary storage device 141 Charger DB 142 User DB 150 Communication interface 160, 290 Bus 200 Terminal device 250 First communication I / F 260 Second communication I / F 270 Input device 280 Output device 300 Vehicle 310 Battery 400 Charger

Claims

1. an input unit that receives input of success / failure information indicating whether charging of a mobile object by a charger has been successful or unsuccessful, charger identification information that identifies the charger, and type identification information that identifies a type of the mobile object; A management device comprising: a memory unit that stores in a storage device the success or failure result of charging the mobile body of the type identified by the type identification information at the charger identified by the charger identification information based on the information input to the input unit, so that the charger used for charging and the type of the mobile body to be charged can be identified.

2. The management device according to claim 1, further comprising a communication unit that transmits at least one of the number of successful charging attempts, the number of failures, the success probability, and the failure probability of charging the mobile body of the type identified by the type identification information at the charger identified by the charger identification information in response to receiving the charger identification information and the type identification information from a terminal device.

3. The management device of claim 1, further comprising a communication unit that transmits the latest success / failure result of charging the mobile body of the type identified by the type identification information at the charger identified by the charger identification information in response to receiving the charger identification information and the type identification information from a terminal device.

4. The management device according to claim 1 , further comprising an aggregation unit that calculates a reliability value that increases as the number of times the charger identified by the charger identification information has charged the mobile object of the type identified by the type identification information increases.

5. The management device according to claim 1 , further comprising an aggregation unit that calculates at least one of a success probability and a failure probability of charging the mobile object of the type identified by the type identification information at the charger identified by the charger identification information.

6. The management device according to claim 1 , further comprising an incentive providing unit that provides an incentive to a sender of the information input to the input unit.

7. The management device according to claim 6 , wherein the granting unit determines the amount of incentive to be granted depending on the date and time when charging was performed in the latest success / failure result stored in the storage device before the success / failure information was input.

8. A terminal device and a management device are included, the terminal device includes a transmission unit that transmits charger identification information that identifies a charger and type identification information that identifies a type of a moving object; The management device includes: an input unit that receives input of success / failure information indicating whether charging of the moving object by the charger has succeeded or failed, the charger identification information, and the type identification information; A management system comprising: a memory unit that stores in a storage device the success or failure result of charging the mobile body of the type identified by the type identification information at the charger identified by the charger identification information based on the information input to the input unit, so that the charger used for charging and the type of the mobile body to be charged can be identified.

9. a management system is configured together with a management device including an input unit that receives input of success / failure information indicating whether charging of a mobile object with a charger has been successful or unsuccessful, charger identification information that identifies the charger, and type identification information that identifies the type of the mobile object, and a storage unit that stores in a storage device the success / failure result of charging the mobile object of the type identified by the type identification information at the charger identified by the charger identification information based on the information input to the input unit, so that the charger used for charging and the type of the mobile object to be charged can be known; A terminal device including a transmitter that transmits the charger identification information and the type identification information.

10. A processor included in a management device including a communication device, an input control unit that controls the communication device to receive input of success / failure information indicating whether charging of the mobile object with the charger has been successful or unsuccessful, charger identification information that identifies the charger, and type identification information that identifies the type of the mobile object; A program that functions as a memory unit that stores in a storage device the success or failure result of charging the mobile body of the type identified by the type identification information at the charger identified by the charger identification information based on information input to the communication device, so that the charger used for charging and the type of the mobile body to be charged can be identified.

11. A management system is configured together with a management device having an input unit that receives input of success / failure information indicating whether charging of a mobile object with a charger was successful or unsuccessful, charger identification information that identifies the charger, and type identification information that identifies the type of the mobile object, and a memory unit that stores the success / failure result of charging the mobile object of the type identified by the type identification information with the charger identified by the charger identification information based on the information input to the input unit in a storage device so that the charger used for charging and the type of the mobile object to be charged can be known, and a processor of a terminal device having a communication device, a program causing the communication device to function as a transmission control unit that controls the communication device to transmit the charger identifying information and the type identifying information;

Images