Battery management method and mobile

Abstract

To manage a history of a state of a battery of a battery pack while suppressing increase in a cost of the battery pack.SOLUTION: A battery management method according to one aspect is the battery management method for managing a plurality of battery packs mounted detachably on respective vehicle bodies of a plurality of movable bodies by an external storage device, receives battery identification information for identifying the battery pack from the battery pack mounted on the vehicle body by a processing circuit fixed to the vehicle body, stores the received battery identification information in a vehicle body side memory fixed to the vehicle body by the processing circuit, stores state history information indicating a history of a state of a battery of the battery pack while being mounted on the vehicle body in the vehicle body side memory in association with the battery identification information by the processing circuit, and transmits the state history information stored in the vehicle body side memory to the external storage device from a movable body in association with the battery identification information by the processing circuit.SELECTED DRAWING: Figure 5

Description

Technical Field

[0001] The present disclosure relates to a battery management method, a memory control device, a moving body, and a server.

Background Art

[0002] Patent Document 1 discloses an electric vehicle equipped with a battery pack (battery unit) including a battery. The battery pack has a battery monitoring device for monitoring the state of the battery.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Before the battery reaches the end of its life, the vehicle body on which the battery pack is mounted may change among a plurality of vehicle bodies. In such a case, it is difficult to continuously store the past battery states. For example, in order to store the history of the battery state, a large-capacity memory is required. Providing such a memory in the battery pack would lead to an increase in the cost of the battery pack.

[0005] Therefore, an object of the present disclosure is to provide a battery management method, a memory control device, a moving body, and a server that can manage the history of the state of the battery of the battery pack while suppressing an increase in the cost of the battery pack.

Means for Solving the Problems

[0006] A battery management method according to one aspect of the present disclosure is a battery management method for managing a plurality of battery packs that are detachably mounted on the bodies of a plurality of mobile bodies using an external storage device, wherein a processing circuit fixed to the vehicle body receives battery identification information for identifying the battery packs from the battery packs mounted on the vehicle body, the processing circuit stores the received battery identification information in a vehicle-side memory fixed to the vehicle body, the processing circuit stores state history information indicating the history of the battery state of the battery packs while they are mounted on the vehicle body, linked to the battery identification information in the vehicle-side memory, and the processing circuit transmits the state history information stored in the vehicle-side memory, linked to the battery identification information, from the mobile body to the external storage device.

[0007] A memory control device according to one aspect of the present disclosure is a memory control device in a mobile body equipped with a battery pack, comprising: a memory; a communication interface capable of communicating with an external storage device; and a processing circuit, wherein the processing circuit stores in the memory state history information indicating the history of the battery state of the battery pack while it is mounted on the mobile body, linked with battery identification information for identifying the battery pack; transmits the state history information stored in the memory to the external storage device via the communication interface, linked with the battery identification information; and after the transmission of the state history information to the external storage device is completed, erases part or all of the transmitted state history information from the memory.

[0008] A mobile device according to one aspect of the present disclosure includes a vehicle body to which a battery pack can be attached and detached, a vehicle-side memory fixed to the vehicle body, a first communication interface capable of communicating with the battery pack mounted on the vehicle body, a second communication interface capable of communicating with an external storage device, and a processing circuit, wherein the processing circuit receives battery identification information for identifying the battery pack from the battery pack via the first communication interface, stores the received battery identification information in the vehicle-side memory, stores state history information indicating the history of the battery state of the battery pack while it is mounted on the vehicle body in the vehicle-side memory in association with the battery identification information, and transmits the state history information stored in the vehicle-side memory in association with the battery identification information via the second communication interface to the external storage device.

[0009] A server according to one aspect of the present disclosure comprises a communication interface capable of communicating with a plurality of mobile bodies equipped with battery packs, a memory, and a processing circuit, wherein the processing circuit sequentially receives, via the communication interface, status history information indicating the history of the battery state of the battery pack while it is mounted on the mobile body, which is linked to battery identification information for identifying the battery pack, as time changes, and aggregates and stores each of the sequentially received status history pieces of information in the memory, linked to the battery identification information. [Effects of the Invention]

[0010] According to one aspect of this disclosure, it is possible to manage the battery status history of a battery pack while suppressing an increase in the cost of the battery pack. [Brief explanation of the drawing]

[0011] [Figure 1] This is a schematic diagram showing the general configuration of a battery management system for implementing a battery management method according to one embodiment. [Figure 2] Figure 1 is an example of a right-side view of an electric motorcycle. [Figure 3]Figure 1 is a block diagram showing an example of the electrical system of an electric motorcycle. [Figure 4] This block diagram shows the configuration of the mobile terminal and server in Figure 1. [Figure 5] This is a flowchart showing the flow of the battery management method in the battery management system shown in Figure 1. [Figure 6] This table shows an example of the frequency of each state category, indicated by the battery discharge current and battery charge level. [Figure 7] This table shows an example of the frequency of each state category, indicated by battery temperature and battery charge level. [Figure 8] This diagram shows an example of the data structure sent from the vehicle's electronic equipment to the server. [Figure 9] This is an example of a histogram showing the frequency of belonging to a state category. [Figure 10] This table shows an example of the frequency of belonging to a state category indicated by the battery charge level. [Figure 11] This table shows an example of the frequency of belonging to a state category indicated by the battery's discharge current. [Figure 12] This table shows an example of the frequency of each state category indicated by battery temperature. [Figure 13] This table shows an example of the frequency of states belonging to the status categories indicated by the usage mode. [Figure 14] Here is another example of a histogram showing the frequency of belonging to a state category. [Modes for carrying out the invention]

[0012] The embodiments will be described below with reference to the drawings.

[0013] (System Overview) FIG. 1 is a schematic diagram showing a general configuration of a battery management system 1 for implementing a battery management method according to an embodiment. The battery management system 1 is a system for managing a plurality of battery packs 30 that are detachably mounted on the vehicle bodies 11 of a plurality of moving bodies 10 by a server 50. In the present embodiment, an electric two-wheeler 10 is described as an example of the moving body 10.

[0014] The electric two-wheeler 10 includes a vehicle body 11 and a battery pack 30. The battery pack 30 is detachably assembled to the vehicle body 11.

[0015] In the present embodiment, the battery pack 30 can be detached from and attached to various vehicle bodies 11. For example, in the battery management system 1, when the remaining battery level of a certain battery pack 30 mounted on the running electric two-wheeler 10 becomes very low, the user of the vehicle body 11 can replace the battery pack 30 with a low remaining battery level with another fully charged battery pack 30 at a predetermined battery pack station 2 or the like.

[0016] In the battery management system 1 of the present embodiment, the usage history of the battery pack 30 is stored in the server 50. Specifically, state history information indicating the history of the state of the battery pack 30 when the battery pack 30 is mounted on the vehicle body 11 is once stored in the memory 19b (see FIG. 3) of the electronic device on the vehicle body 11 side. Thereafter, when the electronic device on the vehicle body 11 side and the portable terminal 40 owned by the user are communicatively connected, various information including the state history information is sent from the electric two-wheeler 10 to the server 50 via the portable terminal 40. In the server 50, the received state history information is stored in association with the battery identification information. For example, the state history information stored in the server 50 is used for analyzing the state of the battery pack or grasping the usage tendency of the battery pack. For example, the information stored in the server 50 can be accessed from an information terminal device 60 outside the server 50 via the Internet or the like. Hereinafter, the components of the battery management system 1 will be sequentially described.

[0017] (Electric Two-Wheeler) Figure 2 is an example of a right side view of the electric motorcycle 10 shown in Figure 1. As shown in Figure 2, the electric motorcycle 10 comprises a body 11 and a battery pack 30. The battery pack 30 is detachable from the body 11.

[0018] The vehicle body 11 is supported by the front wheels 12, which are driven wheels, and the rear wheels 13, which are driven wheels. The vehicle body 11 supports an electric motor 14, which is the source of propulsion. The electric motor 14 generates a driving force that is transmitted to the rear wheels 13, which are driven wheels. The driving force generated by the electric motor 14 is transmitted to the rear wheels 13 via a power transmission mechanism 15. The power transmission mechanism 15 includes a transmission 15a that changes the rotation speed of the electric motor 14, and a mechanism 15b (for example, a chain drive mechanism or a belt drive mechanism) that transmits the rotational power output from the transmission 15a to the axle of the rear wheels 13.

[0019] The vehicle body 11 has a vehicle frame, which has a head pipe 11a and a pair of left and right main frames 11b extending rearward from the head pipe 11a. The head pipe 11a rotatably supports the steering shaft 11c. A front fork 11d extending substantially vertically is connected to the steering shaft 11c, and the front wheel 12 is rotatably supported at the lower end of the front fork 11d. A bar-type handle 11e extending left and right is connected to the upper end of the steering shaft 11c. The right grip of the handle 11e is an accelerator grip for adjusting the driving force generated by the electric motor 14. When the accelerator grip is rotated, the amount of rotation is detected by the accelerator sensor 18 (see Figure 3).

