Battery system

Abstract

A battery system is provided with a battery, a storage unit that stores a first battery identifier that has been bound to personal information in another system and a second battery identifier that is not bound to personal information in the other system, and a control unit that controls the storage unit. The control unit selectively transmits any one of the first battery identifier and the second battery identifier to a predetermined information processing device together with battery information relating to the state of the battery.

Description

Technical Field

[0001] The present disclosure relates to battery systems. Background Art

[0002] A system for managing batteries of electric vehicles has been proposed. As a related invention, for example, Japanese Patent Application Laid-Open No. 2007-141464 discloses a battery information management system that collects and manages characteristics and usage history of on-vehicle batteries. Summary of the invention

[0003] An object of the present disclosure is to appropriately protect privacy in the management of battery information.

[0004] The first scheme of the present disclosure is a battery system comprising: a battery; a storage unit that stores a first battery identifier that has been bound to personal information in other systems and a second battery identifier that has not been bound to personal information in the other systems; and a control unit that selectively sends either the first battery identifier or the second battery identifier together with battery information related to the status of the battery to a specified information processing device.

[0005] In addition, other schemes of the present disclosure are the device included in the above-mentioned system, the information processing method executed by the device, the program for causing a computer to execute the information processing method, or the computer-readable storage medium that non-temporarily stores the program.

[0006] According to the present disclosure, privacy can be appropriately protected in the management of battery information. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Hereinafter, features, advantages, and technical and industrial significance of exemplary embodiments of the present invention will be described with reference to the accompanying drawings, wherein like reference numerals denote like elements, and wherein:

[0008] Figure 1 This is a diagram for explaining the outline of the battery management system in the first embodiment.

[0009] Figure 2 This is a diagram for explaining the configuration of a plurality of devices included in the system.

[0010] Figure 3A This is a diagram for explaining data stored in a plurality of devices included in the system.

[0011] Figure 3B This is a diagram for explaining data stored in a plurality of devices included in the system.

[0012] Figure 3C This is a diagram for explaining data stored in a plurality of devices included in the system.

[0013] Figure 3D This is a diagram for explaining data stored in a plurality of devices included in the system.

[0014] Figure 3E This is a diagram for explaining data stored in a plurality of devices included in the system.

[0015] Figure 4 This is a timing diagram of the process of the first server acquiring information.

[0016] Figure 5 This is a timing diagram of the process of the second server acquiring information.

[0017] Figure 6 This is a flowchart of the processing executed by the ECU of the battery pack. DETAILED DESCRIPTION

[0018] In recent years, the number of vehicles equipped with driving batteries and capable of running on electricity, such as pure electric vehicles (BEVs) and plug-in hybrid electric vehicles (PHEVs), has increased. In addition, a system is known in which automobile manufacturers and the like collect and centrally manage information (battery information) related to the status of batteries mounted on the vehicle.

[0019] In such a system, battery information is managed in a state of being associated with a specific vehicle. In addition, if the vehicle's driving history is managed in the same system, private information such as the driving history can be traced back based on the battery information. Therefore, before collecting battery information, it is generally necessary to obtain consent from the vehicle owner and the like regarding the processing of personal information.

[0020] However, when battery information is collected in a form tied to personal information, the personal information becomes a constraint, and there is a possibility that the battery information cannot be effectively used.

[0021] For example, consider a situation where a battery mounted on a car is removed from the car for the purpose of recycling. In order to evaluate the value of the battery, it is necessary to use the battery information obtained from the battery. However, the identifier (serial number, etc.) of the battery is bound to the personal information of the previous owner in the car manufacturer's system. That is, even after the battery is removed from the vehicle, it can be traced back to the previous owner. From the perspective of personal information protection, this is not preferred.

[0022] The battery system of the present disclosure solves such problems.

[0023] A battery system according to a first aspect of the present disclosure is configured to include a battery, a storage section, and a control section.

[0024] Specifically, the storage unit stores a first battery identifier that has been bound to personal information in another system and a second battery identifier that has not been bound to personal information in the other system. The control unit selectively sends any one of the first battery identifier and the second battery identifier together with battery information related to the state of the battery to a specified information processing device.

[0025] The battery system of the present disclosure stores multiple identifiers as identifiers for identifying batteries. The first battery identifier is an identifier among these identifiers that has been bound to personal information in other systems. For example, the first battery identifier is bound to a specific vehicle or the owner of the vehicle in a battery management device managed by a car manufacturer. In other words, it can be said that the battery information associated with the first battery identifier is information bound to personal information. For example, in the case of sending battery information to such a device, the control unit sends the first battery identifier in combination with the battery information.

