TWI774951B - Management device, management method and program for battery sharing service - Google Patents

Abstract

A management device for a battery sharing service, comprising: a first acquiring unit for acquiring in association with charging data collected by the charging device when the battery is charged by the charging device, and identification information for identifying the battery ; and the 2nd acquisition part is to obtain: the vehicle data collected by the vehicle when the vehicle uses the battery, and the identification information for identifying the battery; and the related means are based on: and the charging data The identification information obtained in association with the identification information obtained in association with the vehicle data associates the charging data and the vehicle data with each other.

Description

Management device, management method and program for battery sharing service

The present invention relates to a management device, a management method and a program for a battery sharing service.

With the spread of electric vehicles and hybrid (hybrid) vehicles, a service that can exchange batteries mounted on the vehicle is provided. Patent Document 1 describes a system that obtains battery performance and determines whether or not to recycle the battery. [Prior Art Literature] [Patent Literature]

[Patent Document 1] Japanese Patent Laid-Open No. 2010-212048

[Problems to be Solved by the Invention]

In a battery sharing service in which batteries of the same type are shared by a plurality of vehicles, one battery can be used by a plurality of vehicles and can be charged by a plurality of charging devices. In order to accurately grasp the state of the battery, it is necessary to grasp how each battery is used in the vehicle and how it is charged in the charging device. An object of the present invention is to provide a technique useful for accurately grasping the history of a battery. [means to solve the problem]

According to some aspects of the present invention, it is possible to provide a management device, which is a management device for a battery sharing service, including: a first acquisition means for collecting data collected by the charging device when the battery is charged by the charging device. The charging data and the identification information for identifying the battery are acquired in association; and the second acquisition means is to obtain the vehicle data collected by the vehicle when the vehicle uses the battery, and the identification information for identifying the battery, Obtained in a related manner; and a related method is to associate the charging data and the vehicle data with each other based on the identification information obtained in connection with the charging data and the identification information obtained in connection with the vehicle data related between. [Effect of invention]

By the above-mentioned means, a technique useful for accurately grasping the history of the battery can be provided.

Other features and advantages of the present invention will become apparent from the following description with reference to the accompanying drawings. In the attached drawings, the same reference numerals are attached to the same or the same configuration.

Hereinafter, embodiments of the present invention will be described with reference to the attached drawings. In the various embodiments, the same reference numerals are attached to the same elements, and overlapping descriptions are omitted. In addition, the respective embodiments can be appropriately changed and combined. In the following examples, a shared service in which batteries are shared by a plurality of vehicles will be described.

A configuration example of a battery management system 100 for providing a shared service according to some embodiments will be described with reference to FIG. 1 . The battery management system 100 includes a management device 110 , a vehicle 120 , a charging device 130 , and a battery 140 . In the first figure, one vehicle 120 , one charging device 130 and one battery 140 are displayed each. Typically, a plurality of vehicles 120 may utilize the shared service at the same time. In addition, a plurality of charging devices 130 and a plurality of batteries 140 are used in the sharing service.

The user of the shared service borrows the battery 140 from the provider of the shared service and installs the battery 140 in the vehicle 120 of the user. Vehicles to be served are hybrid (hybrid) vehicles and electric vehicles using the battery 140 as a power source. The vehicle 120 may be a two-wheeled vehicle, a four-wheeled vehicle, or other vehicles. The vehicle 120 is shown as a two-wheeled vehicle in the figure.

The user charges the battery 140 using the charging device 130 provided by the sharing service when the remaining amount of the battery 140 is reduced. The charging device 130 is installed at a charging station, for example. The user waits for the charging of the used battery 140 to be completed, and the battery 140 may be re-installed in the vehicle 120, or another battery 140 that has been charged may be re-installed. In the latter case, the battery 140 being charged may be used in the vehicle 120 of another user later.

The management device 110 performs an operation for providing a battery sharing service (hereinafter, simply referred to as a sharing service). For example, the management device 110 manages information about batteries. Details of the operation of the management device 110 will be described later. The management device 110 and the vehicle 120 can communicate with each other through the network 150 . Moreover, the management device 110 and the charging device 130 can communicate with each other through the network 150 . The network 150 may be a public network such as the Internet, or may be a private network.