[0020] A meter device 19 is located in front of the handlebars 11e. The meter device 19 has a display 19c that shows the driving speed, motor rotation speed, and battery level. The meter device 19 is supported by the head pipe 11a via a bracket 16.

[0021] The vehicle body 11 has a battery housing space for housing a battery pack 30. The battery housing space is located, for example, between a pair of main frames 11b in the left-right direction. Specifically, a battery case 17 having the battery housing space is positioned between a pair of main frames 11b in the left-right direction and fixed to the pair of main frames 11b. By moving the battery pack 30 relative to the battery case 17, for example in the vertical direction, it is possible to insert the battery pack 30 into or remove it from the battery housing space from above the battery case 17.

[0022] Figure 3 is a block diagram showing an example of the electrical system of the electric motorcycle 10 shown in Figure 1. In addition to the meter device 19 described above, an Electronic Control Unit (ECU) 21 and an inverter device 22 are fixed to the vehicle body 11 of the electric motorcycle 10. The meter device 19, ECU 21, and inverter device 22 are connected to each other via CAN (Controller Area Network) 20 so that they can communicate with one another. Furthermore, as will be described later, when the battery pack 30 is housed in the battery compartment, the equipment built into the battery pack 30 is electrically connected to the meter device 19, ECU 21, and inverter device 22 on the vehicle body 11.

[0023] The meter device 19 displays the driving speed, motor rotation speed, and battery level, etc. The meter device 19 includes a CPU (Central Processing Unit) 19a, memory 19b, display 19c, and communication device 19d. These components 19a, 19b, 19c, and 19d are connected to each other so as to be able to communicate with one another. The CPU 19a controls the operation of the meter device 19. The memory 19b stores various programs and data necessary for the operation of the meter device 19. For example, the memory 19b stores a battery management program that includes instructions for executing the battery management method described later. The memory 19b does not have to be a single storage device, but may be composed of multiple storage devices. For example, the memory 19b may be one of several types of storage devices such as RAM, ROM, hard disk, and flash memory, or it may be composed of a combination of two or more. For example, the various operations of the meter device 19 are realized by the CPU 19a executing the program stored in the memory 19b.

[0024] Furthermore, as will be described later, state history information indicating the state history of the battery pack 30 is stored in memory 19b as overwritable data. The CPU 19a updates and stores the state history information stored in memory 19b based on the battery state information received by the meter device 19, as described later.

[0025] Based on the data received via CAN20, the CPU 19a causes the display unit 19c of the meter device 19 to display the driving speed, motor rotation speed, and battery level, etc. In this embodiment, the display unit 19c is a liquid crystal display device that displays the driving speed, motor rotation speed, and battery level, etc., in digital format. However, the meter device 19 may also include an instrument that displays the driving speed, etc., in analog format, either instead of or in addition to the liquid crystal display device, as the display unit 19c.

[0026] The communication device 19d is a module having a communication circuit for wireless communication with the mobile terminal 40. For example, the communication device 19d is composed of an antenna, an RF (Radio Frequency) circuit, etc. In this embodiment, the wireless communication between the communication device 19d and the first communication device 44 of the mobile terminal 40 that communicates with the communication device 19d is a short-range wireless communication such as Bluetooth® communication, and wireless communication becomes possible when pairing is established. The communication device 19d and the first communication device 44 may communicate with each other via a wired connection. The communication device 19d may also have a function that allows it to communicate with a server via a public wireless network without going through the mobile terminal 40.

[0027] The CPU 19a and communication device 19d in the meter device 19 are examples of processing circuits. Memory 19b is an example of vehicle-side memory. The meter device 19 is an example of a memory control device.

[0028] The ECU 21 is a control unit that determines the driving power of the electric motorcycle 10 according to the operation commands generated by the user and the vehicle status. The ECU 21 controls the inverter device 22 according to the operation commands generated by the user and the vehicle status, and performs driving control according to the user request and the vehicle status. For example, the ECU 21 receives the amount of accelerator operation detected by the accelerator sensor 18 and generates a rotation speed command for the electric motor 14 based on the received signal. The ECU 21 controls the switching operation of the inverter device 22 by sending the rotation speed command to the inverter device 22 via CAN 20.

[0029] The ECU21 includes a CPU21a and a memory21b. These CPU21a and memory21b are connected to each other so that they can communicate with one another. The CPU21a controls the operation of the ECU21. The memory21b stores various programs and data necessary for the operation of the ECU21. The memory21b does not have to be a single storage device; it may be composed of multiple storage devices. For example, the memory21b may be one of several types of storage devices such as RAM, ROM, hard disk, and flash memory, or it may be composed of a combination of two or more. For example, various operations of the ECU21 are realized by the CPU21a executing programs stored in the memory21b.

[0030] The inverter device 22 is electrically connected to the battery 31 of the battery pack 30 housed in the battery housing space. The inverter device 22 converts the DC power discharged from the battery pack 30 into AC power. Based on commands received from the ECU 21, the inverter device 22 adjusts the output voltage and frequency. The power output from the inverter device 22 is sent to the electric motor 14, which operates using the AC power from the inverter device 22 to generate driving force.

[0031] The inverter device 22 includes a CPU 22a, a memory 22b, and an inverter circuit 22c. The CPU 22a controls the operation of the inverter device 22. That is, the CPU 22a functions as part of a control circuit that controls the switching operation of the inverter circuit 22c. The memory 22b stores various programs and data necessary for the operation of the inverter device 22. The memory 22b does not have to be a single storage device, but may be composed of multiple storage devices. For example, the memory 22b may be one of several types of storage devices such as RAM, ROM, hard disk, and flash memory, or it may be composed of a combination of two or more. Various operations of the inverter device 22 are realized, for example, by the CPU 22a executing a program stored in the memory 22b.

[0032] Furthermore, one or more other control devices 24, in addition to the ECU 21, are also fixed to the vehicle body 11. Note that in Figure 3, for the sake of simplification, one or more of the other control devices 24 are shown together as a single block. One or more of the other control devices 24 are connected to the CAN 20. That is, one or more of the other control devices 24 can communicate via the CAN 20 with the meter device 19, the ECU 21, the inverter device 22, and the battery pack 30 housed in the battery housing space.

[0033] Examples of control performed by one or more other control devices 24 include automatic cruise control, traction control, ABS control, suspension control, steering control, and cornering lights. Cornering lights are a function that automatically illuminates the area behind the electric motorcycle 10 when it is turning. Furthermore, if the electric motorcycle 10 is equipped with sensors (such as laser radar, millimeter-wave radar, ultrasonic sensors, or cameras) that detect obstacles or objects around it, the control device 24 may be a device that controls such sensors. Each control device 24 includes a memory for storing various programs and data, and a CPU for executing the programs stored in the memory.

[0034] The battery pack 30 includes a battery 31, a battery management unit (BMU) 32, a casing 33, a voltage sensor 34, a temperature sensor 35, and a current sensor 36. The battery 31, battery management unit 32, voltage sensor 34, temperature sensor 35, and current sensor 36 are housed in the casing 33. When the battery pack 30 is housed in the battery housing space, the battery 31 and battery management unit 32 of the battery pack 30 are electrically connected to the equipment on the vehicle body 11 side.

[0035] Specifically, the casing 33 of the battery pack 30 has a battery-side power supply connector 33a. The battery-side power supply connector 33a is electrically connected to the battery 31. In addition, a vehicle-side power supply connector 23a is fixed to the vehicle body 11. The vehicle-side power supply connector 23a is electrically connected to the inverter device 22. For example, the vehicle-side power supply connector 23a is part of the battery case 17. When the battery pack 30 is housed in the battery housing space, the battery-side power supply connector 33a is mechanically and electrically connected to the vehicle-side power supply connector 23a. This makes it possible to supply power from the battery 31 to the inverter device 22 to drive the electric motor 14 (which may also be called a drive motor).

[0036] Furthermore, the casing 33 of the battery pack 30 has a battery-side communication connector 33b. The battery-side communication connector 33b is electrically connected to the battery management unit 32. In addition, a vehicle-side communication connector 23b is fixed to the vehicle body 11. The vehicle-side communication connector 23b is connected to the CAN 20. For example, the vehicle-side communication connector 23b is part of the battery case 17. When the battery pack 30 is housed in the battery housing space, the battery-side communication connector 33b is mechanically and electrically connected to the vehicle-side communication connector 23b. This allows the battery management unit 32 to communicate with various vehicle-side electronic devices such as the meter device 19, ECU 21, and inverter device 22 via the CAN 20. In other words, the CAN 20 and the vehicle-side communication connector 23b are part of a communication interface that can communicate with the battery pack 30 mounted on the vehicle body 11.

[0037] Battery 31 is composed of multiple battery cells connected in series.