[0026] The second battery identifier is an identifier that is not bound to personal information in other systems among the identifiers for identifying the battery. For example, in a device that manages batteries removed from a vehicle, it is not necessary to bind the vehicle to the battery. For example, when sending battery information to such a device, the control unit combines the second battery identifier that is not bound to personal information with the battery information and sends it. Personal information cannot be traced back based on the battery information collected using the second battery identifier.

[0027] The storage unit of the battery system of the present disclosure stores both the first battery identifier and the second battery identifier, and the control unit selectively determines the identifier to be sent according to the object to which the battery information is to be provided. For example, when the battery is mounted on the vehicle, the battery information is sent together with the first battery identifier, and when the battery is removed from the vehicle, the battery information is sent together with the second battery identifier.

[0028] According to this configuration, the information can be appropriately separated into a case where the battery information is processed together with the personal information and a case where the information is not processed together with the personal information.

[0029] As described above, when the battery identifier that has been bound to personal information is combined with the battery information, the personal information can be traced back from the battery identifier even when the personal information is not processed. On the other hand, in the battery system of the present disclosure, such a situation can be prevented.

[0030] It should be noted that the battery information sometimes includes the driving distance information of the vehicle bound to the battery (specifically, the vehicle equipped with the battery or the vehicle that has been equipped with the battery). In such a case, the vehicle that has been equipped with the battery is sometimes screened out by referring to the driving distance value. Therefore, in the case of sending the second battery identifier to the specified information processing device, the control unit may also convert the value represented by the driving distance information included in the battery information into an approximate number. For example, by truncating or rounding the driving distance at a specific digit to make it an approximate number, such a problem can be prevented.

[0031] The specific embodiments of the present disclosure are described below based on the drawings. Unless otherwise specified, the hardware configuration, module configuration, functional configuration, etc. described in each embodiment are not intended to limit the technical scope of the disclosure to only these.

[0032] First embodiment

[0033] Reference Figure 1 An overview of the battery management system of the first embodiment is described. The battery management system of this embodiment is a system that manages information (battery information) about a battery pack 500 designed for a vehicle 300 through a server device. The battery pack 500 is a unit obtained by adding a computer (ECU: Electronic Control Unit) for control to the driving battery of the vehicle. In the description of the embodiment, the battery pack is also referred to as simply a battery. The battery pack can also be removed from the original vehicle and reused for purposes such as household storage batteries.

[0034] The battery management system of this embodiment includes a first server 100 and a second server 200 as server devices. The first server 100 is a server device that collects information related to the vehicle 300 and information related to the battery pack 500 mounted on the vehicle 300 by communicating with the vehicle 300. The first server 100 may also be a management device used by an automobile manufacturer that manufactures the vehicle 300.

[0035] The first server 100 manages the battery information of the battery pack 500 by binding it to the vehicle 300. For example, the first server 100 collects the identifier, location information, speed, driving distance, etc. of the vehicle 300 as information related to the vehicle, and stores the information related to the battery pack 500 in association with these information. In this way, the first server 100 can grasp the latest status of the vehicle 300 and the battery pack 500. It should be noted that the first server 100 can also obtain consent from the owner of the vehicle 300 to collect such information in advance.

[0036] like Figure 1As shown in the above figure, when the battery pack 500 is mounted on the vehicle 300, the first server 100 can collect information about the battery pack 500 via the vehicle 300. The first server 100, for example, stores the identifier of the battery pack 500 (hereinafter referred to as the battery identifier), the identifier of the vehicle 300, and the collected information in association.

[0037] On the other hand, the battery pack 500 can be removed from the vehicle 300 and recycled. For example, the removed battery pack 500 can be assembled in another vehicle to recirculate the battery pack 500, or assembled in a device other than a vehicle (such as a household storage battery) to recirculate the battery pack 500.

[0038] However, in the case where the battery pack 500 is removed from the vehicle 300, it is difficult to use the battery information collected by the first server 100 after the removal. This is because the battery information collected by the first server 100 is bound to the vehicle 300 (and the original owner of the vehicle 300), so it is not appropriate to use such information after the battery is separated from the vehicle. For example, although the first server 100 obtains consent related to information acquisition from the owner of the vehicle 300 in advance, in most cases, consent related to the use of information after the battery is separated from the vehicle has not yet been obtained.

