Management device, management system, terminal device, and program

Abstract

The problem to be solved by the present invention is to provide a management device, a management system, a terminal device, and a program with which it is possible to grasp the charging status of a charger for each type of moving body. In order to solve the problem, a management device according to an embodiment is provided with an input unit and a storage unit. The input unit receives input of success / failure information indicating whether charging of a moving body in a charger is successful or failed, charger specifying information specifying the charger, and type specifying information specifying the type of the moving body. On the basis of the information input to the input unit, the storage unit determines the type of the charger used in charging and the type of the moving body to be charged. A storage device stores a success / failure result of charging the moving body of the type specified by the type specifying information in the charger specified by the charger specifying information. The storage device also stores the success / failure result of charging the moving body of the type specified by the type specifying information in the charger specified by the charger specifying information.

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 information on the operating status of vehicle chargers.

[0003] [Prior Technical Literature]

[0004] (Patent Document)

[0005] Patent Document 1: Japanese Patent Application Publication No. 2020-124061 Summary of the invention

[0006] [Problems to be solved by the invention]

[0007] However, none of the services provide charging conditions for each vehicle type. Therefore, if the charger cannot charge due to a vehicle type matching problem, the user of the service will lose the opportunity to charge even if it is actually the turn of their vehicle to charge. In addition, conversely, sometimes the charger that is in the service status as charging cannot charge their vehicle.

[0008] An object of the embodiments of the present invention is to provide a management device, a management system, a terminal device, and a program that can grasp the charging status of a charger for each type of mobile body.

[0009] [Technical means to solve the problem]

[0010] The management device of 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 mobile object in the charger is successful or failed, charger identification information identifying the charger, and type identification information identifying the type of the mobile object. The storage unit stores the success or failure result of charging the mobile object of the type identified by the type identification information in the charger identified by the charger identification information in the storage device in such a manner that the charger used for charging and the type of the mobile object to be charged can be known based on the information input to the input unit.

[0011] (Effects of the Invention)

[0012] The present invention can grasp the charging status of the charger for each type of mobile object. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 This is a block diagram showing an example of the configuration of a management system according to an embodiment and main components included in the management system.

[0014] Figure 2 It is depicted by Figure 1 A flowchart of an example of processing performed by a processor of a terminal device in .

[0015] Figure 3 It is depicted by Figure 1 A flowchart of an example of processing performed by a processor of a terminal device in .

[0016] Figure 4 It is depicted by Figure 1 A flowchart of an example of processing performed by a processor of a server device in.

[0017] Figure 5 This is a diagram showing an example of a history table.

[0018] Figure 6 This is a diagram showing an example of a success / failure table. DETAILED DESCRIPTION

[0019] The management system of the embodiment is described below using the drawings. In addition, the scales of the parts of the drawings used in the following description of the embodiment are sometimes appropriately changed. In addition, for the convenience of explanation, the drawings used in the following description of the embodiment are sometimes shown with the structure omitted. In addition, in the drawings and this specification, the same symbol represents the same component.

[0020] Figure 1 It is a block diagram illustrating an example of the structure of the main parts of the management system 1 and the components included in the management system 1 according to the implementation mode. In addition, each component of the device can be built-in or external. The management system 1 manages the information about the success and failure of charging of the vehicle 300 for each charger 400. In addition, the management system 1 provides a charger information service. As an example, the management system 1 includes a server device 100, a terminal device 200, a vehicle 300 and a charger 400. In addition, the management system 1 may also include a part of them. The number of each device is not limited. Typically, the number of terminal devices 200, vehicles 300 and chargers 400 is multiple.

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

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

[0023] The processor 110 is the core part of the computer that performs the operations and control required for the operation of the server device 100, and performs various operations and processes. The processor 110 is, for example, a central processing unit (CPU), a microprocessor (MPU), a system on a chip (SoC), a digital signal processor (DSP), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a programmable logic device (PLD) or a field-programmable gate array (FPGA). Alternatively, the processor 110 is a combination of multiple of these. In addition, the processor 110 can also be a combination of hardware accelerators and the like. The processor 110 controls each part based on the firmware, system software, and application software programs stored in the ROM 120 or the auxiliary storage device 140, so as to realize various functions of the server device 100. In addition, the processor 110 performs the processing described below based on the program. In addition, part or all of the program can also be incorporated into the circuit of the processor 110.

[0024] ROM 120 and RAM 130 are main storage devices of a computer with processor 110 as the core. ROM 120 is a non-volatile memory dedicated to reading data. ROM 120 stores, for example, firmware among the above-mentioned programs. In addition, ROM 120 also stores data used by processor 110 when performing various processes.

[0025] The RAM 130 is a memory used for reading and writing data. The RAM 130 is used as a work area for storing data temporarily used when the processor 110 performs various processes, etc. The RAM 130 is typically a volatile memory.