[0038] The battery management unit 32 includes a CPU 32a and memory 32b. The CPU 32a controls the operation of the battery management unit 32. Memory 32b stores various programs and data necessary for the operation of the battery management unit 32. Memory 32b does not have to be a single storage device, but may be composed of multiple storage devices. For example, memory 32b may be one of several types of storage devices such as RAM, ROM, hard disk, and flash memory, or it may be composed of a combination of two or more. Memory 32b may include, for example, RAM, ROM, hard disk, or flash memory. Various operations of the battery management unit 32 are realized, for example, by the CPU 32a executing programs stored in memory 32b.

[0039] Memory 32b stores battery identification information for identifying the battery pack 30 (i.e., for identifying the battery 31).

[0040] The battery management unit 32 is electrically connected to the voltage sensor 34, the temperature sensor 35, and the current sensor 36. The voltage sensor 34 detects the voltage value of each battery cell in the battery 31. The temperature sensor 35 detects the temperature of the battery 31. The current sensor 36 detects the charging current to the battery 31 and the discharge current from the battery 31. Based on the information detected by the voltage sensor 34, the temperature sensor 35, and the current sensor 36, the battery management unit 32 monitors the status of the battery 31.

[0041] For example, the battery management unit 32 estimates the amount of electricity stored in the battery 31, i.e., the state of charge (SOC) of the battery 31. The battery management unit 32 estimates this from, for example, the voltage value of each battery cell detected by the voltage sensor 34 and the amount of charging and discharging current detected by the current sensor 36. In other words, the battery management unit 32 functions as one of the sensors that detects information related to the state of the battery 31 mounted on the vehicle body 11.

[0042] For example, the battery management unit 32 determines whether the temperature of the battery 31 is within a normal range based on the value detected by the temperature sensor 35.

[0043] For example, the battery management unit 32 determines whether the discharge current from the battery 31 is within a normal range based on the value detected by the current sensor 36.

[0044] The charge level, temperature, and discharge current of the battery 31 are included in the battery status information that indicates the state of the battery 31. The battery status information, along with the battery identification information, is output to the CAN 20 from the battery management unit 32 at all times (at predetermined time intervals). The battery status information thus output to the CAN 20 is used to generate state history information that is stored in the storage device on the vehicle body 11 side (in this example, the memory 19b of the meter device 19), as will be described later.

[0045] (Mobile device) Figure 4 is a block diagram showing the configuration of the mobile terminal 40 and server 50 shown in Figure 1. The mobile terminal 40 is an information communication terminal capable of communicating with the electric motorcycle 10 and the server 50. An example of the mobile terminal 40 is a smartphone carried by the user. The mobile terminal 40 includes a CPU 41, memory 42, touchscreen 43, first communication device 44, and second communication device 45. These components 41, 42, 43, 44, and 45 are connected to each other so that they can communicate with one another.

[0046] The CPU 41 controls the operation of the mobile terminal 40. The memory 42 stores various programs and data necessary for the operation of the mobile terminal 40. The memory 42 does not have to be a single storage device, but may be composed of multiple storage devices. For example, the memory 52 may be one of several types of storage devices such as RAM, ROM, and flash memory, or it may be composed of a combination of two or more. Various operations of the mobile terminal 40 are realized, for example, by the CPU 41 executing programs stored in the memory 42.

[0047] The touchscreen 43 serves as both an input device for receiving user input and a display device for showing a screen visible to the user. Specifically, the touchscreen 43 includes a semi-transparent display and backlight LEDs (display device) and a touch panel (input device) arranged on the display. The input device and display device of the mobile terminal 40 do not have to be integrated, but may be separate components.

[0048] The first communication device 44 is a module having a communication circuit for wireless communication with the electric motorcycle 10. Since the first communication device 44 has the same configuration as the communication device 19d, its description is omitted.

[0049] The second communication device 45 is a module having a communication circuit for connecting to the internet. For example, the second communication device 45 is a wireless LAN module. For example, the second communication device 45 connects to the internet via a public wireless network. The second communication device 45 communicates with the server 50 via the connected internet.

[0050] (server) Server 50 includes a CPU 51, memory 52, and a communication device 53. These components 51, 52, and 53 are connected to each other so that they can communicate with one another.

[0051] The CPU 51 controls the operation of the server 50. The memory 52 stores various programs and data necessary for the operation of the server 50. The memory 52 does not have to be a single storage device, but may be composed of multiple storage devices. For example, the memory 52 may be one of several types of storage devices such as RAM, ROM, hard disk, and flash memory, or it may be composed of a combination of two or more. Various operations of the server 50 are realized, for example, by the CPU 51 executing programs stored in the memory 52.

[0052] The communication device 53 is a module having a communication circuit for connecting to the internet. For example, the communication device 53 may be a wireless LAN module or a LAN module. Information received via the communication device 53 is stored in memory 53. The communication device 53 communicates with the user's mobile terminal 40 of the electric motorcycle 10 via the connected internet. The server 50 is an example of an external storage device.

[0053] (Battery management method) Figure 5 is a flowchart showing the flow of the battery management method in the battery management system 1. By mounting the battery pack 30 on the vehicle body 11, the battery management unit 32 and equipment such as the meter device 19 on the vehicle body 11 are electrically connected to each other via CAN 20 (step S1). That is, communication becomes possible between the battery management unit 32 and the meter device 19. Also, power can be supplied from the battery 31 to the electric motor 14 via the inverter device 22.

[0054] The battery management unit 32 continuously outputs battery identification information and battery status information stored in memory 32b to CAN20 while power is being supplied from the battery 31 to the electric motor 14 (steps S2, S3). Specifically, when the main switch (which may also be called the power switch or ignition switch) that makes the electric motorcycle 10 ready to run is turned on, the battery pack 30 continues to output battery identification information and battery status information to CAN20. However, when the main switch is turned off, the battery pack 30 does not output battery identification information and battery status information to CAN20.

[0055] The meter device 19 receives battery identification information and battery status information output from the battery management unit 32. In the meter device 19, the CPU 19a generates status history information from the received battery status information, which has less data than the battery status information, and shows the history of the state of the battery 31 while it was installed in the vehicle body 11. The CPU 19a then stores the generated status history information in the memory 19b (step S4). In the memory 19b, the status history information is stored linked to the battery identification information.

[0056] Furthermore, the updating and storage of state history information will continue until the timing of the communication connection described in step S5 below is reached. Also, if the power supply to memory 19b is stopped before step S5 below (i.e., the main switch is turned off), the storage of state history information in memory 19b will be maintained.

[0057] The storage of state history information in step S4 will be explained in detail. As mentioned above, battery state information detected by the BMU32, voltage sensor34, temperature sensor35, and current sensor36 is continuously output. Storing all the output information in memory, that is, continuously storing the time-series data of battery state information in memory, would put a strain on memory capacity.

[0058] Therefore, in this embodiment, the meter device 19, based on the battery status information received from the battery pack 30, classifies the battery status into one of a predetermined number of status categories. The CPU 19a then stores in the memory 19b the frequency with which the battery status corresponding to that status category occurred. The method for storing status history information as frequency information will be explained in detail with reference to Figures 6 and 7.

[0059] Figure 6 is a table showing an example of the frequency of belonging to each state category, indicated by the discharge current and state of charge (SOC) of the battery 31. The CPU 19a of the meter device 19 classifies the state of the battery 31 corresponding to the received battery state information into one of several state categories, based on the values ​​of the charge rate and discharge current of the battery 31 included in the received battery state information.

[0060] In the example in Figure 6, the range of discharge current values ​​is divided into five ranges: less than A1, A1 or greater but less than A2, A2 or greater but less than A3, A3 or greater but less than A4, and A4 or greater. Furthermore, from the perspective of the charge level value, it is divided into five ranges: 0% or greater but less than 15%, 15% or greater but less than 30%, 30% or greater but less than 70%, 70% or greater but less than 85%, and 85% or greater but 100% or less. In other words, the combination of the discharge current of battery 31 and the charge level (SOC) of battery 31 is classified into one of 25 state categories in a 5x5 grid.

[0061] After classifying the state into a category, the CPU 19a stores in memory 19b the time the battery 31 was used in the state corresponding to that category (hereinafter also referred to as the usage time per category), as the frequency with which the state of the battery 31 corresponding to that category occurred. In the table in Figure 6, the unit of the value in each cell (X1 to X25) corresponding to the state category is time (hour).

[0062] Specifically, memory 19b stores the usage time for each of the 25 state categories, linked to the battery identification information. Based on the received battery state information, CPU 19a counts the frequency (time in this example) of belonging to each state category and updates the usage time for each state category stored in memory 19b. For example, suppose the battery 31 is in a state where the charge level is 85% or higher and 100% or lower, and a current in the range of A2 or higher and less than A3 has been continuously discharged for 1 hour. In this case, 1 hour is added to the usage time for each state category corresponding to the state where the charge level is 85% or higher and 100% or lower, and the discharge current value is A2 or higher and less than A3.

[0063] Figure 7 is a table showing an example of the frequency of belonging to each state category, indicated by the temperature and state of charge (SOC) of the battery 31. The CPU 19a of the meter device 19 classifies the state of the battery 31 corresponding to the received battery state information into one of several state categories, different from the state categories shown in Figure 6, based on the values ​​of the battery 31's SOC and temperature included in the received battery state information.