[0039] It can also be considered that after the battery pack 500 is removed from the vehicle 300, the battery pack 500 can be connected to a computer to directly read the battery information. However, as long as the battery identifier stored in the battery pack 500 is bound to the vehicle in any device, there is a risk that an individual can be identified. This is because the identifier of the vehicle 300 is bound to the identifier of the battery pack 500 in the first server 100.

[0040] To solve this problem, it is necessary to collect battery information using a battery identifier that is not tied to a vehicle or an individual.

[0041] Therefore, in the present embodiment, two types of battery identifiers are assigned to the battery pack 500 , and battery information is collected using different battery identifiers before and after the battery pack 500 is removed from the vehicle 300 .

[0042] Figure 1 The lower figure is a diagram for explaining information collection after the battery pack 500 is removed from the vehicle 300. The battery pack 500 removed from the vehicle 300 can communicate with the second server 200 via the communication device 400.

[0043] The second server 200 is a server device that manages only battery information without storing information related to the owner of the vehicle 300. After the battery pack 500 is removed from the vehicle 300, it transmits the battery information to the second server 200 via the communication device 400. At this time, the battery pack 500 transmits the battery information together with the battery identifier that is not bound to the vehicle. Even if the second server 200 uses the acquired information, it cannot bind the battery to an individual.

[0044] In this way, when the battery pack 500 is mounted on the vehicle 300, it outputs a battery identifier (first battery identifier) ​​that is bound to the vehicle. In addition, when the battery pack 500 is removed from the vehicle 300, it outputs a battery identifier (second battery identifier) ​​that is not bound to the vehicle. Thus, after the battery is removed from the vehicle, the battery information can be obtained and used without being restricted by personal information.

[0045] Figure 2 The figure shows in more detail the components of the first server 100, the second server 200, the vehicle 300, the communication device 400, and the battery pack 500 included in the battery management system of the present embodiment.

[0046] The first server 100 is a device operated by the automobile manufacturer that manufactured the vehicle 300. The first server 100 is a device that collects and manages information related to the vehicle 300 (for example, location information, etc.) and information related to the battery pack 500. Information related to the battery pack 500 is, for example, information related to the use of the battery in the market, such as the driving distance of the vehicle, the temperature, current, state of charge (SOC: State Of Charge), and charge amount of the battery, and the deterioration condition of the battery. The information collected by the first server 100 is bound to the information related to the vehicle 300. In addition, this information collected through the market is sometimes bound to the information related to the owner of the vehicle 300 in the first server 100. The first server 100 collects and manages this information based on the consent obtained in advance from the owner of the vehicle 300.

[0047] The second server 200 is a device for obtaining information related to the battery pack 500 removed from the vehicle 300, and is a device operated by an operator that has no direct relationship with the automobile manufacturer. In the second server 200, information related to the vehicle 300 is not managed, and the obtained battery information is not bound to information related to vehicles that have been equipped with the battery pack 500 in the past or the owner of the vehicle. It should be noted that the second server 200 can also be operated by the automobile manufacturer that manufactured the vehicle 300, but in this case, the second server 200 is completely independent of the first server 100 and does not establish contact with information related to the vehicle 300 or the owner of the vehicle 300.

[0048] The vehicle 300 is a car (connected car) equipped with a battery pack 500. The vehicle 300 has a module for wireless communication (wireless communication unit 303), a module for CAN (Controller Area Network) communication (CAN communication unit 304), and an electronic control unit (ECU: Electronic Control Unit) 301. The first server 100 can obtain information from the battery pack 500 via these components. In addition, the ECU 301 of the vehicle 300 has the following function: obtain information related to the vehicle (for example, location information, etc.) and send it to the first server 100 as vehicle information.

[0049] The communication device 400 is a device that relays the communication between the second server 200 and the battery pack 500. The battery pack 500 removed from the vehicle 300 loses the interface for wireless communication and cannot communicate directly with the second server 200. Therefore, in this embodiment, the communication device 400 relays the communication between the second server 200 and the battery pack 500. The communication device 400 has the same interface as the interface of the vehicle 300 (for example, a CAN interface) and can communicate with the battery pack 500 via the interface.

[0050] The battery pack 500 is a unit including a driving battery for driving the vehicle 300. The battery pack 500 may be assembled in the vehicle 300 for use, or may be removed from the vehicle 300 and assembled in another vehicle for use, or assembled in a device other than a vehicle (e.g., a household storage battery).