[0026] The auxiliary storage device 140 is an auxiliary storage device of a computer with the processor 110 as the core. The auxiliary storage device 140 is, for example, an electrically erasable programmable read-only memory (EEPROM), a hard disk drive (HDD), or a flash memory. The auxiliary storage device 140 stores the above-mentioned programs, such as system software and application software. In addition, the auxiliary storage device 140 stores data used by the processor 110 when performing various processes, data generated by the processes in the processor 110, and various setting values. As an example, the data stored in the auxiliary storage device 140 includes a charger database (DB) 141 and a user DB 142. The auxiliary storage device 140 is an example of a storage device.

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

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

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

[0030] The success / failure table is a table that stores information on the success / failure of charging vehicle 300 in each charger 400. The details of the success / failure table will be described later.

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

[0032] The user table is a table that stores the vehicles 300 used by each user. The user table stores the user ID and the vehicle ID of the vehicle 300 used by the user identified by the user ID in association. The user ID is identification information uniquely assigned to each user. The vehicle ID is identification information unique to each vehicle. The vehicle ID can be identification information used for the management system 1 or identification information used in other systems. The identification information used in other systems is, for example, a car registration number, a vehicle number, a wireless call number (WCN), a vehicle-mounted device management number, or an electronic toll collection (ETC) card number.

[0033] The vehicle table is a table that stores information about each vehicle 300. As an example, the information includes the model of the vehicle 300. The vehicle table stores the vehicle ID and the model in association with each vehicle 300. The model is an example of the type of the moving body.

[0034] The reward table is a table storing the number of rewards given to each user. As an example, the reward table stores the number by associating reward information with a user ID. The reward information is information indicating the number of rewards given to the user. The server device 100 gives a reward to a user who provides information indicating the success or failure of charging the vehicle 300 in the charger 400. The reward is, for example, legal tender or electronic currency. The reward may also be points. The reward may also be one or more of legal tender, electronic currency, and points.

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

[0036] The bus 160 includes a control bus, an address bus, a data bus, and the like, and transmits signals exchanged between the various components of the server device 100 .

[0037] The terminal device 200 is, for example, a smart phone, a tablet terminal, or a notebook personal computer (Personal Computer, PC). The terminal device 200 may also be a vehicle-mounted device of the vehicle 300. In addition, a device such as a smart phone, a tablet terminal, or a notebook PC may cooperate with a vehicle-mounted device of the vehicle 300 to operate as the terminal device 200. The vehicle-mounted device is, for example, an electronic control unit (electronic control unit, ECU), a car navigation system, or an ETC vehicle-mounted device. As an example, the terminal device 200 includes a processor 210, a ROM 220, a RAM 230, an auxiliary storage device 240, a first communication interface (interface, I / F) 250, a second communication I / F 260, an input device 270, and an output device 280. In addition, a bus 290 and the like connect their respective parts.

[0038] The processor 210 is the central part of the computer that performs the operations and controls required for the operation of the terminal device 200, and performs various operations and processes. The processor 210 is, for example, a CPU, an MPU, a SoC, a DSP, a GPU, an ASIC, a PLD, or an FPGA. Alternatively, the processor 210 is a combination of multiple of these. In addition, the processor 210 may also be a combination of hardware accelerators, etc. The processor 210 controls each part based on the firmware, system software, and application software programs stored in the ROM 220 or the auxiliary storage device 240, etc., so as to realize the various functions of the terminal device 200. In addition, the processor 210 performs the processing described later based on the program. In addition, part or all of the program may also be incorporated into the circuit of the processor 210.

[0039] ROM 220 and RAM 230 are main storage devices of a computer with processor 210 as the core. ROM 220 is a non-volatile memory dedicated to reading data. ROM 220 stores, for example, firmware among the above-mentioned programs. In addition, ROM 220 also stores data used by processor 210 for various processing.

[0040] The RAM 230 is a memory used for reading and writing data. The RAM 230 is used as a work area for storing data temporarily used when the processor 210 performs various processes, etc. The RAM 230 is typically a volatile memory.

[0041] The auxiliary storage device 240 is an auxiliary storage device of a computer with the processor 210 as the core. 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-mentioned programs. In addition, the auxiliary storage device 240 stores data used when the processor 210 performs various processes, data generated by the processes in the processor 210, and various setting values.

[0042] 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, and may be performed via the network NW.

[0043] The second communication I / F 260 is an interface for the terminal device 200 to communicate via the network NW etc. In addition, the first communication I / F 250 may also serve as the second communication I / F 260 .

[0044] The input device 270 receives an operation performed by an operator of the terminal device 200 (hereinafter referred to as "operator"). The input device 270 is, for example, a keyboard, a keypad, a touch panel, a mouse, or a controller. In addition, the input device 270 may also be a device for voice input.