An example of a hardware configuration of each device included in the battery management system 100 will be described with reference to FIG. 2 . The management device 110 includes a processing device 111 , a memory device 112 , an input device 113 , an output device 114 , and a communication device 115 . The processing device 111 is a device that executes the processing performed by the management device 110, and is constituted by a processor such as a CPU, for example. The storage device 112 is a device for storing data for processing in the management device 110, and includes, for example, a main storage device composed of memories such as RAM and ROM, and an auxiliary device composed of a hard disk (HD) or the like. memory device.

The input device 113 is a device for receiving input from a user of the management device 110 (eg, an administrator of the battery management system 100 ), and is constituted by, for example, a keyboard, a mouse, and the like. The output device 114 is a device for presenting information to the user of the management device 110, and is composed of, for example, a liquid crystal display, a speaker, and the like. The communication device 115 is a device for connecting the management device 110 and the network 150, and is composed of a network card or the like in the case of wired communication, and composed of an antenna and a signal processing circuit in the case of wireless communication.

The vehicle 120 includes a processing device 121 , a memory device 122 , an input device 123 , an output device 124 , a communication device 125 , an authentication device 126 , a battery I/F (interface) 127 , and a travel monitoring unit 128 . In FIG. 2, elements that can be used in the shared service are shown, and other elements such as elements related to the running of the vehicle 120 are omitted. The processing device 121 is a device for executing the processing performed by the vehicle 120 , and is constituted by a processor such as a CPU, for example. The storage device 122 is a device for storing data for processing by the vehicle 120, and is constituted by, for example, memories such as RAM and ROM.

The input device 123 is a device for receiving input from the occupant of the vehicle 120 (also a user of the shared service), and is constituted by, for example, a touch panel, buttons, and the like. The output device 124 is a device for presenting information to the occupant of the vehicle 120, and is constituted by, for example, a liquid crystal display, a speaker, and the like. The input device 123 and the output device 124 may be constituted by an integrated device such as a touch panel.

The communication device 125 is a device for connecting the vehicle 120 and the network 150, and is composed of an antenna and a signal processing circuit. The communication device 125 may communicate with the network 150 through, for example, TCU (Telematics Communication Unit) communication. Alternatively or further, the communication device 125 is connected to the charging device 130 or other communication devices in the charging station by using short-range wireless communication such as Wi-FI and Bluetooth, and communicates with the charging device 130 or other communication devices through the charging device 130 or other communication devices. Network 150 communication is also possible.

The authentication device 126 is a device for authenticating the battery 140 . Specifically, the authentication device 126 can determine whether the battery 140 is a battery usable by the sharing service. The vehicle 120 may receive power from the battery 140 only when the authentication result is positive. The authentication device 126 may be used to allow the vehicle 120 to receive authentication from another device. For example, the authentication device 126 has, for example, identification information uniquely assigned to itself, and information used for authentication such as a password or a secret key. Hereinafter, the information used for authentication is referred to as authentication information. The authentication information is stored in the authentication device 126, and also includes information not provided to other devices (for example, a secret key), and information (for example, a hash value) generated from the stored information. When one authentication device 126 is mounted on one vehicle 120 , the identification information of the authentication device 126 is to uniquely identify the vehicle 120 .

The battery I/F 127 is an interface for exchanging data and power with the battery 140 . The authentication device 126 reads out the authentication information from the battery 140 through the battery I/F 127 . In addition, the drive device (not shown) of the vehicle 120 draws electric power from the battery 140 through the battery I/F 127 .

The traveling monitoring unit 128 collects vehicle data about the vehicle when the vehicle 120 uses the battery 140 based on information from various sensors mounted on the vehicle 120 . The vehicle data includes, for example, a history of speed changes, a history of voltage changes of the battery 140 , static information about the vehicle 120 (vehicle type, etc.), and dynamic information about the vehicle 120 (travel distance, etc.).

