Information processing apparatus, information processing system, and information processing method

Abstract

An information processing device that provides information about a battery device that can be installed in a vehicle. It determines whether first information required to track the location of the previous battery device has been registered in a designated management device. If the first information has been registered in the designated management device, it performs first processing required to provide second information about the previous battery device.

Description

[Technical Field]

[0001] This disclosure relates to vehicle technology. [Previous Technology]

[0002] Technology for providing information regarding batteries in electric vehicles is known. For example, Patent Document 1 discloses a system that determines the degree of degradation of the battery installed in a vehicle and notifies the user of the necessity for battery replacement. [Prior Art Documents] [Patent Documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2021-191159 [Summary of the Invention]

[0004] [Problem to be Solved by the Invention] The purpose of this disclosure is to facilitate the registration of information required for tracking batteries installed in vehicles. [Means for Solving the Problem]

[0005] One embodiment of the present disclosure is an information processing apparatus for providing information about a battery device that can be installed in a vehicle. It has a control unit for performing: determining whether first information required for tracking the location of the previous battery device has been registered in a predetermined management device; and, based on the condition that the first information has been registered in the predetermined management device, performing first processing required for providing second information about the previous battery device.

[0006] One embodiment of this disclosure is an information processing system comprising: a first information processing device for managing first information required to track the location of a battery device that can be installed in a vehicle; and a second information processing device for providing information about the battery device. The first information processing device performs the following: when the battery device is removed from the first vehicle, it accepts the registration of the first information for the battery device; the second information processing device performs the following: determining whether the first information corresponding to the battery device has been registered in the first information processing device; and, based on the condition that the first information has been registered in the first information processing device, performing first processing required to provide second information about the battery device.

[0007] One embodiment of the present disclosure is an information processing method, which is an information processing method performed by an information processing device for providing information about a battery device that can be installed in a vehicle. The method includes: determining whether first information required for tracking the location of a previous battery device has been registered in a predetermined management device; and, assuming that the first information has been registered in the predetermined management device, performing first processing required for providing second information about the previous battery device.

[0008] Furthermore, other examples include: the method executed by the aforementioned device, the program required to cause a computer to execute the method, or a computer-readable memory medium that non-temporarily stores the program. [Effects of the Invention]

[0009] If this disclosure is followed, it can facilitate the registration of information needed to track the batteries installed in vehicles.

Implementation Method

[0011] In recent years, electric vehicles (BEVs), plug-in hybrid electric vehicles (PHEVs), and other vehicles equipped with drive batteries that can run on electricity have been gradually increasing.

[0012] Once electric vehicles become widespread, the business of selling batteries salvaged from used cars is expected to become booming. However, if used car batteries are not properly recycled, they could harm the environment. Furthermore, even when batteries are recycled and installed in new vehicles, their value cannot be accurately assessed without using the correct evaluation methods specified by the vehicle manufacturer. To address these issues, it would be ideal for manufacturers (vehicle manufacturers, etc.) to be able to track batteries removed from vehicles. However, currently, once batteries are separated from vehicles, it is difficult for vehicle manufacturers to track their whereabouts. The information processing device disclosed herein aims to solve this problem.

[0013] One aspect of this disclosure is an information processing apparatus for providing information about a battery device that can be installed in a vehicle. Specifically, it has a control unit for performing: determining whether first information required for tracking the location of a previous battery device has been registered in a designated management device; and, based on the condition that the first information has been registered in the designated management device, performing first processing required for providing second information about the previous battery device.

[0014] A battery device is a packaged battery of an electric vehicle. In addition to the battery itself, a battery device may also include: a control computer, a vehicle connection interface, a memory device, etc.

[0015] The information processing device is, for example, a device that reads information from a battery device by connecting to the battery device. Alternatively, the information processing device may also be, for example, a computer (battery ECU) installed in the battery device. The control unit of the information processing device determines whether the first information corresponding to the target battery device has been registered in a designated management device. The so-called first information is information needed to track the location of the battery device, typically including information about the company that removed the battery device from the vehicle, the purpose of the removal, and the recipient after removal.

[0016] The first information, typically, is registered to a designated management device (e.g., a central server for managing battery information) by the operator at the point when the battery device is removed from the vehicle. Furthermore, the control unit performs the first processing necessary to provide second information about the battery device, provided that the first information has been registered in the designated management device. Preferably, the control unit does not perform the first processing necessary to provide second information if the first information has not been registered in the designated management device. In this case, if the first information has not been registered in the management device when the battery device is removed from the vehicle, the second information about the battery device cannot be obtained.

[0017] The second information that is restricted from being obtained through the control unit includes, for example, the battery device's usage history, degradation status, and self-diagnostic results, preferably information needed to evaluate the battery device. If such information access restrictions are implemented on the battery device, its market value will decrease. Based on the aforementioned configuration, when the battery device is disassembled, the aforementioned businesses can be motivated to register the first information, thus facilitating the tracking of the battery device.

[0018] The information processing device is a device capable of communicating with the computer (battery ECU) of the battery device, and may also be, for example, a diagnostic machine or the like, used to read information. In this case, the first processing is the process of reading second information from the battery ECU or the like. Alternatively, the information processing device may be, for example, the computer (battery ECU) itself of the battery device. In this case, the first processing is the process of reading second information from the memory device of the battery device.

[0019] Furthermore, the control system can also perform second processing required to provide third information that differs from the second information. That is, the control system can provide third information even when access to the second information is restricted. The third information is preferably information necessary for the vehicle to move or information necessary to ensure safety. Based on the aforementioned configuration, while maintaining the safety performance of a vehicle equipped with a recyclable battery, information necessary for determining market prices, for example, can be made inaccessible. This provides an incentive for businesses, such as those mentioned above, to register the first information when the battery device is removed.

[0020] Furthermore, the control unit can also detect and memorize the combination of the battery device and the vehicle on which the battery device is installed. Furthermore, the control unit can also perform the first processing of the prior information regardless of whether the prior information is registered when the known combination is detected.

[0021] Hereinafter, specific embodiments of this disclosure will be described based on the drawings. Unless otherwise specified, the hardware configuration, module configuration, functional configuration, etc., described in each embodiment are not intended to limit the scope of the disclosed technology to these contents.

[0022] [First Embodiment] An overview of the battery management system described in the first embodiment will be described with reference to FIG1. ​​The battery management system described in this embodiment is a system that manages information about a battery pack 4 designed for use in an electric vehicle via a server device 1. The battery pack 4 is a drive battery for the vehicle and is a unit with an attached control computer (ECU). In the description of this embodiment, the battery pack is also referred to as a "battery device" or simply a "battery". The battery pack is removed from the original vehicle and can be reused, for example, by being installed in other electric vehicles or for applications such as household batteries.

[0023] Server device 1 is a computer that collects and manages information about the battery pack installed in the vehicle. Server device 1 may also be a device used by an automobile manufacturer that manufactures electric vehicles.

[0024] When the server device 1 is used by an automobile manufacturer, the server device 1 can also manage information about the battery pack installed in the company's automobiles. For example, the server device 1 can periodically collect information about the vehicle, such as vehicle identification elements, location information, speed, and distance traveled, and associate this information with information about the battery pack 4 and memorize it. In this way, the server device 1 can keep track of the latest status of the vehicle and the battery pack 4.

[0025] The diagnostic device 3 is a device used to read various information from the battery pack 4. The diagnostic device 3, by connecting to the battery pack 4, can, for example, perform self-diagnosis on the battery pack 4 and obtain the results. Furthermore, the diagnostic device 3 can read various information possessed by the battery pack 4. This information can also be generated in response to the execution of self-diagnosis, or can be generated autonomously and periodically by the battery pack 4.

[0026] In the following description, the information provided by the battery pack 4 is referred to as "status information". The status information is stored in a memory device of the battery pack 4 and can be read by the diagnostic device 3. When the battery pack 4 is installed in a vehicle, the vehicle's ECU can also read the status information.

[0027] Examples of status information include the driving history, charge / discharge cycles, SoC (State of Charge), and SoH (State of Health) of a vehicle equipped with battery pack 4. The status information includes: information necessary for the vehicle's operation (such as SoC, or information about voltage, current, power, etc.), information necessary for ensuring safety (such as temperature information or current safety thresholds), and information needed to evaluate the value of battery pack 4 (such as SoH or charge / discharge cycles).

[0028] Generally, the battery pack 4 is used while it is attached to the vehicle. In this state, the automaker can track its location through the communication device installed in the vehicle. However, if the battery pack 4 is removed from the vehicle, tracking the battery pack, which does not have a communication device, becomes difficult.

[0029] Therefore, in this embodiment, the server device 1 obtains and manages the information required for tracking the battery pack 4 ("first information" in this disclosure; hereinafter referred to as tracking information) from the terminal (business terminal 2) owned by the business that removed the battery pack at the time when the battery pack 4 is removed from the vehicle.

[0030] Furthermore, in this embodiment, when the diagnostic device 3 is connected to the disassembled battery pack 4, a determination process is performed to determine whether the reading of status information is permitted. Specifically, the battery pack 4 connected to the diagnostic device 3 queries the server device 1 for the existence of tracking information about the device. If the tracking information is not registered to the server device 1, the provision of at least a portion of the status information ("second information" in this disclosure) is refused. If the tracking information has been registered to the server device 1, all the status information can be read.

[0031] Based on the aforementioned configuration, when the operator removes the battery pack from the vehicle, there will be an incentive to register the tracking information to the server device 1. This facilitates the registration of tracking information and makes it easier to track the battery pack removed from the vehicle.

[0032] [Hardware Configuration] Next, the hardware configuration of each device constituting the system will be explained. First, the constituent elements of the server device 1 will be explained. Figure 2 is a schematic diagram of an example of the hardware configuration of the server device 1.

[0033] The server device 1 can be configured as a computer having a processor (CPU, GPU, etc.), main memory (RAM, ROM, etc.), and auxiliary memory (EPROM, hard disk drive, removable media, etc.). The auxiliary memory stores the operating system (OS), various programs, various forms, etc. By executing the programs stored therein, the various functions (software modules) that meet the predetermined purpose can be realized, as described later. However, some or all of the functions can also be realized as hardware modules using hardware circuits such as ASICs, FPGAs, etc.

[0034] The server device 1 is configured to include a control unit 11, a memory unit 12, and a communication unit 13.

[0035] The control unit 11 is a computing unit that implements various functions of the vehicle-mounted device 10 by executing a predetermined program. The control unit 11 can be implemented by a hardware processor such as a CPU. Furthermore, the control unit 11 can also be configured to include RAM, ROM (Read Only Memory), cache memory, etc.

[0036] The memory unit 12 is a means of storing information and is configured to include a main memory device and an auxiliary memory device. The main memory device is a memory that stores the program executed by the control unit 11 or the data used by the control program. The auxiliary memory device is a device that stores the program executed by the control unit 11 or the data used by the control program. The auxiliary memory device may also encapsulate the program executed by the control unit 11 into an application program and store it. Furthermore, it may also store the operating system required to execute these applications. The program stored in the auxiliary memory device is loaded into the main memory device and executed by the control unit 11 to perform the processing described below.

[0037] The main memory device may also contain RAM (Random Access Memory) or ROM (Read Only Memory). Furthermore, the auxiliary memory device may also contain EPROM (Erasable Programmable ROM) or a hard disk drive (HDD). Moreover, the auxiliary memory device may also contain removable media, i.e., portable recording media.

[0038] The communication unit 13 is a communication interface required for connecting the server device 1 to the network. The communication unit 13 may be a wired communication interface or a wireless communication interface.

[0039] Next, the constituent elements of the business terminal 2 will be explained. Figure 3 is a schematic diagram of one example of the hardware configuration of the business terminal 2. The business terminal 2, like the server device 1, can be configured as a computer having a processor (CPU, GPU, etc.), main memory (RAM, ROM, etc.), and auxiliary memory (EPROM, hard disk drive, removable media, etc.).

[0040] The business terminal 2 is configured to include a control unit 21, a memory unit 22, a communication unit 23, and an input / output unit 24.

[0041] The control unit 21 is a computing unit that executes a predetermined program to realize various functions of the business terminal 2. The control unit 21 can be implemented by a hardware processor such as a CPU. Furthermore, the control unit 21 can also be configured to include RAM, ROM (Read Only Memory), cache memory, etc.

[0042] The memory unit 22 is a means of storing information and is constructed from a memory medium such as RAM, magnetic disk, or flash memory. The memory unit 22 stores the program executed by the control unit 21 and the data used by the program.

[0043] The communication unit 23 is a communication interface required to connect the operator terminal 2 to the network. The communication unit 23 may be a wired communication interface or a wireless communication interface.

[0044] The input / output unit 24 is a unit that receives input from the operator of the business terminal 2 and provides information to the operator. Specifically, the input / output unit 24 is composed of a touch panel and its control means, and a liquid crystal display and its control means. In this embodiment, the touch panel and the liquid crystal display are composed of a single touch panel display. In addition, the input / output unit 24 may also include a hardware interface such as a keyboard or mouse.

[0045] Next, the diagnostic device 3 will be described. Figure 4 is a schematic diagram of one example of the hardware configuration of the diagnostic device 3. The diagnostic device 3, like the server device 1, can be configured as a computer having a processor (CPU, GPU, etc.), main memory (RAM, ROM, etc.), and auxiliary memory (EPROM, hard disk drive, removable media, etc.).

[0046] The diagnostic device 3 is configured to include: a control unit 31, a memory unit 32, a communication unit 33, a CAN communication unit 34, and an input / output unit 35.

[0047] The control unit 31 is a calculation unit that implements various functions of the diagnostic device 3 by executing a predetermined program. The control unit 31 can be implemented by, for example, a hardware processor such as a CPU. Furthermore, the control unit 31 can also be configured to include RAM, ROM (Read Only Memory), cache memory, etc.

[0048] The memory unit 32 is a means of storing information and is constructed from a memory medium such as RAM, magnetic disk, or flash memory. The memory unit 32 stores the program executed by the control unit 31 and the data used by the program.

[0049] The communication unit 33 is a communication interface required to connect the diagnostic device 3 to the network. The communication unit 33 can be a wired communication interface or a wireless communication interface. By connecting the diagnostic device 3 to the network through the communication unit 33, the diagnostic device 3 and the server device 1 can communicate.

[0050] The CAN communication unit 34 is an interface required for connecting the diagnostic device 3 and the battery pack 4. In this embodiment, the diagnostic device 3 and the battery pack 4 communicate using an in-vehicle network specification (e.g., Controller Area Network, hereinafter referred to as "CAN") adopted in vehicles. The CAN communication unit 34 may also be a CAN interface.

[0051] Furthermore, when the battery pack 4 is installed in a vehicle, the diagnostic device 3 can also be connected to the battery pack 4 via the vehicle. In this case, by connecting the diagnostic device 3 to the vehicle's network port, the diagnostic device 3 and the battery pack 4 can communicate. Alternatively, the diagnostic device 3 and the battery pack 4 can also be directly connected. In this case, for example, their respective CAN interfaces can be connected to each other via a cable. Thus, the battery pack 4 removed from the vehicle can also be connected to the diagnostic device 3.

[0052] The input / output unit 35 is a unit that receives input from the operator of the diagnostic device 3 and provides information to the operator. Specifically, the input / output unit 35 is composed of a touch panel and its control means, and a liquid crystal display and its control means. In this embodiment, the touch panel and liquid crystal display are composed of a single touch panel display. In addition, the input / output unit 35 may also include a hardware interface such as a keyboard or mouse.

[0053] Next, the battery pack 4 will be described. Figure 5 is a schematic diagram of one example of the hardware configuration of the battery pack 4. The battery pack 4 is a unit consisting of a battery body (battery 44) such as a lithium-ion battery, with an additional computer (ECU 41), a CAN communication unit 42, and a memory unit 43 for controlling the charging and discharging of the battery.

[0054] ECU41 works in conjunction with the vehicle's ECU to control the charging and discharging of the battery. Furthermore, ECU41 can read and provide stored status information in response to external requests. This status information includes, for example, information necessary for evaluating the battery pack 4, such as the number of charge / discharge cycles, as well as information essential for vehicle operation, such as the battery state of charge.

[0055] Status information is required not only by the diagnostic device 3, but also by the ECU of the vehicle in which the battery pack 4 is installed. For example, information necessary for vehicle operation (such as battery charge) or information necessary for safety management (such as temperature information) is also part of the status information.

[0056] The diagnostic device 3 requests information (such as SOH or charge / discharge cycles) needed to evaluate the battery pack 4 as status information. In this embodiment, when the ECU 41 requests status information from the diagnostic device 3, the ECU 41 checks the server device 1 for the presence or absence of tracking information through the diagnostic device 3. If the presence of tracking information can be confirmed, the ECU 41 provides status information to the diagnostic device 3. If the presence of tracking information cannot be confirmed, the ECU 41 refuses to provide status information.

[0057] Furthermore, when there is a requirement to provide status information necessary for the vehicle's operation or for safety management ("Third Information" in this disclosure), the ECU41 provides it unconditionally. The Third Information does not include the aforementioned Second Information.

[0058] The CAN communication unit 42 is an interface used to connect the battery pack 4 to the vehicle or the diagnostic device 3. In addition to being used for direct connection with the diagnostic device 3, the CAN communication unit 42 is also used for communication with the vehicle. When the battery pack 4 is mounted in a vehicle, the CAN communication unit 42 connects to the interface on the vehicle side. In this case, the battery pack 4 and the diagnostic device 3 can communicate via the vehicle's network.

[0059] The memory unit 43 is a means of storing information and is constructed from a memory medium such as RAM, magnetic disk, or flash memory. The memory unit 43 stores the program executed by the ECU 41 and the data used by the program.

[0060] [Software Configuration] Next, the software configuration of each device constituting the system will be described. Figure 6 is a schematic diagram of the software configuration of the server device 1 described in this embodiment.

[0061] In this embodiment, the control unit 11 of the server device 1 is configured with two software modules: an information registration unit 111 and an information provision unit 112. Each software module can also be implemented by executing the program stored in the memory unit 12 (described later) through the control unit 11 (CPU, etc.). The information processing executed by the software modules is synonymous with the information processing executed by the control unit 11 (CPU, etc.).

[0062] The information registration unit 111 responds to a request from the business terminal 2 and obtains information (tracking information) about the specified battery pack from the business terminal 2. As mentioned above, the business that removes the battery pack 4 from the diagnostic device 3 uses the business terminal 2 to send the information required to track the battery pack 4 to the server device 1. The information registration unit 111 receives this information and stores it in the memory unit 12 (tracking information table). In addition, there may be cases where a record of the target battery pack already exists in the tracking information table stored in the memory unit 12. In this case, the information registration unit 111 can also generate a new record in the tracking information table based on the received information.

[0063] Figure 7 is an example of a tracking information table. As shown, the tracking information table contains: the ID (battery ID) required for the automaker to uniquely identify the battery, the battery model, the battery removal date, and information about the owner of the battery at the time of removal. Furthermore, the tracking information table may also contain the purpose of battery removal or the intended recipient of the battery. By referring to the tracking information table, for example, the intended recipient of the battery can be identified, thereby obtaining the information needed to estimate where the battery is currently located.

[0064] The information providing unit 112 responds to queries sent from the diagnostic device 3 or the battery pack 4 by determining whether a record corresponding to the designated battery pack exists in the tracking information table stored in the memory unit 12. For example, in the example of Figure 7, when a query is received from a battery pack with the battery ID "B001", the information providing unit 112 replies with the message "A record of tracking information for the designated battery pack already exists".

[0065] The memory unit 12 stores the aforementioned tracking information table.

[0066] Next, the software configuration of the business terminal 2 will be described. Figure 8 is a schematic diagram of the software configuration of the business terminal 2 described in this embodiment.

[0067] The control unit 21 of the operator terminal 2 is configured as a functional module with a registration unit 211. This functional module can also be implemented by the CPU executing a pre-memorized program. The registration unit 211 acquires tracking information about the target battery pack 4 through the input / output unit 24 and sends the acquired tracking information as battery information to the server device 1. For example, the registration unit 211 accepts input from the operator for information such as the ID (battery ID) required to identify the target battery pack, the battery model, the battery removal date, and the owner of the battery at the time of removal, and sends this information to the server device 1. Furthermore, if the target for reuse or transfer of the removed battery pack is known, this information can also be included in the tracking information.

[0068] Next, the software configuration of the diagnostic device 3 will be described. Figure 9 is a schematic diagram of the software configuration of the diagnostic device 3 described in this embodiment.

[0069] The control unit 31 of the diagnostic device 3 is configured as a functional module with an information acquisition unit 311. This functional module can also be implemented by the CPU executing a pre-memorized program. The information acquisition unit 311 acquires and outputs status information from the battery pack 4 based on the operator's instructions. For example, the information acquisition unit 311 instructs the connected battery pack 4 to read the status information and outputs the status information sent from the battery pack 4 through the input / output unit 35. In addition, the information acquisition unit 311 can also instruct the battery pack 4 to perform self-diagnosis. If the status information is generated in response to the execution of self-diagnosis, the status information can also be acquired after the self-diagnosis is completed.

[0070] Next, the software configuration of the battery pack 4 will be described. Figure 10 is a schematic diagram of the software configuration of the battery pack 4 as described in this embodiment.

[0071] The ECU 41 of the battery pack 4 is composed of two functional modules: a management unit 411 and an information provision unit 412. These functional modules can also be implemented by the CPU executing a program that has been memorized.

[0072] The management unit 411 works in conjunction with the ECU on the vehicle side to control the charging and discharging of the battery. The management unit 411 can also periodically acquire information about the battery and store it as status information in the memory unit 43. Examples of battery information include: the driving distance of the vehicle to which the battery pack 4 is mounted, the number of charge / discharge cycles of the battery 44, the temperature information of the battery 44, the maximum output information of the battery 44, and the maximum capacity information of the battery 44. Furthermore, the management unit 411 is configured to perform incidental functions such as battery self-diagnosis. Through self-diagnosis, for example, the battery's State of Health (SoH) can be calculated. The diagnostic results can also be stored in the memory unit 43 as part of the status information.

[0073] The information providing unit 412 reads out and provides the state information stored in the memory unit 43 based on the requests received from the outside.

[0074] The request for status information can be received from the diagnostic device 3 or from the ECU of the vehicle. When the request for status information necessary for driving or for safety management is received from the ECU of the vehicle, the information providing unit 412 unconditionally provides such status information.

[0075] When the information providing unit 412 receives a request for status information from the diagnostic device 3, the information providing unit 412 provides the status information on the condition that the tracking information corresponding to the self-device has been registered to the server device 1. Specifically, the information providing unit 412 sends data to the server device 1 through the diagnostic device 3 to query whether the tracking information corresponding to the self-device has been registered.

[0076] The information providing unit 412 receives the response sent from the server device 1 in response to a query. For example, if the response indicates that "the tracking information for the requested battery pack does not exist," the information providing unit 412 may refuse to provide the requested status information or provide only a portion of the requested status information. If there is a restriction on providing only a portion of the status information, the information providing unit 412 may also make a determination based on the information stored in the memory unit 43.

[0077] Furthermore, the configurations shown in Figures 2-6 and 8-10 are examples, and all or part of the functions shown can be executed using specially designed circuits. Also, programs can be memorized and executed by a combination of main memory devices and auxiliary memory devices other than those shown in the figures.

[0078] Next, the processing performed by each device included in the system will be explained. Figure 11 is a flowchart of the process by which server device 1 obtains information about a battery pack 4 that has been removed from a vehicle from operator terminal 2. The processing shown in the figure is executed at the point in time when the battery pack 4 is removed from the vehicle. This processing can also be started by operating operator terminal 2 owned by the operator who removed the battery pack 4.

[0079] First, in step S11, the operator terminal 2 accepts the input of tracking information regarding the battery pack of the object. The tracking information, as shown in Figure 7, may also include: an identification element used to uniquely identify the battery, the operator performing the disassembly, the original owner, the purpose of the disassembly, etc. Furthermore, if the battery has already been disassembled, the disassembly date or the transfer target may also be included in the tracking information. The input tracking information is then sent to the server device 1.

[0080] In step S12, the server device 1 (information registration unit 111) stores the received tracking information in the memory unit 12 (tracking information table). For example, the information registration unit 111 generates the record corresponding to the received tracking information and adds it to the tracking information table.

[0081] Next, we will explain the process performed when status information is read from the battery pack 4 via the diagnostic device 3. Figure 12 is a flowchart of an example of the process performed when status information is obtained from the battery pack 4 via the diagnostic device 3.

[0082] Once the diagnostic device 3 is connected to the battery pack 4, the ECU 41 of the battery pack 4 and the diagnostic device 3 become communicable. In this way, the ECU 41 recognizes that the device has been installed in the diagnostic device 3 (step S21).

[0083] In step S22, the diagnostic device 3 accepts the instruction to read the status information of the connected battery pack 4. The diagnostic device 3 generates the data (providing request) for the requested status information and sends it to the battery pack 4.

[0084] Upon receiving the status information request, ECU41 generates the necessary data (step S23) to query server device 1 whether the device's tracking information has been registered. The query will include the battery pack identification element (battery ID). The query is sent to server device 1 via diagnostic device 3.

[0085] Upon receiving the query, the server device 1 (information providing unit 112) uses the battery ID included in the query as the search key to search the tracking information table and extracts the matching records (step S24). If more than one record matching the battery ID is extracted, the server device 1 generates a response indicating that the battery involved in the query has been registered (positive response) and sends it to the diagnostic device 3. If no record matching the battery ID exists, the server device 1 generates a response indicating that the battery involved in the query has not been registered (negative response) and sends it to the diagnostic device 3. The diagnostic device 3 forwards the received response to the battery pack 4 (ECU 41).

[0086] In step S25, the battery pack 4 (ECU 41) determines the content of the response. If the response is negative, the battery pack 4 (ECU 41) sends information indicating that it cannot provide status information (response rejection) to the diagnostic device 3. If the response from the server device 1 is positive, the process proceeds to step S26, where the ECU 41 reads the determined status information from the memory unit 43.

[0087] Furthermore, ECU41 may also refuse to read status information if the query fails or if no response is received from server device 1. That is, ECU41 may also refuse to provide status information if it does not receive a positive response from server device 1 within a predetermined period. The status information is output from diagnostic device 3 and provided to the device operator (step S27).

[0088] As explained above, in the battery management system described in this embodiment, when the managed battery pack is connected to the diagnostic device 3, battery pack authentication processing is performed. Furthermore, if the information required for tracking the battery pack (tracking information) is not registered to the server device 1, reading the status information of the battery pack is restricted. Battery packs with restricted status information reading have a lower market value compared to battery packs without such restriction. This creates an incentive to register tracking information when the battery pack is removed, making battery tracking by vehicle manufacturers and others easier. Alternatively, even if status information reading is restricted, the restriction can be lifted by registering the tracking information afterwards. This achieves the goal of enabling battery pack tracking.

[0089] [Second Embodiment] In the first embodiment, the query to the server device 1 is performed by the ECU 41 of the battery pack 4. On the other hand, the query to the server device 1 can also be performed by the diagnostic device 3. The second embodiment is an embodiment in which the diagnostic device 3 performs the query to the server device 1 and determines whether the status information can be provided.

[0090] Figure 13 is a flowchart illustrating an example of the processing performed when status information is obtained from the battery pack 4 via the diagnostic device 3. The steps shown by the dashed lines are the same as in the first embodiment.

[0091] Once the diagnostic device 3 is connected to the battery pack 4, the ECU 41 of the battery pack 4 and the diagnostic device 3 become communicable. Here, the ECU 41 recognizes that the device has been installed in the diagnostic device 3 (step S21). In step S22, the diagnostic device 3 accepts the instruction to read the status information of the connected battery pack 4.

[0092] In the diagnostic device 3, once an instruction to read out status information is made, the diagnostic device 3 generates a query to confirm with the server device 1 whether the tracking information of the battery pack 4 has been registered (step S23A). The query contains the battery pack's identification element (battery ID). The query is sent to the server device 1.

[0093] The server device 1 (information providing unit 112) that receives the query generates an affirmative or negative response by means of the same process as step S24 in the first embodiment, and sends it to the diagnostic device 3.

[0094] In step S25A, the diagnostic device 3 determines the content of the response. If the response is negative, the process ends. If the response is positive, the diagnostic device 3 sends a request to the battery pack 4, and in response, the battery pack 4 reads out its status information (step S26). The status information is output from the diagnostic device 3 and provided to the device operator (step S27).

[0095] Thus, part of the processing performed by the battery pack 4 in the first embodiment can be performed by the diagnostic device 3.

[0096] [Third Embodiment] In the first embodiment, the battery pack 4 queries the server device 1 every time it receives a request. However, if the battery pack 4 is mounted in a vehicle and the combination of the vehicle and the battery pack remains unchanged, there may be cases where the query to the server device 1 can be omitted. In the third embodiment, the battery pack 4 memorizes the combination of the vehicle and the server device, and omits the query to the server device 1 when the combination remains unchanged.

[0097] Figure 14 is a flowchart illustrating an example of the processing performed when status information is obtained from the battery pack 4 via the diagnostic device 3. The steps shown by the dashed lines are the same as in the first embodiment.

[0098] In the third embodiment, after reading the status information in step S26, the battery pack 4 performs the step of storing the vehicle's identification element (e.g., the vehicle ECU's identification element) in the memory unit 43 (step S32). This step can be described as the step in which the battery pack 4 establishes a connection between the device and the vehicle and stores the information. Furthermore, this step is omitted when the battery pack 4 is not installed in the vehicle.