[0045] The output device 280 displays a screen for notifying the operator of various information. The output device 280 is, for example, a display such as a liquid crystal display or an organic electroluminescence (EL) display. In addition, a touch screen may be used as the input device 270 and the output device 280. That is, the display panel of the touch screen may be used as the output device 280, and the pointing device based on touch input of the touch screen may be used as the input device 270.

[0046] The bus 290 includes a control bus, an address bus, a data bus, and the like, and transmits signals exchanged between various components of the terminal device 200 .

[0047] The vehicle 300 is an electric vehicle such as a car, a motorcycle, or an electric bicycle that can be driven by a battery 310, and the battery 310 can be charged by external power supply. The vehicle 300 is, for example, an electric vehicle (EV) or a plug-in hybrid electric vehicle (PHEV). As an example, the vehicle 300 includes a battery 310. In addition, the vehicle 300 is an example of a mobile body.

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

[0049] The charger 400 is a charger for charging the battery 310 for the vehicle 300. The charger 400 is installed at, for example, a charging station, a charging space, or a parking lot, etc. That is, an unspecified number of chargers 400 can be used.

[0050] The following is based on Figure 2 to Figure 4 The operation of the management system 1 according to the embodiment will be described below. The contents of the processing in the following operation description are just examples, and various processing that can obtain the same result can be used as appropriate. Figure 2 and Figure 3 FIG. 2 is a flowchart showing an example of processing performed by the processor 210 of the terminal device 200. The processor 210 executes, for example, a program stored in the ROM 220 or the auxiliary storage device 240. Figure 2 and Figure 3 processing. Figure 4 FIG. 1 is a flowchart showing an example of processing performed by the processor 110 of the server device 100. The processor 110 executes, for example, a program stored in the ROM 120 or the auxiliary storage device 140. Figure 4 processing.

[0051] exist Figure 2 In step ST11, the processor 210 of the terminal device 200 determines whether to change the setting. For example, when the operator performs an operation to instruct the setting change, the processor 210 determines that the setting is to be changed. If the setting is not to be changed, the processor 210 determines that it is No in step ST11 and proceeds to step ST12.

[0052] In step ST12, the processor 210 determines whether the vehicle 300 is charged. The processor 210 detects that the vehicle 300 is charged by communicating with the vehicle 300 or the battery 310 via the first communication I / F 250. In the case where the terminal device 200 is a vehicle-mounted device, the object of the determination of whether the charging is performed, that is, the vehicle 300, is, for example, the vehicle 300 on which the terminal device 200 is mounted as a vehicle-mounted device. In the case where the terminal device 200 is not a vehicle-mounted device, the object of the determination of whether the charging is performed, that is, the vehicle 300, is, for example, the vehicle 300 that has been previously associated with the terminal device 200. Here, the so-called charging of the vehicle 300 has nothing to do with whether the charging is successful or failed. If the charging of the vehicle 300 is not detected, the processor 210 determines No in step ST12 and proceeds to step ST13.

[0053] In step ST13, the processor 210 determines whether the operator inputs the charging result. For example, when the operator performs an operation indicating inputting the charging result, the processor 210 determines that the charging result is to be input. 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 is not smooth. The input of the charging result will be described below. If it is not determined that the charging result is to be input, the processor 210 determines No in step ST13 and proceeds to step ST14.

[0054] In step ST14, the processor 210 determines whether a notification of giving is received via the second communication I / F 260. If a notification of giving is not received, the processor 210 determines No in step ST14 and returns to step ST11. Then, the processor 210 enters a standby state in which steps ST11 to ST14 are repeated until the setting is changed, the vehicle 300 is charged, the charging result is input, or a notification of giving is received.

[0055] If it is determined that the setting is to be changed in the standby state of repeating steps ST11 to ST14 , the processor 210 makes a Yes determination in step ST11 and proceeds to step ST15 .

[0056] In step ST15, the processor 210 changes the setting based on the operation content of 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, whether to automatically send the charging result. The setting content includes, for example, information indicating which vehicle 300 the user used and the model of the vehicle 300. After processing step ST15, the processor 210 returns to step ST11.

[0057] If the charging of the vehicle 300 is detected during the standby state of repeating steps ST11 to ST14 , the processor 210 makes a Yes determination in step ST12 and proceeds to step ST16 .

[0058] 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 a setting for automatically sending the charging result. If it is a setting for automatically sending the charging result, the processor 210 determines Yes in step ST16 and proceeds to step ST17.