The charging device 130 includes a processing device 131 , a memory device 132 , an input device 133 , an output device 134 , a communication device 135 , an authentication device 136 , a battery I/F 137 , and a power supply monitoring unit 138 . The processing device 131 is a device that executes the processing performed by the charging device 130 , and is constituted by a processor such as a CPU, for example. The storage device 132 is a device for storing data for processing by the charging device 130, and is constituted by, for example, memories such as RAM and ROM. The input device 133 is a device for receiving input from the user of the charging device 130 (eg, the occupant of the vehicle 120 and the store clerk of the charging station), and is composed of, for example, a touch panel and buttons. The output device 134 is a device for presenting information to the user of the charging device 130, and is composed of, for example, a liquid crystal display, a speaker, and the like. The input device 133 and the output device 134 may be constituted by an integrated device such as a touch panel. The communication device 135 is a device for connecting the charging device 130 to the network 150, and is composed of an antenna, a signal processing circuit, and the like.

The authentication device 136 is a device for authenticating the battery 140 . Specifically, the authentication device 136 can determine whether the battery 140 is a battery usable by the sharing service. The charging device 130 may supply power to the battery 140 only when the authentication result is positive. The authentication device 136 may be used to allow the charging device 130 to receive authentication from another device. For example, the authentication device 136 has, for example, identification information uniquely assigned to itself, and information used for authentication such as a password or a secret key (the above-mentioned authentication information). When one authentication device 136 is attached to one charging device 130 , the identification information of the authentication device 136 is to uniquely identify the charging device 130 .

The battery I/F 137 is an interface for exchanging data and power with the battery 140 . The authentication device 136 reads out the authentication information from the battery 140 through the battery I/F 137 . In addition, the charging device 130 supplies power to the battery 140 through the battery I/F 127 .

The power supply monitoring unit 138 collects charging data related to charging when the battery 140 is charged by the charging device 130 . The charging data includes, for example, a history of voltage changes of the battery 140 and static information (model number, etc.) about the charging device 130 .

An example of the hardware configuration of the battery 140 will be described with reference to FIG. 3 . The battery 140 includes an outer case 301 , a battery unit 302 , an authentication unit 303 , and a control unit 308 . The battery unit 302 , the authentication unit 303 and the control unit 308 are stored in the outer case 301 . The outer case 301 includes a connector 305 for connecting to an external device and a connector 306 for connecting to the battery unit 302 . The battery unit 302 has a connector 307 for connecting with the outer case 301 . The connector 305 and the connector 306 are connected to each other through the internal bus bar 304 . The authentication unit 303 and the control unit 308 are also connected to the internal bus bar 304 .

The authentication unit 303 is a device for authenticating an external device connected to the battery 140 . Specifically, the authentication unit 303 can determine whether the vehicle 120 connected to the battery 140 or the charging device 130 can use the shared service. The control unit 308 performs the overall operation of the battery 140 . The battery cell 302 is the basic configuration of a battery including electrodes and an electrolyte.

Referring to FIG. 4 , an example of the operation of the vehicle 120 in the shared service will be described. This operation is performed by the processing device 121 reading out the program stored in the memory device 122 and executing the commands contained therein. Instead of this, at least a part of the following operations may be implemented by a dedicated circuit such as an ASIC (Integrated Circuit for Specific Purposes). This operation is started when the battery 140 is mounted on the vehicle 120 . In the vehicle 120, for example, the installation can be detected by measuring the resistance value between the terminals of the battery I/F 127.

In step S401, the vehicle 120 performs the authentication of the mounted battery 140. This authentication can be done by any means. For example, a one-time password can also be used, and a challenge response method can also be used. Information used for the authentication of the battery 140 (for example, the public key of the authentication unit 303 of the battery 140 , etc.) is stored in the authentication device 126 of the vehicle 120 . The vehicle 120 may update the information for the authentication battery 140 in step S401 or before this process.