[0064] In the example in Figure 7, the temperature range of the battery 31 is divided into six ranges: less than B1, B1 or greater but less than B2, B2 or greater but less than B3, B3 or greater but less than B4, B4 or greater but less than B5, and B5 or greater. Furthermore, from the perspective of the charge level, it is divided into five ranges: 0% or greater but less than 15%, 15% or greater but less than 30%, 30% or greater but less than 70%, 70% or greater but less than 85%, and 85% or greater but 100% or less. In other words, the combination of the temperature of the battery 31 and the charge level (SOC) of the battery 31 is classified into one of 6 × 5 = 30 state categories.

[0065] After classifying into a state category, the CPU 19a stores the usage time for each category in memory 19b as the frequency with which the battery state corresponding to that state category occurred. In the table in Figure 7, as in Figure 6, the unit of the value in each cell (Y1 to Y30) corresponding to the state category is time (hour).

[0066] Specifically, memory 19b stores the usage time for each of the 30 state categories, linked to the battery identification information. Based on the received battery state information, CPU 19a counts the frequency (time in this example) of belonging to each state category and updates the usage time for each state category stored in memory 19b. For example, suppose the battery 31 has been in a state where the charge level is 85% or higher and 100% or lower, and the temperature is between B3 and B4 for 1 hour. In this case, 1 hour is added to the usage time for the state category corresponding to the charge level being 85% or higher and 100% or lower, and the battery 31 temperature being between B3 and B4.

[0067] Thus, the state history information, which shows the history of the battery 31's state, is stored as information that shows the cumulative frequency (time in this example) of the battery 31 belonging to a predetermined state. Therefore, the history of the battery 31's state can be stored in a form that requires a small amount of data.

[0068] In the examples in Figures 6 and 7, the range of charge levels within each state category is not uniform. Specifically, the range of charge levels between 30% and 70% is approximately 40%, while the range of other charge levels is approximately 15%. In other words, the range of charge levels in categories close to 0% or 100% is relatively small. The reason for varying the range of information related to the state of the battery 31 (in other words, the range of sensor detection values ​​required to belong to that state category) for each state category is to make it easier to evaluate the battery's degradation status.

[0069] To explain in more detail, the system developers of Battery Management System 1, through diligent research, concluded that the charge level, discharge current, and temperature of Battery 31 are particularly useful information for understanding the degradation of Battery 31. Furthermore, the system developers concluded that the longer the battery 31 remains near 100% or 0%, the faster it degrades. They also concluded that if Battery 31 is used at a temperature far from room temperature or if the discharge current is high while it is near 100% or 0%, the degradation will be even faster. For example, in the range that includes Battery 31 with a charge level of 50%, in this example, the range between 30% and 70% charge levels, battery degradation is less likely to occur compared to other ranges. Therefore, by subdividing the categories that are prone to causing Battery 31 degradation, it is made easier to evaluate the battery's degradation status. In other words, by increasing the amount of information in the areas that are most likely to affect degradation, it is made easier to evaluate the battery's degradation status.

[0070] For example, the range of discharge current values ​​may also be varied for each state category. For instance, the range of A3 or higher and less than A4 (i.e., |A4-A3|), which represents a high current that is likely to cause battery degradation, may be narrower than the range of A2 or higher and less than A3 (i.e., |A3-A2|), which represents a lower current than the range of A3 or higher and less than A4. For example, the range of B4 or higher and less than B5 (i.e., |B4-B3|), which represents a high temperature state that is likely to cause battery degradation, may be narrower than the range of B2 or higher and less than B3 (i.e., |B3-B2|), which represents a lower temperature than the range of B4 or higher and less than B5.

[0071] Returning to Figure 5, the meter device 19 periodically or irregularly transmits the state history information stored in memory 19b from the electric motorcycle 10 to the server 50 via a portable terminal 40 carried by the user of the electric motorcycle 10. Specifically, when the meter device 19 and the user's portable terminal 40 establish a communication connection (step S5), the CPU 19a of the meter device 19 transmits various information, including state history information and battery identification information, to the portable terminal 40 via the communicator 19d (step S6). The portable terminal 40 transmits the received information to the server 50 via the second communicator 45 (step S7).

[0072] Figure 8 shows an example of the data structure sent from a meter device 19, which is an example of electronic equipment on the vehicle body, to the server 50. The server 50 contains status history information (in this embodiment, information indicating the frequency of each status category) and battery identification information (also referred to as battery ID), as well as vehicle identification information (also referred to as vehicle ID), user identification information (also referred to as user ID), usage industry information, detection period information, battery usage time information, transmission date and time information, location identification information (also referred to as location ID), and more. All of this information sent to the server 50 is related to each other.

[0073] Vehicle identification information is information used to identify the vehicle body 11. Vehicle identification information includes vehicle type information indicating the type of vehicle body 11. However, various types of information sent to the server 50 may include vehicle type information separately from the vehicle identification information.

[0074] User identification information is information for identifying the user of the vehicle 11. Industry of use information is information for classifying how the electric motorcycle 10 is used. Industry of use information allows for identification of, for example, whether it is used by a user for hobbies or leisure, used for work such as by a delivery company using the electric motorcycle 10, or used by a rental company that rents it out to users who wish to use it. User identification information may also include information indicating the user's characteristics or the country or region where the user lives. User identification information may also include industry of use information.

[0075] In this embodiment, vehicle identification information, user identification information, and industry information are stored in the memory 19b of the meter device 19. However, vehicle identification information, user identification information, and industry information may also be stored in the memory of another electronic device fixed to the vehicle body 11, such as the ECU 21. Furthermore, the user identification information and industry information stored in the memory may be changed by the user by operating the meter device 19 or a portable terminal 40.

[0076] The detection period information indicates the detection period of the source data (i.e., battery status information) used to generate the status history information sent to the server 50. In other words, the detection period information indicates the time period for which the status history information sent to the server 50 covers the battery status history. For example, the detection period information may include information indicating the start and end dates and times for acquiring the battery status information.

[0077] Battery usage time information indicates the usage time of the battery pack 30. For example, the battery usage time information may also indicate the time elapsed from the date of manufacture of the battery pack 30 to the present. For example, the battery usage time information may also indicate the elapsed time since the user started using the battery pack 30. The battery usage time information may also indicate the time during which power is supplied to the vehicle's electronic equipment.

[0078] The transmission date and time information indicates the date and time when various information, including status history information, was transmitted to the mobile terminal 40 or the server 5.

[0079] Location identification information is information for identifying the region where the vehicle body 11 is located. For example, location identification information is information indicating the geographical location of the electric motorcycle 10 when the information is transmitted or when the battery status information is acquired. For example, location identification information may be the location information of the electric motorcycle 10 at the time of information transmission, acquired by the GPS (Global Positioning System) installed in the electric motorcycle 10. For example, location identification information may be information indicating the location of the base station that relayed the information at the time of information transmission. Location identification information may also be country-specific identification information assigned to the vehicle body. Location identification information may be location region information registered in advance by the user of the electric motorcycle 10, or it may be information acquired by sensors, etc.

[0080] In steps S5 and S6 of Figure 5, the electric motorcycle 10 may communicate with the mobile terminal 40 at predetermined timings. For example, the electric motorcycle 10 may periodically connect to the mobile terminal 40 when the electric motorcycle 10 is started, i.e., when the main switch is turned on. As another example, the electric motorcycle 10 may connect to the mobile terminal 40 at irregular timings when the driver commands the electric motorcycle 10 or the mobile terminal 40 to connect to each other. As yet another example, the electric motorcycle 10 may connect to a mobile terminal owned by the mechanic when it is being serviced.

[0081] In server 50, the received status history information and battery identification information are linked together and stored in memory 52 (step S8). Once server 50 has stored the information transmitted from the vehicle body 11, such as the status history information, it sends storage completion information to the mobile terminal 40 to indicate that storage is complete (step S9).

[0082] When the mobile terminal 40 receives memory completion information from the server 50, it transmits the memory completion information to the meter device 19, which is an electronic device on the vehicle body 11 (step S10). When the meter device 19 receives the memory completion information, it erases the transmitted state history information (step S11).

[0083] In this way, status history information is accumulated in the server 50. An information terminal device 60 authorized to access the information stored in the server 50 can visualize and display the status of the battery pack 30 from the status history information stored in the server 50 in the form of a histogram or table. For example, Figure 9 shows an example of a histogram showing the frequency of belonging to a status category. By outputting the frequency of each status category as a histogram to the display of the information terminal device 60 in this way, it becomes easy to understand the usage history of the battery pack 30. The information terminal device 60 may be a device used by the battery pack developer or battery maintenance company, or it may be a mobile terminal 40 owned by the user.