[0051] The battery pack 500 includes a battery body such as a lithium-ion battery and a computer (ECU 501) for controlling charging and discharging. The ECU 501 included in the battery pack 500 has the following functions: obtaining information related to the state of the battery (battery information, such as values ​​related to the deterioration of the battery) and outputting the information together with its own identifier to the outside.

[0052] Next, the details of each device will be described.

[0053] First, the first server 100 will be described.

[0054] The first server 100 is a computer such as a personal computer, a smartphone, a mobile phone, a tablet computer, or a personal information terminal, and includes a control unit 101 , a storage unit 102 , a wireless communication unit 103 , and an input / output unit 104 .

[0055] The control unit 101 is a computing device that is in charge of the control performed by the first server 100. The control unit 101 can be implemented by a computing device such as a central processing unit (CPU).

[0056] The control unit 101 acquires two types of information, namely, information on the vehicle 300 (vehicle information) and information on the battery pack 500 (battery information), by communicating with the vehicle 300 .

[0057] The control unit 101 is configured to include a data acquisition unit 1011 as a functional module. This functional module can also be realized by executing a stored program by the CPU.

[0058] The data acquisition unit 1011 acquires battery information of any vehicle by communicating with the battery pack 500 (ECU 501) via the vehicle 300. In addition, the data acquisition unit 1011 acquires vehicle information of the vehicle by communicating with the ECU 301 of the vehicle 300. The acquired battery information is stored in the storage unit 102 (described later) as battery data 102A. In addition, the acquired vehicle information is stored in the storage unit 102 as vehicle data 102B.

[0059] The storage unit 102 is configured to include a main storage device and an auxiliary storage device. The main storage device is a memory for expanding the program executed by the control unit 101 and the data used by the control program. The auxiliary storage device is a device that stores the program executed in the control unit 101 and the data used by the control program. The auxiliary storage device may also store a program obtained by packaging the program executed in the control unit 101 as an application program. In addition, an operating system for executing these application programs may also be stored. The program stored in the auxiliary storage device is loaded into the main storage device and executed by the control unit 101, thereby performing the processing described later.

[0060] The main storage device may also include a random access memory (RAM) and a read-only memory (ROM). In addition, the auxiliary storage device may also include an erasable programmable read-only memory (EPROM) and a hard disk drive (HDD). Furthermore, the auxiliary storage device may also include a removable media, i.e., a removable recording medium.

[0061] Furthermore, the storage unit 102 stores battery data 102A, vehicle data 102B, and traceability data 102C.

[0062] The battery data 102A is a collection of battery information acquired from the battery pack 500 mounted on the vehicle 300 . Figure 3A An example of battery data 102A is shown in FIG. As shown in the figure, battery data 102A has fields for a first battery ID, a battery model ID, and a status. The first battery ID field stores an identifier for uniquely identifying a battery pack 500. The first server 100 stores the first battery ID in association with an identifier of the vehicle 300. In other words, the first battery ID is a battery identifier that has been bound to the vehicle 300 (and its owner) in the first server 100.

[0063] The battery model ID field stores an identifier for identifying the model of the battery pack 500 .

[0064] The state field stores a set of data related to the state of the battery. Examples of the data related to the state of the battery include the number of charge and discharge cycles, state of health (SoH), maximum output power, and travel distance.

[0065] SoH is a value indicating the ratio of the current full charge capacity to the initial full charge capacity. For example, a battery with an SoH of 80% can store 80% of the initial full charge capacity. The number of charge and discharge times is the number of times the battery has been charged and discharged since it was new. The number of charge and discharge times is counted as one at the time when 100% of the battery's power has been used. The maximum output power refers to the maximum power that the battery can output. In the case of battery deterioration, the maximum output power is sometimes limited. In other words, there are used batteries whose maximum output power is lower than that of new batteries.

[0066] The travel distance is the value of the odometer of the vehicle 300 equipped with the battery. This information is updated at any time based on the travel distance information (the value of the odometer or the short-distance trip meter, etc.) obtained from the vehicle 300. It should be noted that when the battery is replaced between vehicles, the travel distance may also be the cumulative value of all vehicles.

[0067] It should be noted that any other index may be used as long as it indicates the degree of battery deterioration. For example, an index such as the operating history of a safety device included in the battery or the state of a plurality of single cells may be used.