[0059] In step ST17, the processor 210 generates result information. The result information is information that notifies the charging result. As an example, the result information includes vehicle type identification information, charger identification information, date and time information, success or failure information, DC / AC information, and wireless information. In the case of charging failure, the result information may also include cause information. In the case of successful charging, the result information may also include power information and power information. In addition, in the case where there is unknown information among the above information, the processor 210 may also generate result information including information indicating that the information is unknown. For each information used in the generation of the result information, the processor 210 obtains it from at least one of the server device 100, the auxiliary storage device 240, the vehicle 300, and the charger 400. Among them, when other acquisition locations are shown in the following description, the processor 210 may also obtain information from the acquisition location. The processor 210 obtains information from the server device 100, for example, via the second communication I / F 260. The processor 210 obtains information from the vehicle 300, for example, via the first communication I / F 250. Processor 210 acquires information from charger 400 via second communication I / F 260 , for example. Alternatively, processor 210 acquires information from charger 400 via first communication I / F 250 and vehicle 300 .

[0060] The vehicle model identification information is information that enables the server device 100 to identify the vehicle model of the vehicle 300 charged by the charger 400. The vehicle model identification information includes, for example, at least one of the vehicle ID of the vehicle 300, the user ID of the user who uses the vehicle 300, and the vehicle model information. The vehicle model information is information indicating the vehicle model of the vehicle 300. In addition, the vehicle model identification information is an example of type identification information that identifies the type of the mobile object.

[0061] The charger identification information is information that enables the server device 100 to identify the charger 400 that charges the vehicle 300. The charger identification information is, for example, location information indicating the installation location of the charger 400 or a charger ID. In addition, the processor 210 obtains the location information using, for example, a global navigation satellite system (GNSS) such as a global positioning system (GPS). In addition, the processor 210 may also obtain the location information using an indoor location information system.

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

[0063] The success or failure information is information indicating whether charging is successful.

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

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

[0066] The failure information is information indicating the reason for the charging failure. The reasons for the charging failure include the specifications of the vehicle 300 and the charger 400 not being in accordance with each other, the vehicle 300 or the charger 400 being an old software version, the vehicle 300 being abnormal, the charger 400 being abnormal, and the electrical system supplying power to the charger 400 being abnormal. In addition, the abnormality includes a malfunction.

[0067] The electric power information is information indicating the amount of electric power used for charging.

[0068] The electric power information is information indicating the amount of electric power being charged.

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

[0070] If the setting is not to automatically transmit the charging result, processor 210 makes a No determination in step ST16 and proceeds to step ST19.

[0071] In step ST19, processor 210 generates an image corresponding to the notification screen. Processor 210 then instructs output device 280 to display the generated image. Output device 280 receives the display instruction and displays the notification screen.

[0072] The notification screen is a screen for notifying the operator that the vehicle 300 is being charged. 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 when the display of the notification screen is terminated without inputting the charging result.

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

[0074] If it is determined that the charging result is to be inputted in the standby state of repeating steps ST11 to ST14 , processor 210 determines Yes in step ST13 and proceeds to step ST21 .

[0075] In step ST21, processor 210 generates an image corresponding to the input screen. Then, processor 210 instructs output device 280 to display the generated image. Output device 280 receives the display instruction and displays the input screen.

[0076] The input screen is a screen for inputting the result of charging the vehicle 300 in the charger 400. As an example, the input screen can input vehicle type determination information, charger determination information, date and time information, success or failure information, DC / AC information, wireless information, cause information, power information, and power information. The input screen includes an input field for inputting each of these information. In addition, 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 of the information input to the input screen.

[0077] The processor 210 may also automatically input information into each input field of the input screen. For each piece of information input into each input field, the processor 210 obtains it from at least one of the server device 100, the auxiliary storage device 240, the vehicle 300, and the charger 400, for example. Here, the information input by the processor 210 is limited to clear information. Among them, the processor 210 may also input a default value into the input field of the input screen as an example of entry, etc.

[0078] The operator does not need to input information in all the input fields. In the case where the information input to the input screen is to be sent, the vehicle type determination information, charger determination information, and success / failure information may also be required to be input on the input screen.

[0079] In step ST22, the processor 210 determines whether to send each information input to the input screen to the server device 100. For example, when the send button displayed on the input screen is operated, the processor 210 determines that it is to be sent. If it is not determined that the information is to be sent, the processor 210 determines No in step ST22 and repeats the process of step ST22. On the contrary, if it is determined that the information is to be sent, the processor 210 determines Yes in step ST22 and proceeds to step ST23.

[0080] In step ST23, the processor 210 generates result information using the information input to the input screen. After generating the result information, the processor 210 instructs the second communication I / F 260 to send the result information to the server device 100. The second communication I / F 260 receives the instruction to send and sends the result information to the server device 100. The sent result information is received by the communication interface 150 of the server device 100. After processing step ST23, the processor 210 returns to step ST11.

[0081] According to the above, the processor 210 functions as an example of a transmission unit to transmit the charger identification information for identifying the charger and the type identification information for identifying the type of the mobile object by cooperating with the second communication I / F 260 to perform the processing of step ST18 or ST23. In addition, 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 ST23.

[0082] On the other hand, Figure 4 In step ST41, the processor 110 of the server device 100 determines whether the result information is received via the communication interface 150. If the result information is not received, the processor 110 determines No in step ST41 and proceeds to step ST42.