[0084] Incidentally, there are cases where the battery pack 30 is removed from the vehicle body 11 and installed in another vehicle body 11. Even in this case, the server 50 receives and stores new status history information from the other vehicle body 11 to which the battery pack 30 has been installed. By aggregating the status history information for each battery identification information of the battery pack 30, the server 50 can centrally manage the elapsed state of the battery pack 30 over time.

[0085] More specifically, both the state history information obtained from the vehicle in which the battery pack 30 was previously installed and the state history information obtained from the vehicle in which the battery pack 30 is currently installed are linked to the same battery identification information. Therefore, the server 50 can combine the state history information obtained from the vehicle in which the battery pack 30 was previously installed with the state history information obtained from the vehicle in which the battery pack 30 is currently installed. In this way, the battery status can be analyzed using not only the state history information from when the battery was installed in the current vehicle 11, but also the state history information from when it was installed in previous vehicle 11s, allowing for a more accurate understanding of the battery status.

[0086] In addition, the server 50 can aggregate status history information for each vehicle identification information or for each user identification information based on the aggregated information. Furthermore, the server 50 may diagnose the usability of the battery pack 30 by setting different conditions depending on the vehicle type, industry of use, or region of use.

[0087] For example, it is easy to compare the state history information stored in the server 50 with the state history information associated with a vehicle identification information representing a certain vehicle A, and the state history information associated with a vehicle identification information representing a different vehicle B. In this way, state history information can be aggregated for each vehicle identification information, making it easier to analyze which vehicle the battery pack 30 was installed in when the malfunction began.

[0088] Furthermore, it is possible to access server 50 from a terminal outside server 50 and send the information aggregated in server 50 from server 50 to the terminal outside server 50. This allows the terminal outside server 50 to perform a diagnosis regarding the usability of the battery pack 30. Examples of terminals outside server 50 include an information terminal device 60 authorized to access information stored in server 50, and a mobile terminal 40 owned by a user. The terminal outside server 50 may also receive the diagnosis results of the battery pack 30 performed by server 50.

[0089] The CPU 51 of the server 50 can diagnose the usability of the battery pack 30 based on the aggregated information. When diagnosing the battery pack 30 in the server 50, for example, the CPU 51 in the server 50 determines the degree of degradation of the battery 31 from the state history information stored in the memory 52, which is associated with the same battery identification information. For example, the CPU 51 determines the degree of degradation and usability based on the frequency of factors that accelerate degradation. More specifically, the CPU 51 may determine that the degree of degradation is high if the time spent in a low or high state category of SOC (for example, a range of 0% or more but less than 15%, or a range of 85% or more but 100% or less) exceeds a predetermined period. Similarly, the CPU 51 may determine that the degree of degradation of the battery 31 is high if the time spent outside a predetermined temperature range or the time spent with excessive current exceeds a predetermined period. Battery pack developers and battery service providers may collect battery packs 30 with a high degree of battery degradation 31, perform a detailed diagnosis, and evaluate whether there are any abnormalities in the battery 31.

[0090] Furthermore, by using the information aggregated in server 50, it becomes easier to analyze the causes of degradation. Additionally, from the information aggregated in server 50, a group of drivers with a high degree of degradation may be identified, and the usage environment and driving operations of the electric motorcycle 10 that affect the degradation of battery 1 may be analyzed. Furthermore, the required battery performance may be analyzed based on the information aggregated in server 50. In this way, by aggregating historical information in server 50, analysis from diverse perspectives becomes possible.

[0091] Furthermore, in step S11, the meter device 19 erases the state history information from memory 19b. In this embodiment, all of the state history information is erased from memory 19b, but some of the state history information may be erased from memory 19b. Also, the state history information may not be erased from memory 19b at all. In other words, step S11 may be omitted.

[0092] For example, state history information is stored in memory 19b, linked to battery identification information. When the battery pack 30 installed in the vehicle body 11 is changed, the state history information of the newly installed battery pack 30 is stored in memory 19b, linked to the battery identification information of the newly installed battery pack 30, in addition to the state history information stored in memory 19b, linked to the battery identification information of the newly installed battery pack 30. Each time the battery pack 30 installed in the vehicle body 11 is replaced, memory 19b reserves a storage area for storing state history information for each battery pack 30, which can put a strain on the memory capacity. On the other hand, state history information that has already been sent to the server 50 does not need to be stored in memory 19b. For this reason, the meter device 19 deletes unnecessary state history information, such as the state history information stored in link to the battery identification information of the previously installed battery pack 30. The deletion of unnecessary state history information can be performed, for example, after the battery pack 30 has been replaced.

[0093] For example, the communication connection between the meter device 19 and the mobile terminal 40 in step S5 can be achieved, for example, by the user of the mobile terminal 40 launching a predetermined application program stored in the memory 42 of the mobile terminal 40. In this case, unless the user launches the application program, the server 50 will not collect the status history information of the battery pack 30. Therefore, the electronic equipment on the vehicle body 11 may be equipped with a function that prompts the user to communicate with the electronic equipment of the vehicle body 11 via the mobile terminal 40.

[0094] For example, if communication between the meter device 19 and the mobile terminal 40 is not established for a predetermined number of days, the CPU 19a of the meter device 19 will display a message or warning on the display unit 19c prompting communication between the meter device 19 and the mobile terminal 40.

[0095] Alternatively, the electric motorcycle 10 may be configured not to operate unless a communication connection is established between the meter device 19 and the mobile terminal 40 when the user gets on the electric motorcycle 10. For example, the CPU 21a of the ECU 21 determines whether or not a communication connection has been established between the meter device 19 and the mobile terminal 40. If it is determined that there is no communication connection between the meter device 19 and the mobile terminal 40, the CPU 21a of the ECU 21 will not send a command to the inverter device 22 to supply power to the electric motor 14, even if the accelerator sensor 18 detects accelerator operation by the user.

[0096] By providing the electronic equipment on the vehicle body 11 with a function that prompts the user to communicate with the electronic equipment on the vehicle body 11 using the mobile terminal 40, it becomes easier to aggregate the status history information of the battery pack 30 on the server 50, even when user operation is required for communication between the mobile terminal 40 and the electronic equipment on the vehicle body.

[0097] (Effects and Benefits) As described above, according to this embodiment, state history information showing the state history of the battery 31 is stored in the vehicle body 11 side memory 19b, rather than in the memory 32b built into the battery pack 30. Therefore, the capacity of the memory 32b on the battery pack 30 side can be reduced, and the cost increase of the battery pack 30 can be suppressed.

[0098] Furthermore, the state history information stored in the memory 19b on the vehicle body 11 is linked to the battery identification information and sent to the server 50. Therefore, even if the battery pack 30 is installed in a different vehicle body 11 than the one it was previously installed in, the server 50 has accumulated the state history information acquired while it was installed in the previous vehicle body 11, allowing for centralized management of the battery state history of the battery 31 of the battery pack 30.

[0099] Furthermore, in this embodiment, after the transmission of status history information from the meter device 19 to the server 50 via the mobile terminal 40 is completed, the meter device 19 erases the status history information from the memory 19b. This makes it easier to reduce not only the memory capacity of the battery pack 30 but also the capacity of the memory 19b of the vehicle body 11.

[0100] Furthermore, in this embodiment, the meter device 19 transmits the state history information stored in the memory 19b from the electric motorcycle 10 to the server 50 via a portable terminal 40 carried by the user of the electric motorcycle 10. This makes it easier to simplify the configuration of the communication device provided on the electric motorcycle 10.

[0101] Furthermore, in this embodiment, the meter device 19's CPU 19a classifies the battery state into one of a predetermined state category based on battery state information detected by the BMU 32, voltage sensor 34, temperature sensor 35, and current sensor 36. The CPU 19a then stores in memory 19b the frequency with which the battery state corresponding to that state category occurred. Therefore, compared to accumulating time-series data of battery state information in memory 19b, it is possible to avoid increasing the memory capacity required to store the battery state of 31.

[0102] (Other embodiments) This disclosure is not limited to the embodiments described above, and various modifications are possible without departing from the gist of this disclosure.

[0103] In the above embodiment, an electric motorcycle was given as an example of a mobile body having a vehicle body on which the battery pack can be attached and detached, but the mobile body may be another type of mobile body such as an electric vehicle. The mobile body may be, for example, a hybrid vehicle equipped with an internal combustion engine and an electric motor as a power source for driving. In addition to motorcycles, the mobile body may be a bicycle or a four-wheeled vehicle. Furthermore, the battery management method disclosed herein is more preferably used in saddle-type vehicles, which have less space to accommodate a large memory compared to four-wheeled vehicles. The battery pack may be used in common among different types of mobile bodies. For example, the battery pack may be mounted on a motorcycle and then mounted on another vehicle, such as a four-wheeled vehicle. The mobile body on which the battery pack is mounted may be a non-vehicle such as a lawnmower, power tool, vacuum cleaner or other electric work machine. The mobile body does not have to be a vehicle on which a user rides, and may be an unmanned mobile body on which no user rides.