[0068] The vehicle data 102B is a collection of vehicle information acquired from the vehicle 300 . Figure 3BAn example of vehicle data 102B is shown in FIG. As shown in the figure, vehicle data 102B has fields for vehicle ID, first battery ID, and driving information. The vehicle ID field stores an identifier for uniquely identifying vehicle 300. The first battery ID field stores an identifier for uniquely identifying battery pack 500 mounted on vehicle 300 as described above. The driving information field stores a collection of data related to the driving of vehicle 300. As data related to driving, for example, data such as speed, direction of travel, and location information can be given as examples. Vehicle data 102B is updated based on vehicle information periodically collected from vehicle 300.

[0069] Figure 3C An example of traceability data 102C is shown in FIG. The traceability data 102C is information (traceability-related information) used to calculate greenhouse gas emissions during manufacturing, recycling rates of raw materials, or scores related to due diligence for the target battery pack 500. The first server 100 binds the first battery ID and the traceability-related information for the battery pack 500 under management and stores them, and can provide the first battery ID and the traceability-related information upon request.

[0070] The wireless communication unit 103 is a wireless communication interface for connecting the first server 100 to the network. The wireless communication unit 103 is configured to be able to wirelessly communicate with the vehicle 300 via a communication service such as a wireless LAN (Local Area Network), 3G, 4G, or 5G.

[0071] The input / output unit 104 is a unit that accepts input operations performed by the operator of the device and presents information to the operator. In this embodiment, the input / output unit 104 is composed of a touch panel display. That is, the input / output unit 104 is composed of a liquid crystal display and its control components, a touch panel and its control components.

[0072] Next, the second server 200 will be described.

[0073] The second server 200 is a computer such as a personal computer, a smartphone, a mobile phone, a tablet computer, or a personal information terminal, and includes a control unit 201 , a storage unit 202 , a wireless communication unit 203 , and an input / output unit 204 .

[0074] The second server 200 can be configured as a computer having a processor such as a CPU, a GPU (Graphics Processing Unit), a main storage device such as a RAM, a ROM, an EPROM, a hard disk drive, a removable medium, and other auxiliary storage devices. The configuration of the second server 200 can be the same as that of the first server 100, so the description of the specific hardware configuration is omitted.

[0075] The control unit 201 is a computing device that is in charge of the control performed by the second server 200. The control unit 201 can be realized by a computing device such as a central processing unit (CPU).

[0076] The control unit 201 acquires information (battery information) related to the battery pack 500 via the communication device 400 . The control unit 201 is different from the control unit 101 of the first server 100 in that the control unit 201 communicates with the battery pack 500 via the communication device 400 instead of the vehicle 300 .

[0077] The control unit 201 is configured to have a data acquisition unit 2011 as a functional module. This functional module can also be realized by executing a stored program by the CPU.

[0078] The data acquisition unit 2011 acquires battery information by communicating with the battery pack 500 (ECU 501) via the communication device 400. The acquired battery information is stored as battery data 202A described later.

[0079] The storage unit 202 is configured to include a main storage device and an auxiliary storage device similarly to the storage unit 102. In addition, the storage unit 202 stores battery data 202A.

[0080] The battery data 202A is a collection of battery information acquired from the battery pack 500 . Figure 3D An example of battery data 202A is shown in FIG. The battery data 202A is similar to the battery data 102A stored in the first server 100, but is different in that the battery pack 500 is identified by the second battery ID instead of the first battery ID. The second battery ID is an identifier for uniquely identifying the battery pack 500, just like the first battery ID, but the second battery ID is not associated with the identifier of the vehicle 300 in the first server 100 and the second server 200. In other words, the second battery ID is a battery identifier that cannot be bound to the vehicle 300 (and its owner).

[0081] In this embodiment, the second server 200 manages the battery information using the second battery ID. The second battery ID is not tied to the vehicle 300 and its owner, so the battery information can be used without being restricted by personal information by using the second battery ID.

[0082] The wireless communication unit 203 and the input / output unit 204 are the same as the wireless communication unit 103 and the input / output unit 104 , and thus their description is omitted.

[0083] Next, the vehicle 300 will be described.

[0084] The vehicle 300 is an electric vehicle equipped with a battery pack 500. The vehicle 300 is typically a pure electric vehicle (BEV), but may be any vehicle driven by a driving battery, such as a plug-in hybrid vehicle.