[0099] Furthermore, in the third embodiment, the battery pack 4 executes step S31 at the time point when it receives the request.

[0100] In step S31, the battery pack 4 determines whether the identification element of the vehicle currently being mounted has been stored in the memory unit 43. For example, if the battery pack 4 is not mounted on a vehicle (e.g., communication with the vehicle's ECU is not established), or if the identification element of the vehicle currently mounted on the battery pack 4 is different from that stored in step S32, this step will become a negative determination. If the identification element of the vehicle mounted on the battery pack 4 is the same as that stored in step S32, this step will become a positive determination. A positive determination in this step means that the combination of the battery pack 4 and the vehicle has not changed since the last readout of the status information. In this case, the battery pack 4 skips the query to the server device 1 and performs the readout of the status information. If a negative determination occurs in this step, the battery pack 4 queries the server device 1 using the method described above.

[0101] (Modification of the third embodiment) In the third embodiment, the battery pack 4 stores information indicating the combination of the battery pack 4 and the vehicle to which it is mounted. On the other hand, this information can also be stored by the diagnostic device 3.

[0102] Figure 15 is a flowchart of an example of the process performed when status information is obtained from the battery pack 4 by the diagnostic device 3. The steps shown by the dashed lines are the same as in the second embodiment.

[0103] In this modified example, after providing status information in step S27, the diagnostic device 3 performs the step of storing the combination of the vehicle's identification element (e.g., the vehicle ECU's identification element) and the battery pack 4's identification element (e.g., the ECU 41's identification element) in the memory unit 32 (step S34). Furthermore, this step is omitted when the battery pack 4 is not installed in the vehicle.