[0104] In the above embodiment, the state history information was stored in the memory 19b of the meter device 19, but the memory in which the state history information is stored is not limited to this. For example, instead of being stored in the memory 19b of the meter device 19, the state history information may be stored in the memory 21b of the ECU 21, in the memory 22b of the inverter device 22, or in the memory of another control device 24. The state history information may also be stored in a memory mounted on an external electrical component, which is an electrical component other than the battery pack and fixed to the vehicle body, in other words, a vehicle-side memory. It is preferable that the vehicle-side memory be mounted on an external electrical component that also has functions other than storage.

[0105] By utilizing the memory storage function of external electrical components, there is no need to install a new storage device, thus reducing the number of parts. Furthermore, functions other than memory storage in external electrical components may include control functions for controlling the actuators being controlled. In this case, state history information is stored in a memory area that stores programs for implementing control functions or calculation information for executing programs. For example, control functions could include meter control, engine control, and battery control, as well as brake control, suspension control, lamp control, radar and camera control, solenoid valve control, and other control functions for actuators and sensors installed on the vehicle body. State history information is stored in a portion of the memory area for control functions.

[0106] Furthermore, as mentioned above, the state history information stored in memory is generated by processing battery state information into frequency information, thus reducing the data capacity. This makes it easier to store state history information without exceeding the memory capacity of the external electrical components. Also, as mentioned above, after the transmission of state history information from the external electrical component's memory to the server is completed, at least a portion of the transmitted state history information is erased from memory. This makes it easier to store state history information without exceeding the memory capacity of the external electrical components. Moreover, the external electrical components used to store state history information are not limited to one; multiple electrical components may be used. This allows for a larger overall system capacity for storing state history information. In the above description, the vehicle-side memory is said to have functions other than storage, but it is not limited to this, and may be an electrical component that only has a storage function.

[0107] Furthermore, if the mobile terminal 40 is fixed to the vehicle body 11, for example, by a detachable motorcycle mobile terminal holder attached to the vehicle body 11, the status history information can be stored in the memory 42 of the mobile terminal 40 fixed to the vehicle body 11. In other words, the memory of the mobile terminal 40 fixed to the vehicle body can also be called "vehicle-side memory fixed to the vehicle body".

[0108] The vehicle-side memory that stores the state history information preferably has the ability to erase the stored contents based on a command from the processing circuit, such as flash memory, and also has the function of retaining the stored contents even when the power supply is cut off.

[0109] In addition, the memory of the electrical components in the battery pack may be used as the memory for storing the state history information described above. Furthermore, although a portable terminal carried by the driver while driving or a maintenance terminal carried by a worker during maintenance is not fixed to the vehicle body, the state history information may be stored in the memory of the portable terminal or maintenance terminal that is not fixed to the vehicle body, as long as the portable terminal or maintenance terminal can communicate with the vehicle and transmit information to a server.

[0110] Furthermore, the processing circuit is not limited to the circuit of the meter device 19. Processing circuits of various control devices mounted on the vehicle can be used. For example, it could be the circuit of an ECU, the circuit of an inverter device, or, if a portable terminal is fixed to the vehicle body, the circuit of a portable terminal. The processing circuit may also consist of circuits including multiple electronic devices fixed to the vehicle body.

[0111] In a vehicle, the electrical component that generates state history information and the electrical component that stores the generated state history information may be the same or different. For example, in the above embodiment, the CPU 19a of the meter device 19 generates state history information as frequency information from the received battery state information and stores it in the memory 19b, but the circuit of another electrical component may generate the state history information, or the state history information may be stored in the memory of another electrical component. The circuit of the electrical component that generates the state history information may read previously stored state history information (frequency information) from the memory of the electrical component that stores the state history information, and add the state history information generated this time from the battery state information to the read frequency information, thereby generating state history information that shows the cumulative frequency from the past. The information stored in the memory may be updated by storing the state history information thus generated in the memory of the electrical component that stores the state history information.

[0112] Furthermore, while a meter device was described in the above embodiment as an example of a memory control device in a mobile vehicle equipped with a battery pack, the memory control device is not limited to this. The memory control device may be an ECU, an inverter device, or any other electrical component mounted on the vehicle body. The memory control device may consist of one or more devices other than the battery pack fixed to the vehicle body. The memory control device may also be a portable terminal equipped with a memory for storing state history information.

[0113] Furthermore, while a server was described in the above embodiment as an example of an external storage device to which state history information is sent from a mobile device, the external storage device is not limited to this. The external storage device may be any storage device located outside the vehicle, other than a server. For example, the external storage device may be a mobile device such as a smartphone or tablet. Alternatively, for example, the external storage device may be a computer on a local network (e.g., a personal computer).

[0114] In the above embodiment, the communication device that sends status history information to the mobile terminal 40 was part of the meter device 19, but the communication device that sends status history information to the mobile terminal may be separate from the meter device, or it may be part of other equipment fixed to the vehicle body.

[0115] In the above embodiment, status history information was transmitted from the electric motorcycle, which is the mobile vehicle, to the server 50 via a mobile terminal carried by the user. However, the status history information may also be transmitted from the mobile vehicle to the server without going through the user's mobile terminal. For example, the vehicle body of the mobile vehicle may be equipped with a communication circuit including an antenna that can connect to a public wireless network. In this case, the status history information may be transmitted from the vehicle body to the server regardless of whether the driver has a mobile terminal or not. The information may be transmitted from the mobile vehicle to the server wirelessly or via a wired connection.

[0116] The categories shown in Figures 6 and 7 are merely examples of state categories. The method of classifying state categories is not limited to these. For example, the range of charge levels in a state category may be uniform. For example, a state category may be classified by only one of the following: the charge level of battery 31, the discharge current of battery 31, or the temperature of battery 31, as shown in Figures 10, 11, and 12, respectively. Alternatively, a state category may be classified by a combination of two or more of the charge level of battery 31, the discharge current of battery 31, and the temperature of battery 31. A processing circuit such as a CPU may classify the battery state into one type of state category based on the battery state information, or it may classify it into multiple types of state categories (for example, two or more of the state categories shown in Figures 6, 7, 10, 11, and 12).

[0117] Incidentally, the higher the battery discharge current, the higher the battery temperature tends to be. Also, using the battery at high temperatures can accelerate battery degradation. For this reason, as mentioned above, if the battery 31 is used when the charge level is near 100% or near 0% and the temperature is far from room temperature, or if the discharge current is high, it is thought that battery degradation will be even faster. For this reason, classifying the state categories based on the relationship between the state of charge (SOC) and temperature-related information indicating the battery temperature or parameters that affect the battery temperature (e.g., battery discharge current), as shown in Figures 6 and 7, may be useful in understanding the degree of battery degradation.

[0118] Furthermore, the multiple state categories include a first category, which is at least distinguished by the battery charge level, and a second category, which is more likely to cause battery degradation compared to the battery state corresponding to the first category. It is preferable from the viewpoint of ease of evaluating the battery degradation status to make the range of charge levels corresponding to each second category narrower than the range of charge levels corresponding to the first category.

[0119] For example, the state categories may be distinguished by items other than the charge level of the battery 31, the discharge current of the battery 31, and the temperature of the battery 31. For example, Figure 13 is a table showing an example of the frequency of belonging to a state category indicated by the control mode in a hybrid vehicle equipped with an internal combustion engine and an electric motor as a driving power source. As shown in Figure 13, it is also possible to store the frequency of belonging to a control mode as state history information. That is, the one or more parameters that distinguish the state categories do not have to be the charge level of the battery 31, the discharge current of the battery 31, or the temperature of the battery 31, or they may include one or more of the charge level of the battery 31, the discharge current of the battery 31, and the temperature of the battery 31.

[0120] Figure 9 shows a histogram illustrating the frequency of belonging to each state category, defined by the temperature and state of charge (SOC) of the battery 31, but this is merely one example. For instance, the state history information displayed on the display of the information terminal device 60 could also be a histogram showing the frequency of belonging to a state category divided by a single parameter, as shown in Figure 14.

[0121] In the vehicle's electronic equipment, the CPU stores in memory 19b the time the battery 31 was used in the state corresponding to the state category (usage time per category) as the frequency with which the state of the battery 31 corresponding to the state category occurred. However, the frequency with which the state of the battery 31 corresponding to the state category occurred does not have to be counted in time. For example, the CPU may store in memory 19b the ratio of the usage time per category to the total usage time of the battery as the frequency with which the state of the battery 31 corresponding to the state category occurred. In other words, although the unit was time in the examples of Figures 6 and 7, the unit may be a percentage (%). In this case, the CPU in the vehicle's electronic equipment may also store the total usage time of the battery in memory. The total usage time of the battery may also be sent from the vehicle's electronic equipment to the server along with the state history information.

[0122] Furthermore, the frequency of belonging to a state category may be calculated by counting the number of times a battery belongs to a state category until it leaves that category, or it may be calculated by adding a value each time a battery continuously belongs to a state category for a predetermined period of time (e.g., 10 minutes). If a state category is expressed within a range of SOC, the number of times the SOC value at the start of battery charging or discharging belongs to that state category may be counted as the frequency information for that state category.