[0083] In step ST42, the processor 110 determines whether a status request is received via the communication interface 150. If a status request is not received, the processor 110 determines No in step ST42 and returns to step ST41. Then, the processor 110 enters a standby state, in which step ST41 and step ST42 are repeated until result information or a status request is received.

[0084] If the result information is received while the processor 110 is in the standby state of repeating steps ST41 and ST42 , the processor 110 makes a Yes determination in step ST41 and proceeds to step ST43 .

[0085] According to the above, the processor 110 functions as an example of an input unit by cooperating with the communication interface 150 to receive the result information, and receives input of success or failure information indicating whether the charging of the mobile body in the charger is successful or failed, charger determination information for determining the charger, and type determination information for determining the type of the mobile body. In addition, the processor 110 functions as an example of an input control unit for controlling the communication device by controlling the communication interface 150 to receive the result information, and receives input of success or failure information indicating whether the charging of the mobile body in the charger is successful or failed, charger determination information for determining the charger, and type determination information for determining the type of the mobile body.

[0086] In step ST43, the processor 110 determines the vehicle model represented by the vehicle model determination information in the result information received in step ST41. In the case where the vehicle model determination information includes the vehicle model information, the processor 110 determines the vehicle model represented by the vehicle model information as the vehicle model represented by the vehicle model determination information. In the case where the vehicle model determination information includes the 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 model associated with the vehicle ID. Thus, the processor 110 determines the vehicle model represented by the vehicle model determination information. In the case where the vehicle model determination information includes the vehicle ID, the processor 110 refers to the vehicle table to obtain the vehicle model associated with the vehicle ID. Thus, the processor 110 determines the vehicle model represented by the vehicle model determination information.

[0087] In step ST44, the processor 110 identifies the charger 400 indicated by the charger identification information in the result information received in step ST41. In the case where the charger identification information includes a charger ID, the processor 110 identifies the charger 400 by acquiring the charger ID. In the case where the charger identification information includes location information, the processor 110 refers to the charger table to identify the charger 400 whose location is closest to the location information. Then, the processor 110 acquires the charger ID of the charger 400.

[0088] In step ST45 , processor 110 updates the history table to add the history using the result information received in step ST42 , the vehicle type determined in step ST43 , and the information of charger 400 determined in step ST44 .

[0089] Figure 5 1 is a diagram showing an example of the history table T1. The processor 110, for example, adds one row to the history table T1 and writes various information in the added row. In addition, the processor 110 may leave the column blank for unknown information. Figure 5 In the table, a blank column is indicated by a “-”.

[0090] Furthermore, the processor 110 may cancel the processing of steps ST45 to ST48 without updating the history table T1 when the cause indicated by the cause information is a specific cause. The specific cause may be, for example, an abnormality of the vehicle 300 or a breakdown of the vehicle 300 .

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

[0092] Figure 6 2 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 model with success / failure aggregate information and reliability.

[0093] The success and failure aggregate information includes, for example, the number of successes, the number of failures, the number of trials, and the success probability. The success and failure aggregate information associated with the combination of the charger ID and the vehicle model indicates the aggregate result of the success or failure of the charging of the vehicle model by the charger 400 determined by the charger ID. The number of successes is the number of successes of the charging. The number of failures is the number of failures of the charging. The number of trials is the sum of the number of successes and the number of failures. (Probability of success) = (number of successes) ÷ (number of trials). The success and failure aggregate information may also include the failure probability. (Probability of failure) = (number of failures) ÷ (number of trials). In addition, the success and failure aggregate information may also include at least one of the number of successes, the number of failures, the success probability, and the failure probability.

[0094] Alternatively, the processor 110 may determine the number of successes, the number of failures, the number of attempts, and the success probability using only the history of charging performed in the current predetermined period in the history table T1.

[0095] Processor 110 uses the number of trials to calculate reliability. Reliability is a value that increases as the number of trials in the most recent specified period increases. Reliability is a value that indicates how reliable the success and failure aggregate information is. The fewer the number of trials, the greater the error in the success probability and the failure probability. Reliability shows the extent of the error. In addition, the specified period may also be all periods.

[0096] According to the above, the processor 110 functions as an example of a storage unit by performing at least any one of steps ST45 and ST46, and stores in the storage device the success or failure results of charging a mobile body of the type determined by the type determination information in the charger determined by the charger determination information in a manner that can know the charger used in charging and the type of the mobile body as the charging object based on the information input to the input unit.

[0097] Furthermore, the processor 110 functions as an example of aggregating unit by calculating the reliability, and calculates a reliability whose value becomes larger as the number of times the charger specified by the charger identification information charges the mobile object of the type specified by the type identification information increases.

[0098] In addition, the processor 110 functions as an example of an aggregating unit by calculating at least one of the success probability and the failure probability of charging the mobile body of the type specified by the type identification information in the charger specified by the charger identification information.