[0104] Furthermore, in this modified example, the diagnostic device 3 executes step S33 at the point in time when the requested status information is read.

[0105] In step S33, the diagnostic device 3 determines whether the combination of the identification element of the currently connected battery pack 4 and the vehicle identification element has been memorized in the memory unit 43. For example, if the battery pack 4 and the diagnostic device 3 are directly connected, or if the combination of the identification element of the battery pack 4 and the vehicle identification element is different from that memorized in step S34, this step becomes a negative determination. If the combination of the identification element of the battery pack 4 and the vehicle identification element is the same as that memorized in step S34, then this step becomes a positive determination. A positive determination here means that the combination of the battery pack 4 and the vehicle has not changed since the last readout of the status information. In this case, the diagnostic device 3 omits the query to the server device 1 and performs the readout of the status information. If a negative determination is made in this step, the diagnostic device 3 queries the server device 1 using the method described above.

[0106] (Modified Example) The above-described implementation is only one example. This disclosure can be implemented with appropriate modifications without departing from its essence. For example, the treatments or methods described in this disclosure can be freely combined and implemented as long as no technical contradictions occur.

[0107] Furthermore, while examples of the status information being stored in the battery pack 4 have been described in various embodiments, it is also possible to consider a scenario where the status information is collected and managed by the server device 1. In this case, the diagnostic device 3 (or the operator terminal 2) requests the given status information of the battery pack 4 from the server device 1. In this case, the server device 1 determines whether the tracking information of the specified battery pack 4 has been stored in a designated database, and if it has been stored, it can also provide the requested status information.