[0123] The various types of information sent from the mobile device to the server are not limited to those described in the above embodiments. For example, the various types of information sent to the server may not include some or all of the following: vehicle identification information (vehicle ID), user identification information (user ID), industry of use information, detection period information, battery usage time information, transmission date and time information, and location identification information. The various types of information sent to the server may also include other information such as the total number of charge cycles. The total charge / discharge amount and SOC may also be sent to the server.

[0124] In the above embodiment, the state history information indicating the state history of the battery 31 was stored as information indicating the cumulative time the battery 31 belonged to a predetermined state, but the method of storing the state history information is not limited to this. For example, time-series data of sensor detection values ​​(i.e., raw data, battery state information) may be stored in memory as state history information. In other words, the state history information stored in memory may be generated as frequency information from the battery state information, may be the battery state information itself, or may be information processed from the battery state information into a format other than frequency information.

[0125] In the above embodiment, the battery state information indicating the state of the battery 31 was exemplified as the charge level of the battery 31, the temperature of the battery 31, and the discharge current of the battery 31. However, the measurement method and calculation method for detecting these are not particularly limited. For example, the inverter device 22 may include a current sensor that detects the current input to the inverter device 22. In this case, the value detected by the current sensor of the inverter device 22 may be used as the discharge current for the battery 31.

[0126] Battery status information is not limited to the charge level of battery 31, the temperature of battery 31, or the discharge current of battery 31. Battery status information may not include some or all of the charge level of battery 31, the temperature of battery 31, or the discharge current of battery 31. For example, battery status information indicating the state of battery 31 may include information indicating the orientation of battery 31 (e.g., tilt), information indicating the acceleration of battery 31, or information indicating the geographical location of battery 31 (in other words, information indicating where the vehicle is moving). That is, sensors that detect information indicating the state of battery 31 (battery status information) may include a battery management unit, a temperature sensor, a current sensor, a gyroscope sensor, an acceleration sensor, or a GPS, ECU, etc.

[0127] The sensor that detects battery status information indicating the state of the battery 31 may be built into the battery pack or fixed to the vehicle body to which the battery pack is attached.

[0128] In steps S2 and S3 described in the above embodiment, the battery management unit 32 continuously output battery status information and battery identification information to the CAN20 while power was being supplied from the battery 31 to the electric motor 14. However, the battery management unit 32 does not have to continuously output battery status information and battery identification information to the CAN20. For example, the battery management unit 32 may output battery identification information to the CAN20 when the main switch for making the electric motorcycle 10 ready to run is turned on, and may not output battery identification information to the CAN20 until the main switch is turned off. Alternatively, for example, the battery management unit 32 may periodically output battery status information to the CAN20 while the main switch is on.

[0129] Furthermore, for example, the battery management unit 32 may output the status history information, which is frequency information as described above, to the CAN 20 instead of the battery status information. That is, the CPU 32a of the battery management unit 32 may generate status history information, which is frequency information, from the battery status information and output the generated status history information to the CAN 20. If the battery pack 30 is equipped with a communication circuit for communicating with a mobile terminal 40 or a server 50, the CPU 32a of the battery management unit 32 may generate status history information, which is frequency information, from the battery status information and transmit the generated status history information directly to the mobile terminal 40 or server 50 via the communication circuit.

[0130] Steps S8 and S9 described in the above embodiment can be executed on the mobile terminal 40 instead of the server 50. For example, after step S6, the mobile terminal 40 can store the received state history information, battery identification information, and vehicle identification information in memory 42, linking them together. In the mobile terminal 40, the CPU 41 can diagnose the state of the battery 31 corresponding to the battery identification information from the state history information stored in memory 42, which is linked to the same battery identification information. In other words, multiple battery packs 30 that have been installed in the mobile vehicle 10 owned by the user can be managed on the user's mobile terminal 40.

[0131] In the above embodiment, the CPU 19a of the meter device 19 transmitted vehicle identification information, along with status history information and battery identification information, to the mobile terminal 40 via the communication device 19d. However, vehicle identification information does not necessarily have to be sent from the equipment on the vehicle body 11 side to the mobile terminal 40 and the server 50. User identification information for identifying the user of the vehicle body may be sent from the equipment on the vehicle body 11 side to the mobile terminal 40 and the server 50 along with the status history information and battery identification information. User identification information for identifying the user of the vehicle body may be, for example, purchaser information of the vehicle body or user information of the vehicle body rented from a rental company.

[0132] The battery pack status history information aggregated in the server's memory can be used for various purposes. For example, the battery pack status history information aggregated in the server's memory can be used to determine the degree of battery degradation of battery pack 30, and can also be used by battery pack developers to optimize the durability conditions of the battery pack. For example, the battery pack status history information aggregated in the server's memory can be used to disclose the status of the battery pack to the user.

[0133] The functions of the elements disclosed herein can be performed using circuits or processing circuits, including general-purpose processors, dedicated processors, integrated circuits, ASICs (Application Specific Integrated Circuits), conventional circuits, or any combination thereof, configured or programmed to perform the disclosed functions. A processor is considered a processing circuit or circuit because it includes transistors and other circuits. In this disclosure, a circuit, unit, or means is hardware that performs the enumerated functions, or hardware programmed to perform the enumerated functions. The hardware may be hardware disclosed herein, or other known hardware that is programmed or configured to perform the enumerated functions. If the hardware is a processor, which is considered a type of circuit, then the circuit, means, or unit is a combination of hardware and software, and the software is used to configure the hardware or processor.

[0134] [Disclosure items] Each of the following items is a disclosure of a preferred embodiment.

[0135] [Item 1] A battery management method for managing multiple battery packs, each detachably mounted on the body of multiple mobile vehicles, using an external storage device, A processing circuit fixed to the vehicle body receives battery identification information for identifying the battery pack from the battery pack mounted on the vehicle body. The processing circuit stores the received battery identification information in a vehicle-side memory fixed to the vehicle body. The processing circuit stores state history information, which indicates the battery state history of the battery pack while it is mounted on the vehicle body, in the vehicle body memory, linked to the battery identification information. A battery management method comprising the processing circuit linking the state history information stored in the vehicle body memory with the battery identification information and transmitting it from the mobile device to the external storage device.

[0136] According to the above method, since the state history information is stored in the vehicle's memory, it is not necessary to store the state history information on the battery pack side. Therefore, it is possible to suppress the need to increase the memory capacity of the battery pack side, and thus keep the cost of the battery pack down.

[0137] Furthermore, the state history information stored in the vehicle's memory is linked to the battery identification information and sent to an external storage device. Therefore, even if the battery pack is installed in a different vehicle than the one it was previously installed in, the state history acquired while it was installed in the previous vehicle is stored in the external storage device, allowing for management of all vehicles in which it was previously installed, and making it easier to manage the battery pack's battery state history.

[0138] [Item 2] The battery management method according to item 1, wherein, after the transmission of the state history information to the external storage device is completed, the processing circuit erases part or all of the state history information from the vehicle-side memory.

[0139] According to the above method, it is easier to reduce the memory capacity of the vehicle body's memory.

[0140] [Item 3] The battery management method according to item 1 or 2, wherein the processing circuit transmits the state history information stored in the vehicle body memory wirelessly from the mobile device to the external storage device.

[0141] According to the above method, transmission to an external storage device is easier compared to wired communication. outside Transmit to the storage device You can, It is also acceptable to send it to an external storage device without going through a mobile device. stomach. External storage without going through a mobile device to If it has a communication circuit that can transmit, the driver can do so at a distance. Also outside It can communicate with the internal memory at all times. the law of nature, external storage device of It is easy to increase the frequency of sending messages. 。

[0142] [Item 4] The battery management method according to any one of items 1 to 3, wherein the processing circuit transmits the state history information stored in the vehicle body memory from the mobile body to the external storage device via a mobile terminal carried by the user of the mobile body.

[0143] Transfer When connecting from a moving object to an external storage device without going through a mobile terminal, the communication from the moving object to the base station is more complex than a short-range communication circuit that can communicate with a mobile terminal. high High communication performance is required. According to the above method, the configuration of the communication device installed on the mobile body can be easily simplified.

[0144] [Item 5] The battery management method according to any one of items 1 to 4, wherein the state history information is information relating to at least one of the battery's charge level, the battery's discharge current, and the battery's temperature.

[0145] According to the above method, it is easy to reduce state history information. Battery charge level, battery discharge current, and battery temperature degree , has a significant impact on representing the state history. Therefore, in addition to the battery charge level, battery discharge current, and battery temperature, others Use the information Rather few amount of information Battery degradation Easy to judge stomach.

[0146] [Item 6] The battery management method, before storing the state history information in the vehicle-side memory in association with the battery identification information, detects information related to the state of the battery using at least one sensor. The process further includes classifying the battery state into one of a predetermined number of state categories based on information detected by at least one of the sensors, The battery management method according to any one of items 1 to 5, wherein the processing circuit stores the state history information in association with the battery identification information in the vehicle-side memory, and includes storing the frequency at which the battery state corresponding to the state category occurred as state history information in the vehicle-side memory.