In step S402, the vehicle 120 determines whether the authentication has succeeded. In the case of success (“YES” in step S402 ) the vehicle 120 proceeds to S403 , and in the case of failure (“NO” in step S402 ) the vehicle 120 ends the process. When the authentication fails, the vehicle 120 may notify the occupant of the authentication failure through the output device 124 . Thereby, the occupant can know that the battery mounted on the vehicle 120 is not a battery that is a target of the shared service.

In step S403 , the vehicle 120 runs using at least the electric power from the battery 140 . During this running, the running monitoring unit 128 of the vehicle 120 collects the vehicle data of the vehicle 120 .

In step S404, the vehicle 120 transmits the vehicle data to the management device 110 in association with the identification information of the battery 140 being mounted. The transmission of the vehicle data may be performed in real time at the same time as the acquisition of the vehicle data. Alternatively, the vehicle 120 stores the vehicle data in the memory device 122 in advance, and transmits the vehicle data at a predetermined time point (for example, when the battery 140 is exchanged, when the short-distance wireless communication is connected, etc.). Can. The vehicle data may be sent to the management device 110 through a communication device (eg, the charging device 130 and the access point) installed at the charging station. In the vehicle 120, the identification information of the battery 140 (identification information uniquely assigned to the battery) may be read out at the time of authentication of the battery 140, or may be read at another time point.

Referring to FIG. 5 , an operation example of the charging device 130 in the shared service will be described. This operation is performed by the processing device 131 reading out the program stored in the memory device 132 and executing the commands contained therein. Instead of this, at least a part of the following operations may be implemented by a dedicated circuit such as an ASIC (Integrated Circuit for Specific Purposes). This operation is started when the battery 140 is attached to the charging device 130 . The charging device 130 can detect the mounting by, for example, measuring the resistance value between the terminals of the battery I/F 137 .

In step S501, the charging device 130 authenticates the installed battery 140. This authentication can be done by any means. For example, a one-time password can also be used, and a challenge response method can also be used. The information used for the authentication of the battery 140 is stored in the authentication device 136 of the charging device 130 . The charging device 130 may update the information for authenticating the battery 140 in step S501 or before this process.

In step S502, the charging device 130 determines whether the authentication has succeeded. In the case of success (“YES” in step S502 ), the charging device 130 proceeds to S503 , and in the case of failure (“NO” in step S502 ), the charging device 130 ends the process. When the authentication fails, the charging device 130 may notify the user (the occupant and the clerk of the charging station) of the authentication failure through the output device 134 . Thereby, the user can know that the battery attached to the charging device 130 does not belong to the battery of the object of the shared service.

In step S503 , the charging device 130 charges the battery 140 by supplying power to the battery 140 . During the charging, the power supply monitoring unit 138 of the charging device 130 collects the charging data of the charging device 130 .

In step S504, the charging device 130 transmits the charging data to the management device 110 in association with the identification information of the battery 140 being mounted. The sending of the charging data may be performed in real time at the same time as the acquisition. Alternatively, the charging device 130 may transmit the charging data after the charging is completed. The charging device 130 may read out the identification information of the battery 140 (identification information uniquely assigned to the battery) when the battery 140 is authenticated, or may be read out at other time points.

An example of the operation of the battery 140 in the shared service will be described with reference to FIG. 6 . This operation is performed by the control unit 308 . This operation is started when the battery 140 is installed in an external device such as the vehicle 120 or the charging device 130 . The installation of the battery 140 can be detected, for example, by measuring the resistance value between the terminals of the connector 305 .

In step S601, the battery 140 performs authentication with an external device connected to itself. This authentication can be done by any means. For example, a one-time password can also be used, and a challenge response method can also be used. The information necessary for the authentication of the battery 140 is stored in the authentication device 136 of the battery 140 . The battery 140 may update the information for authenticating the external device in step S601 or before this process. The additional information may be performed through the vehicle 120 or the charging device 130 , or may be performed using a communication device (not shown) mounted on the battery 140 .

In step S602, the battery 140 determines whether the authentication has succeeded. In the case of success (“YES” in step S602 ), the battery 140 proceeds to S603 , and in the case of failure (“NO” in step S602 ), the battery 140 ends the process. When the authentication fails, the battery 140 may notify the external device of the authentication failure. In step S603 , the battery 140 is powered to the vehicle 120 or is charged from the charging device 130 .