[0108] Figure 16 is a flowchart illustrating an example of the processing performed when status information is obtained from server device 1 via operator terminal 2. The steps shown by the dashed lines are the same as in the second embodiment. In this variation, instead of diagnostic device 3, operator terminal 2 generates and sends a query to server device 1 (steps S22-S23A). Server device 1 extracts the tracking information through the same processing as in step S24.

[0109] In step S41, server device 1 determines whether the tracking information for the designated battery pack 4 has been registered in the tracking information table. If it has been registered, the process proceeds to step S42, where server device 1 retrieves the status information for the designated battery pack 4 from a designated database and sends it to the operator terminal 2. The operator terminal 2 outputs the retrieved status information (step S27). If the tracking information for the designated battery pack 4 has not been registered in the tracking information table, the process ends. Thus, the status information may not be stored in the battery pack 4, but rather in server device 1. In this case, the "information processing device" and the "designated management device" in this disclosure both become server device 1.

[0110] Furthermore, a process described as being performed by one device can also be performed by multiple devices. Alternatively, a process described as being performed by different devices can also be performed by one device. In a computer system, the hardware configuration (server configuration) by which each function is implemented can be flexibly changed.

[0111] This disclosure can also be implemented by supplying a computer program that implements the functions described in the above embodiments to a computer, whereby one or more processors of the computer read and execute the program. Such a computer program can also be provided to a computer via a non-transitory computer-readable memory medium that can be connected to a computer's system bus, or via a network. Non-transitory computer-readable memory media includes, for example, any type of disk such as a floppy disk (registered trademark), hard disk drive (HDD), optical disk (CD-ROM, DVD, Blu-ray disc, etc.), read-only memory (ROM), random access memory (RAM), EPROM, EEPROM, magnetic cards, flash memory, optical cards, and any type of media suitable for storing electronic commands. [Simplified Explanation of the Diagram]