[0099] In step ST47, the processor 110 updates the reward table and gives a reward to the user who sent the result information. That is, the processor 110 adds the number of the newly given reward to the number of the reward indicated by the reward information associated with the user ID included in the vehicle type identification information in the result information received in step ST41. In addition, the processor 110 may cancel the processing of steps ST47 and ST48 when the user ID is unknown.

[0100] The number of rewards given can be fixed or can be changed according to conditions. In addition, the number of rewards can also be 0 according to conditions. The processor 110 can also determine the number of rewards based on, for example, the difference between the date and time of the history added in step ST45 and the latest history before the history in the history associated with the vehicle type determined in step ST44 and the charger ID of the charger 400 determined in step ST45. The processor 110 increases the number of rewards, for example, when the difference is greater than a specified value. The processor 110 sets the number of rewards to 0, for example, when the difference is less than a specified value. For example, the larger the difference, the greater the number of rewards the processor 110 increases. In addition, the date and time in the latest history before the history added in step ST45 is an example of the date and time of charging in the latest success or failure result stored in the storage device before the success or failure information is input.

[0101] The processor 110 may deposit the rewards given to each user into the user's account in real time or at a later date. Alternatively, the processor 110 may give the user at least one of legal tender, electronic currency, and points using other methods.

[0102] As described above, the processor 110 functions as an example of a granting unit by performing the process of step ST47 to grant a reward to the source of the information input to the input unit.

[0103] In step ST48, the processor 110 generates a grant notification. The grant notification includes information indicating the number of rewards granted in step ST47. The grant notification is information notifying the number. After generating the grant notification, the processor 110 instructs the communication interface 150 to send the grant notification to the terminal device 200. The communication interface 150 receives the instruction to send and sends the grant notification to the terminal device 200. The sent grant notification is received by the second communication I / F 260 of the terminal device 200. After processing step ST48, the processor 110 returns to step ST41.

[0104] On the other hand, if the Figure 2 If the processor 210 of the terminal device 200 receives a notification of provision during the standby state of steps ST11 to ST14, the processor 210 of the terminal device 200 determines Yes in step ST14 and proceeds to step ST24.

[0105] In step ST24, the processor 210 generates an image corresponding to the given screen. Then, the processor 210 instructs the output device 280 to display the generated image. The output device 280 receives the display instruction and displays the given screen. After processing step ST24, the processor 210 returns to step ST11.

[0106] The grant screen is a screen for notifying the operator of the number of rewards included in the grant notification received in step ST 14. As an example, the grant screen includes an image indicating the number.

[0107] The management system 1 can browse the success and failure summary information, etc. Figure 3 and Figure 4 This section explains how to browse success and failure summary information, etc.

[0108] exist Figure 3 In step ST31, the processor 210 of the terminal device 200 generates an image corresponding to the browsing input screen. Then, the processor 210 instructs the output device 280 to display the generated image. The output device 280 receives the display instruction and displays the browsing input screen.

[0109] The browsing input screen is a screen for inputting information required for browsing, such as success and failure summary 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 these information. In addition, the processor 210 can also automatically input information in each input field of the browsing input screen. In addition, as an example, the browsing 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 information input into the browsing input screen.

[0110] In step ST32, the processor 210 determines whether each information input into the browsing input screen is to be sent to the server device 100. For example, when the send button displayed on the browsing input screen is operated, the processor 210 determines that the information is to be sent. If it is not determined that the information is to be sent, the processor 210 determines No in step ST32 and repeats the process of step ST32. On the other hand, if it is determined that the information is to be sent, the processor 210 determines Yes in step ST32 and proceeds to step ST33.

[0111] In step ST33, the processor 210 generates an information request. As an example, the information request includes the vehicle type identification information and the charger identification information input into the browsing input screen. The information request is a request to send the success and failure summary information and reliability and the latest charging history information determined by the vehicle type identification information and the charger identification information. After generating the information request, the processor 210 instructs the second communication I / F 260 to send the information request to the server device 100. The second communication I / F 260 receives the instruction to send and sends the information request to the server device 100. The sent information request is received by the communication interface 150 of the server device 100.

[0112] On the other hand, if the Figure 4 If a status request is received during the standby state of step ST41 and step ST42, the processor 110 of the server device 100 determines Yes in step ST42 and proceeds to step ST47.

[0113] In step ST49 , the processor 110 specifies the vehicle model indicated by the vehicle model specifying information in the information request received in step ST42 , similarly to step ST43 .

[0114] In step ST50 , processor 110 specifies charger 400 indicated by the charger identification information in the information request received in step ST42 , similarly to step ST44 .

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