An example of the operation of the management device 110 in the shared service will be described with reference to FIG. 7 . This operation is performed by the processing device 111 reading out the program stored in the memory device 112 and executing the commands contained therein. Instead of this, at least a part of the following operations may be implemented by a dedicated circuit such as an ASIC (Integrated Circuit for Specific Purposes). This operation is repeated while the management device 110 is operating.

In step S701, the management device 110 obtains the vehicle data from the vehicle 120 and the identification information of the battery 140 in association with each other. For example, the vehicle data and the identification information may be related by being transmitted at the same time point, or the correlation may be expressed explicitly. In step S702, the management device 110 stores the vehicle data in the memory device 112 in association with the identified battery. Specifically, the management device 110 updates the battery management data (described later) stored in the storage device 112 .

In step S703, the management device 110 obtains the charging data from the charging device 130 and the identification information of the battery 140 in association with each other. For example, the charging data and the identification information may be associated by being sent at the same time point, or the association may be explicitly stated. In step S704, the management device 110 stores charging data (described later) in the memory device 112 in association with the identified battery.

The above-mentioned steps S701 and S702, and steps S703 and S704 may be executed in reverse, or may be executed in parallel.

An example of the battery management data 800 will be described with reference to FIG. 8 . The battery management data 800 is stored in the memory device 112 . The management device 110 is related to the battery using the battery management data 800 . The battery management data 800 is recorded in each battery 140 . Field 801 is to display the identification information of the battery. Field 802 shows the current position of the battery. Column 803 shows the manufacturer of the battery. Field 804 shows the date of manufacture of the battery. Column 805 is to display the acquired walking data. Column 806 displays the acquired charging data. Field 807 displays information about the user in battery utilization (eg, uniquely assigned identification information for the user). In step S702, the management device 110 defines the record of the object of the battery management data 800 by comparing the acquired identification information of the battery with the field 801, and updates the travel data in the field 805 of the record. In step S704, the management device 110 defines the record of the object of the battery management data 800 by comparing the acquired identification information of the battery with the field 801, and updates the charging data in the field 806 of the record. In this way, the management device 110 stores the charging data and the vehicle data in the battery management data 800 in association with each other based on the identification information obtained in association with the charging data and the identification information obtained in association with the vehicle data. record of.

In the above example, as shown in FIG. 9A , the authentication device 126 of the vehicle 120 and the authentication device 136 of the charging device 130 perform authentication of the battery 140 respectively, and the vehicle data or the charging data are managed according to the authentication result. Device 110 sends a message. Alternatively, as shown in FIG. 9B , the management device 110 may include an authentication device 901 , and the authentication device 901 may authenticate the battery 140 through the vehicle 120 . Specifically, the authentication device 901 obtains the authentication information read from the battery 140 through the vehicle 120 , and uses the information to authenticate the battery 140 . Depending on the authentication method, the authentication device 901 may send the authentication information (eg, random numbers in the challenge response method) to the battery 140 through the vehicle 120 .

Similarly, as shown in FIG. 9C , instead of authenticating the battery 140 by the authentication device 136 of the charging device 130 , the authentication device 901 of the management device 110 may authenticate the battery 140 through the charging device 130 . Further, the authentication device 901 may perform both authentication through the battery 140 of the vehicle 120 and authentication through the battery 140 of the charging device 130 .

In the above example, the management device 110 correlates the vehicle data and the charging data using the identification information uniquely allocated to the battery 140 . Alternatively, the management device 110 may perform the correlation between the vehicle data and the charging data using the identification information of the user who is uniquely allocated to the battery sharing service. For example, the user is the authentication device 126 that writes the identification information (user identification information) assigned to itself in the vehicle 120 . When the vehicle 120 is equipped with the battery 140 , the user identification information is written into the authentication unit 303 of the battery 140 . The charging device 130 reads out the user identification information when the battery 140 is installed.