[0010] [Figure 1] Overview diagram of the battery management system according to the first embodiment. [Figure 2] Hardware configuration diagram of the server device according to the first embodiment. [Figure 3] Hardware configuration diagram of the business terminal according to the first embodiment. [Figure 4] Hardware configuration diagram of the diagnostic device according to the first embodiment. [Figure 5] Hardware configuration diagram of the battery pack according to the first embodiment. [Figure 6] Software configuration diagram of the server device according to the first embodiment. [Figure 7] An example of tracking information stored in the server device. [Figure 8] Software configuration diagram of the business terminal according to the first embodiment. [Figure 9] Software configuration diagram of the diagnostic device according to the first embodiment. [Figure 10] Software configuration diagram of the battery pack according to the first embodiment. [Figure 11] Flowchart of the process for processing tracking information registered on the server device. [Figure 12] First flowchart of the process executed when status information is requested. [Figure 13] Second flowchart of the process executed when status information is requested. [Figure 14] Third flowchart of the process executed when status information is requested. [Figure 15] Fourth procedure diagram of the process executed when a status information request is made. [Figure 16] Fifth procedure diagram of the process executed when a status information request is made.

Claims

1. An information processing apparatus for providing information about a battery device that can be installed in a vehicle, comprising a control unit that performs the following steps: determining whether first information required for tracking the location of a previous battery device has been registered in a designated management device; if the first information has been registered in the designated management device, performing first processing required for providing second information about the previous battery device; detecting and memorizing a combination of the previous battery device and the vehicle in which the previous battery device is installed; and performing the first processing of the previous information regardless of whether the first information of the previous information is registered in the designated management device when a known combination is detected.