[0085] The vehicle 300 is wirelessly connected to the first server 100. Furthermore, the vehicle 300 is communicatively connected to the battery pack 500 via an in-vehicle network (CAN network).

[0086] The vehicle 300 is configured to include an ECU 301 , a sensor group 302 , a wireless communication unit 303 , and a CAN communication unit 304 .

[0087] The ECU 301 obtains vehicle information and battery information in response to a request from the first server 100, and transmits them to the first server 100. The vehicle information includes, for example, the speed, direction of travel, and location information of the vehicle 300, and can be generated based on sensor data obtained from the sensor group 302 described later. The battery information can be obtained from the ECU 501 included in the battery pack 500.

[0088] The sensor group 302 is a collection of multiple sensors for acquiring vehicle information. For example, the sensor group 302 may also be configured to include a speed sensor, a gyroscope sensor, a compass, a GPS (Global Positioning System) module, and the like.

[0089] The wireless communication unit 303 is a wireless communication interface for connecting the vehicle 300 to a network. The wireless communication unit 303 is configured to be able to communicate with the first server 100 via a wireless LAN, a mobile communication service such as 3G, 4G, or 5G, for example.

[0090] The CAN communication unit 304 is a communication interface with an in-vehicle network provided in the vehicle 300. The CAN communication unit 304 performs communication via a controller area network (CAN) network.

[0091] Next, the communication device 400 will be described.

[0092] The communication device 400 is a device that connects the second server 200 and the battery pack 500. The battery pack 500 has only an interface for communicating with the vehicle 300 via the CAN network, and cannot communicate with the second server 200 in a single state. Therefore, in this embodiment, the second server 200 and the battery pack 500 are connected using the communication device 400 having both a CAN network interface and a wireless communication interface. The communication device 400 has a CAN network interface that is the same as the CAN network interface of the vehicle 300, and can communicate with the battery pack 500 via the CAN network interface.

[0093] The communication device 400 is configured to include a control unit 401 , a wireless communication unit 402 , and a CAN communication unit 403 .

[0094] The control unit 401 acquires the battery information from the ECU 501 included in the battery pack 500 in response to a request from the second server 200 , and transmits the battery information to the second server 200 .

[0095] The wireless communication unit 402 is a network interface for connecting the communication device 400 to a network, similar to the wireless communication unit 203 .

[0096] The CAN communication unit 403 is a communication interface with the in-vehicle network similar to the CAN communication unit 304. The CAN communication unit 403 performs communication via the CAN network.

[0097] Next, the battery pack 500 will be described.

[0098] The battery pack 500 is a unit in which a computer (ECU 501 ), a storage unit 502 , and a CAN communication unit 503 are added to a battery body such as a lithium-ion battery to control the charge and discharge of the battery.

[0099] In addition to controlling the charge and discharge of the battery body, ECU 501 also performs the following processing: periodically generates battery information as information related to its own state, and causes storage unit 502 as a storage device to store the battery information as state data 502A. In addition, ECU 501 performs the following processing: in response to a request from an external device, the stored battery information is sent to the external device.

[0100] Figure 3E This is an example of the state data 502A. The state data 502A is similar to the battery data 102A stored in the first server 100 and the battery data 202A stored in the second server 200. However, the state data 502A is different in that it is associated with both the first battery ID and the second battery ID.

[0101] Furthermore, when sending the battery information, the ECU 501 determines which of the first battery ID and the second battery ID to output according to the destination of the battery information. In the present embodiment, when the battery pack 500 is attached to the vehicle 300 and the battery information is sent to the first server 100 via the vehicle 300, the ECU 501 sends the first battery ID in association with the battery information. When the battery pack 500 is removed from the vehicle 300 and the battery information is sent to the second server 200 via the communication device 400, the ECU 501 sends the second battery ID in association with the battery information. At this time, the ECU 501 performs processing to convert the travel distance included in the battery information into an approximate number.

[0102] The CAN communication unit 503 is an interface for connecting the battery pack 500 to an in-vehicle network.

[0103] It should be noted that Figure 2 The configuration shown is an example, and all or part of the functions shown in the figure may be executed using a specially designed circuit. In addition, the program may be stored or executed by a combination of a main storage device and an auxiliary storage device other than those shown in the figure.

[0104] Next, the processing executed by each device included in the system is described.