[0116] In step ST52, the processor 110 generates charging information. The charging information includes the success and failure aggregation information, reliability, and history acquired in step ST51. The charging information is information notifying the success and failure aggregation information, the reliability, and the history. In addition, the history is set to not include the vehicle ID and the user ID. After generating the charging information, the processor 110 instructs the communication interface 150 to send the charging information to the terminal device 200 that is the source of the status request. The communication interface 150 receives the instruction to send and sends the charging information to the terminal device 200. The sent charging information is received by the second communication I / F 260 of the terminal device 200. After processing step ST52, the processor 110 returns to step ST41.

[0117] According to the above, the processor 110 functions as an example of a communication unit by cooperating with the communication interface 150 to perform the processing of step ST42 and send the success and failure summary information, and transmits at least one of the number of successes, the number of failures, the success probability, and the failure probability of charging the mobile body of the type determined by the type determination information in the charger determined by the charger determination information according to the charger determination information and the type determination information received from the terminal device. In addition, the processor 110 functions as an example of a communication unit by cooperating with the communication interface 150 to perform the processing of step ST42 and send the history, and transmits the latest success and failure results of charging the mobile body of the type determined by the type determination information in the charger determined by the charger determination information according to the charger determination information and the type determination information received from the terminal device.

[0118] On the other hand, Figure 3 In step ST34, 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.

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

[0120] The charging screen is a screen for notifying the operator of the contents of the success / failure summary information, the reliability, and the history contained in the charging information received in step ST33. As an example, the charging screen includes an image showing the success / failure summary information, the reliability, and the history.

[0121] According to the management system 1 of the embodiment, the server device 100 receives input of success or failure information, charger identification information, and vehicle type identification information. In addition, the server device 100 of the embodiment stores charging success or failure information in a manner that allows the charger 400 used in charging and the vehicle type of the vehicle 300 to be charged to be known. As a result, the server device 100 of the embodiment can grasp the success or failure status of charging for each vehicle type of each charger 400. In addition, by using the server device 100 of the embodiment, the user can understand the success or failure status of charging for each vehicle type of each charger 400.

[0122] In addition, 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. And, based on this reception, the server device 100 of the embodiment sends the success and failure summary information of charging the vehicle type identified by the vehicle type identification information in the charger 400 identified by the charger identification information to the terminal device 400. Thus, the user can understand the success and failure summary information of charging a specific vehicle type by a specific charger 400.

[0123] In addition, 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. And, based on this reception, the server device 100 of the embodiment sends the latest success or failure result of charging the vehicle type identified by the vehicle type identification information in the charger 400 identified by the charger identification information to the terminal device 400. Thus, the user can know the latest success or failure result of charging the specific vehicle type in the specific charger 400.

[0124] Furthermore, according to the management system 1 of the embodiment, the server device 100 obtains a reliability that increases as the number of trials increases. This allows the user to understand how reliable the success / failure summary information is.

[0125] Furthermore, according to the management system 1 of the embodiment, the server device 100 calculates at least one of the success probability and the failure probability. Thus, the user can understand the probability that the charger 400 can charge.

[0126] Furthermore, according to the management system 1 of the embodiment, the server device 100 provides a reward to the user who is the source of the result information transmission. The reward is a motivation for the user to transmit the result information.

[0127] Furthermore, according to management system 1 of the embodiment, server device 100 determines the amount of reward based on the date and time of the history. If the amount of reward increases when the date and time of the latest history is old, the user can be allowed to use charger 400 with fewer records in the history.

[0128] The above-mentioned embodiment may be modified as follows.

[0129] In the above embodiment, the server device 100 sends the latest charging history to the terminal device 200. However, the server device 100 may also send N charging histories counted from the latest one to the terminal device 200. N is an integer greater than 1. The value of N is determined, for example, based on the operation of the operator. Alternatively, the value of N may also be determined by the administrator or designer of the management system 1.

[0130] The terminal device 200 may not be able to automatically transmit the charging result. Alternatively, the terminal device 200 may only be able to automatically transmit the charging result.

[0131] In the above-mentioned embodiment, the case of charging the vehicle 300 is described as an example. However, the management system of the embodiment can also be applied to the case of charging a mobile body other than the vehicle 300. Examples of mobile bodies other than the vehicle 300 include bicycles, airplanes, and ships. In mobile bodies other than the vehicle 300, the management system of the embodiment can also use aircraft models or ship models instead of vehicle models. Aircraft models or ship models are examples of types of mobile bodies. Based on the above, the server device of the embodiment can grasp the charging status of the charger for each type of mobile body.

[0132] The moving object of the embodiment may be unmanned.

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

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

[0135] Each device 100 in the embodiment may be composed of a plurality of devices.

[0136] The processor 110 and the processor 210 may implement part or all of the processing implemented by the program in the above-mentioned embodiments by means of a hardware structure of a circuit.

[0137] The program for implementing the processing of the implementation mode is transferred in a state of being stored in a non-temporary computer-readable storage medium in the device, for example. However, the device may also be transferred without storing the program. Then, the program may also be transferred separately and written to the device. The transfer of the program in this case may be achieved, for example, by recording it in a removable non-temporary computer-readable storage medium, or by downloading it via a network such as the Internet or a LAN.