In step S404 , the vehicle 120 transmits the traveling data to the management device 110 in association with the user identification information written in the battery 140 . In step S504 , the charging device 130 sends the charging data to the management device 110 in association with the user identification information read from the battery 140 . The management device 110 correlates the vehicle data and the charging data according to the user identification information of the two. Since the user identification information of each user is overwritten on the battery 140 every time the battery 140 is mounted on a different vehicle 120 , the vehicle data and charging data of the same type of battery may be correlated in this way.

<Organization of Examples> <Configuration 1> A management device (110) for a battery sharing service, comprising: a first acquisition means for obtaining charging data collected by the charging device when the charging device (130) charges the battery, and identification information for identifying the battery, and the second obtaining means is to obtain: the vehicle data collected by the vehicle when the vehicle (120) uses the battery, and the identification information for identifying the battery, and the related means, It is based on the identification information obtained in association with the charging data and the identification information obtained in association with the vehicle data to associate the charging data and the vehicle data with each other. According to this configuration, the history of the charging device and each battery in the vehicle can be accurately grasped. <Configuration 2> According to the management device of configuration 1, wherein the battery is provided with an outer case (301) and a battery unit (302), the outer case and the battery unit respectively have identification information, and the associated means is based on the outer case and the battery Each identification information of the unit associates the aforementioned charging data and the aforementioned vehicle data with each other. According to this configuration, it is possible to detect that the battery cell or the outer case of the battery has been replaced. <Configuration 3> The management device of the configuration 1 or 2 further includes authentication means for authenticating the battery using the information read from the battery through the charging device. According to this configuration, authentication can be performed at the management device. <Configuration 4> The management device according to any one of the configurations 1 to 3 further includes authentication means for authenticating the battery using information read from the battery through the vehicle. According to this configuration, authentication can be performed at the management device. <Configuration 5> According to the management device of the configuration 1 or 2, the first acquisition means is that the charging device acquires the charging data when the authentication of the battery is successful. According to this configuration, authentication can be performed at the charging device. <Configuration 6> The management device according to any one of the configurations 1 to 3, wherein the second acquisition means is to acquire the vehicle data when the vehicle has successfully authenticated the battery. According to this configuration, the vehicle can be authenticated. <Constitution 7> The management device according to any one of configurations 1 to 5, wherein the vehicle can communicate with a communication device (130) installed at a charging station, and the second obtaining means is to obtain the vehicle data from the vehicle through the communication device . According to this structure, the communication cost of a vehicle can be reduced. <Configuration 8> The management apparatus according to any one of the configurations 1 to 7, wherein the identification information of the battery includes identification information uniquely assigned to the battery. According to this configuration, the battery can be managed by the identification information assigned to the battery. <Configuration 9> The management apparatus according to any one of configurations 1 to 7, wherein the identification information of the battery includes identification information of a user of the sharing service that is uniquely assigned to the battery. According to this configuration, the battery can be managed by the identification information assigned to the user. <Constitution 10> The management method is a management method of a battery sharing service, and includes a process of correlatingly acquiring charging data collected by a charging device (130) by the charging device and identification information for identifying the battery when the charging device (130) charges the battery (S703); and the process of obtaining: the vehicle data collected by the vehicle when the vehicle (120) uses the battery, and the identification information for identifying the battery, in a related manner (S701); and the basis: with the aforementioned charging The identification information obtained in association with the data and the identification information obtained in association with the vehicle data are associated with the charging data and the vehicle data (S702, S704). According to this configuration, the history of the charging device and each battery in the vehicle can be accurately grasped. <Constitution 11> The management method of composition 10, wherein the battery is provided with an outer box (301) and a battery unit (302), the outer box and the battery unit respectively have identification information, and in the aforementioned correlation process, according to the aforementioned outer box and the battery unit (302) Each identification information of the battery unit correlates the charging data and the vehicle data with each other. According to this configuration, it is possible to detect that the battery cell or the outer case of the battery has been replaced. <Constitution 12> The management method according to the configuration 10 or 11 further includes a process of authenticating the battery using the information read from the battery through the aforementioned charging device. According to this configuration, authentication can be performed in the management method. <Constitution 13> The management method according to any one of the configurations 10 to 12 further includes a process of authenticating the battery using the information read from the battery through the vehicle. According to this configuration, authentication can be performed in the management method. <Constitution 14> According to the management method of configuration 10 or 11, the charging device acquires the charging data when the authentication of the battery is successful. According to this configuration, authentication can be performed at the charging device. <Constitution 15> The management method according to any one of the configurations 10 to 12, wherein the vehicle acquires the vehicle data when the authentication of the battery is successful. According to this configuration, the vehicle can be authenticated. <Constitution 16> The management method according to any one of 10 to 14, wherein the vehicle can communicate with a communication device (130) installed at the charging station, and the vehicle data is obtained from the vehicle through the communication device. According to this structure, the communication cost of a vehicle can be reduced. <Constitution 17> The management method according to any one of configurations 10 to 16, wherein the identification information of the battery includes the identification information uniquely assigned to the battery. According to this configuration, the battery can be managed by the identification information assigned to the battery. <Constitution 18> The management method according to any one of configurations 10 to 16, wherein the identification information of the battery includes identification information of a user who is uniquely assigned to the sharing service of the battery. According to this configuration, the battery can be managed by the identification information assigned to the user. <Constitution 19> A program that uses a computer as a function of each of the means constituting any one of the management apparatuses in 1 to 9. According to this configuration, the history of the charging device and each battery in the vehicle can be accurately grasped.