2. The information processing apparatus as described in claim 1, wherein, The first processing step is the process of reading the second information from the predetermined memory device.

3. The information processing apparatus as described in claim 2, wherein, The memory device mentioned above refers to the memory device possessed by the battery device mentioned above.

4. The information processing apparatus as described in claim 1, wherein, The aforementioned control unit performs second processing to provide the third information that differs from the second information mentioned above.

5. The information processing apparatus as described in claim 4, wherein, The third piece of information in the foregoing contains the information necessary for the vehicle in the foregoing to move.

6. The information processing apparatus as described in claim 1, wherein, The second piece of information in the foregoing section contains information regarding the deterioration status of the battery device mentioned above.

7. An information processing system comprising: a first information processing unit for managing first information required for tracking the location of a battery device that can be installed in a vehicle; and a second information processing unit for providing information about the battery device, wherein... The first information processing device performs the following: when the front battery device is removed from the first vehicle, it accepts the registration of the first information of the front battery device; the second information processing device performs the following: it determines whether the first information of the front battery device has been registered in the first information processing device; if the first information of the front battery device has been registered in the first information processing device, it performs the first processing required to provide the second information of the front battery device.

8. The information processing system as described in claim 7, wherein, The aforementioned second information processing device does not perform the aforementioned first processing if the aforementioned first information is not registered in the aforementioned first information processing device.