[0138] The embodiments of the present invention have been described above, but these are shown as examples and are not intended to limit the scope of the present invention. The embodiments of the present invention can be implemented in various forms without departing from the gist of the present invention.

[0139] Reference numerals

[0140] 1. Management System

[0141] 100 server devices

[0142] 110,210 processors

[0143] 120,220 ROM

[0144] 130,230 RAM

[0145] 140,240 auxiliary storage devices

[0146] 141 Charger DB

[0147] 142 UserDB

[0148] 150 communication interface

[0149] 160,290 bus

[0150] 200 terminal devices

[0151] 250 First Communication I / F

[0152] 260 Second communication I / F

[0153] 270 Input devices

[0154] 280 output devices

[0155] 300 vehicles

[0156] 310 battery

[0157] 400 charger

Claims

1. A management device comprising: an input unit that receives input of success or failure information indicating whether charging of the mobile object in the charger is successful or failed, charger identification information identifying the charger, and type identification information identifying the type of the mobile object; and, The storage unit stores in a storage device the success or failure results of charging the mobile body of the type determined by the type determination information in the charger determined by the charger determination information in a manner that can know the charger used in charging and the type of the mobile body as the charging object, based on the information input to the input unit.

2. The management device according to claim 1 further comprises a communication unit, which sends at least any one of the number of successes, the number of failures, the success probability and the failure probability of charging the mobile body of the type determined by the type determination information in the charger determined by the charger determination information based on the charger determination information and the type determination information received from the terminal device.

3. The management device according to claim 1 further comprises a communication unit, which sends the latest success or failure result of charging the mobile body of the type determined by the type determination information in the charger determined by the charger determination information based on the charger determination information and the type determination information received from the terminal device.

4. The management device according to claim 1, further comprising a counting unit that calculates a reliability whose value becomes larger as the number of times the mobile object of the type specified by the type specifying information is charged by the charger specified by the charger specifying information increases. 5 . The management device according to claim 1 , further comprising a calculating unit that calculates at least one of a success probability and a failure probability of charging the mobile object of the type specified by the type specifying information in the charger specified by the charger specifying information. 6 . The management device according to claim 1 , further comprising a granting unit configured to grant an incentive to a source of the information input to the input unit.

7. The management device according to claim 6, wherein: The granting unit determines the amount of the reward to be granted based on the date and time of charging performed in the latest success or failure result stored in the storage device before the success or failure information is input.

8. A management system, comprising a terminal device and a management device, The terminal device includes a transmitting unit configured to transmit charger identification information for identifying a charger and type identification information for identifying a type of a mobile object. The aforementioned management device has: an input unit that receives input of success or failure information indicating whether charging of the mobile object in the charger succeeded or failed, the charger identification information, and the type identification information; and, The storage unit stores in a storage device the success or failure results of charging the mobile body of the type determined by the type determination information in the charger determined by the charger determination information in a manner that can know the charger used in charging and the type of the mobile body as the charging object, based on the information input to the input unit.

9. A terminal device, which together with a management device constitutes a management system, the management device comprising: an input unit, which receives input of success or failure information indicating whether charging of a mobile body in a charger is successful or failed, charger determination information that determines the charger, and type determination information that determines the type of the mobile body; and a storage unit, which stores in the storage device the success or failure result of charging the mobile body of the type determined by the type determination information in the charger determined by the charger determination information based on the information input to the input unit, in a manner that allows the charger used in charging and the type of the mobile body as the charging object to be known; and, The terminal device includes a transmitting unit that transmits the charger identification information and the type identification information.

10. A program that causes a processor included in a management device including a communication device to function as the following means: an input control unit that controls the communication device to receive input of success or failure information indicating whether charging of the mobile object in the charger is successful or failed, charger identification information that identifies the charger, and type identification information that identifies the type of the mobile object; and, The storage unit stores in the storage device the success or failure results of charging the mobile body of the type determined by the type determination information in the charger determined by the charger determination information in a manner that can know the charger used in charging and the type of the mobile body as the charging object, based on the information input into the communication device.

11. A program for causing a processor of a terminal device to function as a transmission control unit, the terminal device comprising a communication device and constituting a management system together with a management device, the management device comprising: An input unit receives input of success or failure information indicating whether charging of the mobile object in the charger is successful or failed, charger determination information that determines the charger, and type determination information that determines the type of the mobile object; and a storage unit stores, based on the information input to the input unit, a success or failure result of charging the mobile object of the type determined by the type determination information in the charger determined by the charger determination information in a storage device in such a manner that the charger used in charging and the type of the mobile object as a charging target can be known; and, The transmission control unit controls the communication device to transmit the charger identification information and the type identification information.

Images