The present invention is not limited to the above-described embodiments, and various changes and modifications can be made without departing from the spirit and scope of the present invention. Therefore, in order to announce the scope of the present invention, the following claims are added.

100‧‧‧Battery Management System 110‧‧‧Management device 111‧‧‧Processing device 112‧‧‧Memory Device 113‧‧‧Input device 114‧‧‧Output device 115‧‧‧Communications 120‧‧‧vehicles 121‧‧‧Processing device 122‧‧‧Memory Device 123‧‧‧Input device 124‧‧‧Output device 125‧‧‧Communications 126‧‧‧Authentication device 128‧‧‧Walking Monitoring Department 130‧‧‧Charging device 131‧‧‧Processing device 132‧‧‧Memory Device 133‧‧‧Input device 134‧‧‧Output device 135‧‧‧Communications 136‧‧‧Authentication device 138‧‧‧Power Supply Monitoring Department 140‧‧‧battery 150‧‧‧Internet 301‧‧‧Outer box 302‧‧‧Battery unit 303‧‧‧Certification Department 304‧‧‧Internal busbar 305‧‧‧Connector 306‧‧‧Connector 307‧‧‧Connector 308‧‧‧Control Department 800‧‧‧Battery management information 801‧‧‧Field 802‧‧‧Field 803‧‧‧Field 804‧‧‧Field 805‧‧‧Field 806‧‧‧Field 807‧‧‧Field 901‧‧‧Authentication device

The attached drawings are included in and constitute a part of the specification, show embodiments of the present invention, and are used to explain the principles of the present invention together therewith. [FIG. 1] A diagram illustrating a configuration example of a battery management system according to an embodiment of the present invention. [ FIG. 2 ] A diagram illustrating a configuration example of each device of the battery management system according to the embodiment of the present invention. [FIG. 3] A diagram illustrating a configuration example of a battery according to an embodiment of the present invention. [FIG. 4] A diagram illustrating an example of the operation of the vehicle according to the embodiment of the present invention. [ FIG. 5 ] A diagram illustrating an example of the operation of the charging device according to the embodiment of the present invention. [ Fig. 6 ] A diagram illustrating an example of the operation of the battery according to the embodiment of the present invention. [ Fig. 7 ] A diagram illustrating an example of the operation of the management device according to the embodiment of the present invention. [FIG. 8] A diagram illustrating an example of battery management data according to an embodiment of the present invention. [ Fig. 9A ] A diagram illustrating another configuration example of each device of the battery management system according to the embodiment of the present invention. [ FIG. 9B ] A diagram illustrating another configuration example of each device of the battery management system according to the embodiment of the present invention. [ FIG. 9C ] A diagram illustrating another configuration example of each device of the battery management system according to the embodiment of the present invention.