[0105] Figure 4 This is a timing chart of a process in which the first server 100 acquires information about the vehicle 300 and the battery pack 500 mounted on the vehicle 300. The illustrated process is executed when the battery pack 500 is mounted on the vehicle 300. This process may be executed periodically or may be executed in response to a predetermined event.

[0106] First, in S11, the first server 100 determines the target vehicle from which information is to be collected. The target vehicle may be determined according to the information collection plan or based on instructions from an operator. For example, the first server 100 obtains the vehicle ID of the determined vehicle and sends an information request to the vehicle 300 having the vehicle ID. The information request is data for requesting the vehicle 300 to send vehicle information and battery information. The information request is received by the vehicle 300 (ECU 301).

[0107] In S12 , the vehicle 300 (ECU 301 ) that has received the information request generates vehicle information. As described above, the vehicle information may also include the vehicle's speed, travel direction, position information, etc. The ECU 301 may acquire this information based on the sensor data acquired from the sensor group 302 .

[0108] Then, the ECU 301 transmits an information request to the battery pack 500 (ECU 501 ). The information request is data for requesting the battery pack 500 to transmit battery information.

[0109] In S13, the battery pack 500 (ECU501) that receives the information request generates battery information. ECU501 can generate battery information based on the status data 502A stored in the storage unit 502, or update the status data 502A with the latest information and generate battery information based on the updated information. The first battery ID is associated with the battery information generated here. The first battery ID and the battery information are sent to the vehicle 300 (ECU301).

[0110] The vehicle 300 (ECU 301 ) adds the vehicle information to the first battery ID and the battery information, and transmits the same to the first server 100 .

[0111] In S14 , the first server 100 updates the battery data 102A and the vehicle data 102B based on the received information.

[0112] Figure 5 4 is a sequence diagram of a process in which the second server 200 acquires information on the battery pack 500 removed from the vehicle 300. The illustrated process is executed when the battery pack 500 is removed from the vehicle 300 and connected to the communication device 400. This process may also be started by an operator's operation.

[0113] First, the operator connects the communication device 400 to the battery pack 500. The communication device 400 and the battery pack 500 may be connected using a CAN interface.

[0114] When the communication device 400 and the battery pack 500 are connected, the communication device 400 (control unit 401) transmits an information request to the battery pack 500 (ECU 501). The information request is data requesting the battery pack 500 to transmit battery information.

[0115] In S21, the battery pack 500 (ECU 501) that has received the information request generates battery information. ECU 501 may generate battery information based on the status data 502A stored in the storage unit 502, or may update the status data 502A with the latest information and generate battery information based on the updated information. The second battery ID is associated with the battery information generated here.

[0116] As described above, the status data includes information related to the driving distance of the vehicle 300 equipped with the battery pack 500. Although the second battery ID is an ID that is not bound to the vehicle, when referring to the driving distance, vehicles that have been equipped with the battery pack 500 are sometimes screened out. Therefore, in S22, ECU501 converts the driving distance contained in the battery information into an approximate number by truncation or rounding it off at any digit. For example, the driving distance is 36421km, and when the thousands are processed to make it an approximate number, the driving distance becomes 36000km. In addition, when the hundreds are processed to make it an approximate number, the driving distance becomes 36400km. As long as the degree of battery degradation can be estimated, the digits of the object that makes the driving distance an approximate number can be set arbitrarily. It should be noted that the above example is displayed in kilometers, but the same is true when the driving distance is displayed in miles.

[0117] When the process of S22 is completed, the second battery ID and the battery information are sent to the communication device 400 (control unit 401 ). The communication device 400 (control unit 401 ) transmits the second battery ID and the battery information to the second server 200 .

[0118] In S23 , the second server 200 updates the battery data 202A based on the received information.

[0119] Next, the contents of the processing performed by the battery pack 500 (ECU 501 ) in the above-mentioned S13 , S21 , and S22 will be described. Figure 6 This is a flowchart of the process executed by the battery pack 500 (ECU 501 ) that has received the information request in S13 , S21 , and S22 .

[0120] First, in S31 , ECU 501 generates battery information. The battery information may be generated based on state data 502A acquired in advance and stored in storage unit 502 .

[0121] Next, in S32, the ECU 501 determines whether the received information request is an information request transmitted from the vehicle 300. If the information request is an information request transmitted from the vehicle 300, the process proceeds to S33. If the information request is not an information request transmitted from the vehicle 300 (that is, if the information request is an information request transmitted from the communication device 400), the process proceeds to S34.