9. The information processing system as described in claim 7, wherein, The first processing step is the process of reading the second information from the predetermined memory device.

10. The information processing system as described in claim 9, wherein, The memory device mentioned above refers to the memory device possessed by the battery device mentioned above.

11. The information processing system as described in claim 8, wherein, The aforementioned second information processing device performs second processing required to provide third information that is different from the aforementioned second information.

12. The information processing system as described in claim 11, wherein, The third piece of information in the foregoing contains the information necessary for the vehicle in the foregoing to move.

13. The information processing system as described in claim 7, wherein, The second piece of information in the foregoing section contains information regarding the deterioration status of the battery device mentioned above.

14. The information processing system as described in claim 7, wherein, The aforementioned second information processing device detects and memorizes the combination of the aforementioned battery device and the vehicle on which the aforementioned battery device is installed.

15. The information processing system as described in claim 14, wherein, The second information processing device will execute the first processing of the preceding information regardless of whether the first information of the preceding information is registered in the first information processing device of the preceding information when the known preceding combination is detected.

16. An information processing method, executed by an information processing apparatus for providing information about a battery device that can be installed in a vehicle, comprising: determining whether first information required for tracking the location of a previous battery device has been registered in a designated management device; performing first processing required for providing second information about the previous battery device, provided that the first information has been registered in the designated management device; detecting and memorizing a combination of the previous battery device and the vehicle in which the previous battery device is installed; and performing the first processing of the previous information regardless of whether the first information of the previous information is registered in the designated management device when a known combination is detected.

Images