Claims (19)

A management device for a battery sharing service is characterized by comprising: a first acquisition means for correlating charging data collected by the charging device and identification information for identifying the battery when the charging device charges the battery The data of the connection is obtained from the charging data through the wide area communication network; and the second obtaining means is to use: the vehicle data collected by the vehicle when the battery is used by a vehicle different from the aforementioned charging device, and the identification of the battery. The identification information and related data are obtained from the vehicle through the wide area communication network; and the related means are compared first: the identification information obtained in connection with the charging data, and the data related to the vehicle. The identification information obtained from the ground, and then the charging data and the vehicle data are correlated with each other according to the result of the comparison. According to the management device of the battery sharing service of claim 1, the battery is provided with an outer box and a battery unit, the outer box and the battery unit respectively have identification information, and the related means is based on the outer box and the battery unit. Each identification information of the battery unit correlates the charging data and the vehicle data with each other. The management device for a battery sharing service according to claim 1, further comprising authentication means for authenticating the battery using information read from the battery through the charging device. The management device for a battery sharing service according to claim 1, further comprising authentication means for authenticating the battery using information read from the battery through the vehicle. The management device of the battery sharing service according to claim 1, wherein the first obtaining means is that the charging device obtains the charging data when the authentication of the battery is successful. The battery sharing service management device of claim 1, wherein the second obtaining means is that the vehicle obtains the vehicle data when the battery authentication is successful. The management device for a battery sharing service according to claim 1, wherein the vehicle can communicate with a communication device installed at a charging station, and the second acquisition means is from the vehicle through the communication device Obtain the aforementioned vehicle information. The battery sharing service management device of claim 1, wherein the identification information of the battery includes identification information uniquely allocated to the battery. The battery sharing service management device according to claim 1, wherein the identification information of the battery includes identification information of a user of the battery sharing service that is uniquely assigned to the battery. A management method for a battery sharing service, comprising: charging data collected by a charging device through the charging device when charging a battery, and identification information for identifying the battery, and related data from the charging data through a wide range of The process of obtaining from the domain communication network; and: the vehicle data collected by the vehicle when the battery is used by the vehicle different from the aforementioned charging device, and the identification information used to identify the battery, the related data, from the vehicle through the broadcast The process of obtaining the domain communication network; and first compare: the identification information obtained in connection with the charging data, and the identification information obtained in connection with the vehicle data, and then according to the result of the comparison. The process by which the data and the aforementioned vehicle data are related to each other. According to the management method of the battery sharing service of claim 10 of the scope of application, wherein the battery has an outer case and a battery unit, and the outer case and the battery unit respectively have identification information. The identification information of the box and the battery unit correlates the charging data and the vehicle data with each other. The management method of the battery sharing service of claim 10, further comprising a process of authenticating the battery using the information read from the battery through the charging device. The method for managing a battery sharing service according to claim 10 of the scope of the application, further comprising a process of authenticating the battery using information read from the battery through the vehicle. According to the management method of the battery sharing service of claim 10, the charging device obtains the charging data when the authentication of the battery is successful. For example, the management method of the battery sharing service in the 10th item of the patent scope, In the case of the aforementioned vehicle, the aforementioned vehicle data is obtained when the authentication of the battery is successful. The method for managing a battery sharing service of claim 10, wherein the vehicle can communicate with a communication device installed at a charging station, and the vehicle data is obtained from the vehicle through the communication device. The method for managing a battery sharing service according to claim 10, wherein the identification information of the battery includes the identification information uniquely allocated to the battery. The method for managing a battery sharing service of claim 10, wherein the identification information of the battery includes identification information of a user who is uniquely assigned to the battery sharing service. A program of a battery sharing service uses a computer loaded to execute the program as each means function of the management device according to any one of the claims 1 to 9 of the scope of the patent application.

Images