[0122] In S33 , the ECU 501 reads out the first battery ID, and transmits the first battery ID together with the battery information generated in S31 .

[0123] In S34, ECU 501 executes a process of converting the running distance included in the battery information into an approximate number. ECU 501 can convert the running distance included in the battery information into an approximate number by rounding, truncating, or increasing the number at any digit.

[0124] In S35 , the ECU 501 reads out the second battery ID, and transmits the second battery ID together with the battery information generated in S31 .

[0125] As described above, in the battery management system of the present embodiment, the battery pack as the management object stores two types of identifiers, an identifier that is bound to personal information and an identifier that is not bound to personal information. The battery pack determines the identifier to be sent together with the battery information based on the device of the communication destination. As a result, battery information can be appropriately provided to both the device that processes personal information (the first server 100) and the device that does not process personal information (the second server 200). In particular, a battery identifier that is not bound to personal information is provided to a device that does not process personal information, so that personal information cannot be tracked based on the battery information.

[0126] Furthermore, the battery pack of this embodiment converts the travel distance included in the battery information into an approximate number when providing the battery information to the second server 200. This makes it easier to estimate the vehicle that has carried the target battery pack.

[0127] Modifications

[0128] The above-described embodiment is merely an example, and the present disclosure can be implemented with appropriate modifications without departing from the gist of the disclosure.

[0129] For example, the processes and components described in the present disclosure can be implemented in combination as long as no technical contradiction occurs.

[0130] In the description of the embodiment, the battery identifier to be output is determined based on whether the battery pack 500 is mounted on the vehicle 300 (S32), but this determination may also be determined based on the communication destination. For example, the battery identifier to be output may be determined based on whether the device that sent the information request is the first server (i.e., a device associated with the vehicle 300) or the second server (a device not associated with the vehicle 300).

[0131] In the description of the embodiment, the process (S34) of converting the travel distance included in the battery information into an approximate number is performed by the battery pack 500 (ECU 501), but this process may be performed by the communication device 400. The communication device 400 performs this conversion process before transmitting the battery information received from the battery pack 500 to the second server 200.

[0132] Furthermore, a process described as being performed by one device may be shared and executed by a plurality of devices. Alternatively, a process described as being performed by different devices may be performed by one device. In a computer system, the hardware configuration (server configuration) used to implement each function can be flexibly changed.

[0133] The present disclosure can also be implemented in the following manner: a computer program having the functions described in the above embodiments is provided to a computer, and the program is read and executed by one or more processors of the computer. Such a computer program can be provided to the computer via a non-temporary computer-readable storage medium that can be connected to the system bus of the computer, or it can be provided to the computer via a network. Non-temporary computer-readable storage media include, for example, disks (floppy disks (registered trademarks), hard disk drives (HDDs), etc.), optical disks (CD-ROMs (Compact Disc Read Only Memory: read-only optical disks), DVDs (Digital Versatile Discs: digital versatile optical disks) / Blu-ray disks, etc.) and any type of disk, read-only memory (ROM), random access memory (RAM), EPROM, EEPROM (Electrically Erasable Programmable Read Only Memory: electrically erasable programmable read-only memory), magnetic cards, flash memory, optical cards, and any type of medium suitable for storing electronic commands.

Claims

1. A battery system comprising: Battery; A storage unit that stores a first battery identifier that has been bound to personal information in another system and a second battery identifier that has not been bound to personal information in the other system; as well as The control unit selectively transmits any one of the first battery identifier and the second battery identifier together with battery information related to the state of the battery to a predetermined information processing device.

2. The battery system according to claim 1, wherein: When the battery is mounted on the vehicle, the control unit sends the battery information together with the first battery identifier to the specified information processing device. When the battery is removed from the vehicle, the control unit sends the battery information together with the second battery identifier to the specified information processing device.

3. The battery system according to claim 1, wherein: When the specified information processing device is a device associated with the vehicle equipped with the battery system, the control unit sends the battery information together with the first battery identifier to the specified information processing device. When the specified information processing device is a device not associated with the vehicle equipped with the battery system, the control unit sends the battery information together with the second battery identifier to the specified information processing device.

4. The battery system according to claim 1, wherein: The battery information includes driving distance information of a vehicle bound to the battery.

5. The battery system according to claim 4, wherein: When the second battery identifier is to be transmitted to the predetermined information processing device, the control unit converts a value indicated by the travel distance information included in the battery information into an approximate number.

Images