[0147] According to the method described above, by using frequency, it is easier to acquire the desired information as history and reduce the amount of information compared to simply accumulating the battery state as is.

[0148] [Item 7] The battery management method according to any one of items 1 to 6, further comprising transmitting the state history information stored in the vehicle body memory from the mobile device to the external storage device, linking it not only with the battery identification information but also with vehicle identification information for identifying the vehicle body or user identification information for identifying the user of the vehicle body.

[0149] According to the method described above, it is easy to analyze the battery status for each vehicle in which the battery is installed, and this information can be easily used as a history of the battery status.

[0150] [Item 8] A memory control device for a mobile device equipped with a battery pack, Memory and A communication interface capable of communicating with an external storage device, A processing circuit is provided, The aforementioned processing circuit is State history information indicating the battery state history of the battery pack while it is mounted on the mobile body is stored in the memory, linked to battery identification information for identifying the battery pack. The state history information stored in the memory is linked to the battery identification information and transmitted to the external storage device via the communication interface. A memory control device that, after the transmission of the state history information to the external storage device is completed, erases part or all of the transmitted state history information from the memory.

[0151] According to the above configuration, the memory capacity can be easily reduced by erasing the state history information in memory after sending the state history information to an external storage device.

[0152] Furthermore, in item 8, the memory may be memory fixed to the vehicle body (for example, memory in a vehicle control device, inverter device, meter device, etc.). Also, in item 8, the memory may be memory built into a battery pack (for example, memory in a battery management unit). Also, in item 8, the memory may be memory built into a portable device carried by the driver without being fixed to the vehicle body (for example, a smartphone). Also, in item 8, the memory may be memory built into an information acquisition device owned by a dealer or the like that acquires information from the vehicle body.

[0153] [Item 9] A vehicle body with a removable battery pack, A vehicle-side memory fixed to the vehicle body, A first communication interface capable of communicating with the battery pack mounted on the vehicle body, A second communication interface capable of communicating with an external storage device, A processing circuit is provided, The aforementioned processing circuit is The battery pack receives battery identification information for identifying the battery pack via the first communication interface. The received battery identification information is stored in the vehicle body's memory. State history information indicating the battery state history of the battery pack while it is installed in the vehicle body is stored in the vehicle body's memory, linked to the battery identification information. A mobile device that transmits the state history information stored in the vehicle body memory, linked with the battery identification information, to the external storage device via the second communication interface.

[0154] According to the above configuration, since the state history information is stored in the vehicle's memory, it is not necessary to store the state history information on the battery pack side. Therefore, it is possible to suppress the need to increase the memory capacity of the battery pack side, and thus the increase in the cost of the battery pack can be kept down.

[0155] Furthermore, the state history information stored in the vehicle's memory is linked to the battery identification information and sent to the external storage device. Therefore, even if the battery pack is installed in a different vehicle than the one it was previously installed in, the state history acquired while it was installed in the previous vehicle is stored in the external storage device, allowing for the management of the battery pack's state history.

[0156] [Item 10] A server comprising a communication interface capable of communicating with multiple mobile devices equipped with battery packs, memory, and processing circuitry, The aforementioned processing circuit is State history information, which indicates the history of the battery state of the battery pack while it is mounted on the mobile body and is linked to battery identification information for identifying the battery pack, is sequentially received via the communication interface as time changes. A server that aggregates and stores the sequentially received state history information in the memory, linking it with the battery identification information.

[0157] According to the above configuration, even if the battery pack is installed in a vehicle body different from the one it was previously installed in, the server has accumulated a history of the battery state acquired while it was installed in the previous vehicle body, so it is possible to manage the history of the battery state of the battery pack. [Explanation of Symbols]

[0158] 1: Battery Management System 10: Electric motorcycle (mobile object) 11: Vehicle body 14: Electric motor 19: Metering device 19a: CPU 19b: Memory 19c:Display unit 19d: Communication device 21: ECU 21a: CPU 21b: Memory 22: Inverter device 22a: CPU 22b: Memory 22c: Inverter circuit 23a: Vehicle-side power supply connector 23b: Vehicle-side communication connector 30: Battery Pack 30: Server 31: Battery 32: Battery Management Unit 32a:CPU 32b: Memory 33a: Battery-side power supply connector 33b: Battery-side communication connector 34: Voltage Sensor 35: Temperature sensor 36: Current Sensor 40: Mobile devices 41: CPU 42: Memory 43: Touchscreen 44: First communication device 45: Second communication device 50: Server 51: CPU 52: Memory 53: Communication device

Claims

1. A battery management method for managing multiple battery packs, each detachably mounted on the body of multiple mobile vehicles, using an external storage device, A processing circuit fixed to the vehicle body receives battery identification information for identifying the battery pack from the battery pack mounted on the vehicle body, The processing circuit stores the received battery identification information in a vehicle-side memory mounted on an external electrical component fixed to the vehicle body. The processing circuit stores state history information, which indicates the battery state history of the battery pack while it is mounted on the vehicle body, in the vehicle body memory, linked to the battery identification information. The processing circuit includes linking the state history information stored in the vehicle body memory with the battery identification information and transmitting it from the mobile device to the external storage device, The aforementioned external electrical equipment is an electrical equipment other than the battery pack mounted on the mobile body, and the battery management method includes a memory function and a function different from the memory function.

2. The battery management method according to claim 1, further comprising the processing circuit erasing part or all of the state history information from the vehicle-side memory after the transmission of the state history information to the external storage device has been completed.

3. The battery management method according to claim 1 or 2, wherein the state history information is information relating to at least one of the battery's charge level, the battery's discharge current, and the battery's temperature.

4. The battery management method includes detecting information related to the battery state using at least one sensor before storing the state history information in the vehicle-side memory in association with the battery identification information. The process further includes classifying the battery state into one of a predetermined number of state categories based on information detected by at least one of the sensors, The processing circuit storing the state history information in the vehicle-side memory in association with the battery identification information includes storing the battery usage time corresponding to each state category as state history information in the vehicle-side memory. The battery management method according to claim 1 or 2, wherein the usage time is the time the battery was used in the state of the battery corresponding to the state category.

5. A mobile body, A vehicle body with a removable battery pack, A vehicle-side memory mounted on an external electrical component fixed to the vehicle body, A first communication interface capable of communicating with the battery pack mounted on the vehicle body, A second communication interface capable of communicating with an external storage device, A processing circuit is provided, The aforementioned processing circuit is Receiving battery identification information for identifying the battery pack from the battery pack via the first communication interface, The received battery identification information is stored in the vehicle body's memory, The state history information, which indicates the battery state history of the battery pack while it is installed in the vehicle body, is stored in the vehicle body's memory, linked to the battery identification information. The system is configured to transmit the state history information stored in the vehicle body memory, linked with the battery identification information, to the external storage device via the second communication interface. The aforementioned external electrical components are electrical components other than the battery pack mounted on the mobile body, and the mobile body includes a memory function and a function different from the memory function.

6. Receiving the battery identification information, wherein when the battery pack is mounted on the vehicle body, the processing circuit receives from the battery pack the battery identification information of the battery pack and battery status information which is information indicating the state of the battery pack, The processing circuit includes generating state history information based on the battery state information received from the battery pack, which indicates the state history of the battery pack while it was mounted on the vehicle body. The battery management method according to claim 1 or 2, wherein the amount of data for the state history information is less than the amount of data for the battery state information.

7. The battery management method according to claim 1 or 2, wherein the state history information is stored in the vehicle body memory, and the processing circuit stores the state history information as overwritable data in a portion of the storage area of ​​the vehicle body memory.

8. Receiving the battery identification information, wherein when the battery pack is mounted on the vehicle body, the processing circuit receives from the battery pack the battery identification information of the battery pack and battery status information which is information indicating the state of the battery pack, The processing circuit generates state history information based on the battery state information received from the battery pack, which indicates the state history of the battery pack while it was mounted on the vehicle body. The state history information is stored in the vehicle body memory, and the processing circuit stores the generated state history information in the vehicle body memory, linked to the battery identification information. The battery management method according to claim 1 or 2, further comprising the processing circuit continuing to update the state history information stored in the vehicle body memory with the generated state history information until the timing for communication connection with the external storage device is reached.

9. The external electrical component of the pack includes, as a function different from the memory function, a control function for controlling an actuator or sensor provided on the vehicle body. The battery management method according to claim 1 or 2, wherein the control function includes one or more of the following: meter control, drive source control, brake control, suspension control, lamp control, radar control, camera control, and solenoid valve control.

10. The battery management method according to claim 1 or 2, wherein when the first battery pack, which is the battery pack mounted on the vehicle body, is changed to a second battery pack different from the first battery pack, the battery identification information and state history information of the second battery pack, in addition to the battery identification information and state history information of the first battery pack stored in the vehicle body memory, are linked together and stored in the vehicle body memory.

Images