Information processing device, information processing system, and information processing method

Abstract

An information processing device according to the present invention provides information about a battery device that can be installed on a vehicle. The information processing device performs first processing for: determining whether first information for tracking the location of the battery device is registered at a prescribed management device; and providing second information about the battery device on the condition that the first information is registered at the prescribed management device.

Description

Information processing device, information processing system, and information processing method

[0001] The present disclosure relates to vehicle technology.

[0002] There are known technologies for providing information about the battery of an electric vehicle. For example, Patent Document 1 discloses a system that determines the degree of deterioration of a battery installed in a vehicle and notifies a user of the need to replace the battery.

[0003] Japanese Patent Application Laid-Open No. 2021-191159

[0004] The present disclosure aims to encourage registration of information for tracking batteries installed in vehicles.

[0005] One aspect of an embodiment of the present disclosure is an information processing device that provides information regarding a battery device that can be attached to a vehicle, and has a control unit that performs the following: determining whether first information for tracking the location of the battery device is registered in a specified management device; and, on the condition that the first information is registered in the specified management device, executing a first process for providing second information regarding the battery device.

[0006] One aspect of an embodiment of the present disclosure is an information processing system including a first information processing device that manages first information for tracking the location of a battery device that can be attached to a vehicle, and a second information processing device that provides information about the battery device, wherein the first information processing device accepts registration of the first information about the battery device when the battery device is removed from a first vehicle, and the second information processing device determines in the first information processing device whether the first information corresponding to the battery device has been registered, and performs a first process to provide second information about the battery device, on condition that the first information has been registered in the first information processing device.

[0007] One aspect of an embodiment of the present disclosure is an information processing method executed by an information processing device that provides information about a battery device that can be attached to a vehicle, the information processing method including: determining whether first information for tracking the location of the battery device is registered in a specified management device; and, on the condition that the first information is registered in the specified management device, executing a first process for providing second information about the battery device.

[0008] Other aspects include a method executed by the above-described device, a program for causing a computer to execute the method, or a computer-readable storage medium non-transitoryly storing the program.

[0009] According to the present disclosure, it is possible to encourage registration of information for tracking a battery installed in a vehicle.

[0010] 1 is a schematic diagram of a battery management system according to a first embodiment. FIG. 1 is a hardware configuration diagram of a server device according to a first embodiment. FIG. 2 is a hardware configuration diagram of a business operator terminal according to a first embodiment. FIG. 3 is a hardware configuration diagram of a diagnostic device according to a first embodiment. FIG. 4 is a hardware configuration diagram of a battery pack according to a first embodiment. FIG. 5 is a software configuration diagram of a server device according to a first embodiment. An example of tracking information stored in a server device. FIG. 6 is a software configuration diagram of a business operator terminal according to a first embodiment. FIG. 7 is a software configuration diagram of a diagnostic device according to a first embodiment. FIG. 8 is a software configuration diagram of a battery pack according to a first embodiment. FIG. 9 is a sequence diagram of a process for registering tracking information in a server device. FIG. 10 is a first sequence diagram of a process executed when a status information request is made. FIG. 11 is a second sequence diagram of a process executed when a status information request is made. FIG. 12 is a third sequence diagram of a process executed when a status information request is made. FIG. 13 is a fourth sequence diagram of a process executed when a status information request is made. FIG. 14 is a fifth sequence diagram of a process executed when a status information request is made.

[0011] In recent years, there has been an increase in automobiles that are equipped with a drive battery and can run on electricity as an energy source, such as electric vehicles (BEVs) and plug-in hybrid electric vehicles (PHEVs).

[0012] As electric vehicles become more widespread, it is predicted that businesses that remove batteries from used vehicles and sell them will become more active. However, used vehicle batteries may harm the environment if not recycled properly. Furthermore, even if a battery is recycled and installed in a new vehicle, its value cannot be accurately estimated unless it is evaluated using the correct method established by the vehicle manufacturer. To solve these problems, it is desirable for manufacturers (such as vehicle manufacturers) to be able to track batteries removed from vehicles. However, currently, once a battery is separated from a vehicle, it is difficult for vehicle manufacturers to track its whereabouts. The information processing device according to the present disclosure solves such problems.

[0013] One aspect of the present disclosure is an information processing device that provides information about a battery device that can be installed in a vehicle, and specifically includes a control unit that determines whether first information for tracking the location of the battery device is registered in a predetermined management device, and, if the first information is registered in the predetermined management device, executes a first process to provide second information about the battery device.

[0014] A battery device is a packaged battery for an electric vehicle. In addition to the battery itself, the battery device may also include a control computer, an interface for connecting to the vehicle, a storage device, and the like.

[0015] The information processing device is, for example, a device that connects to a battery device and reads information from the battery device. Alternatively, the information processing device may be, for example, a computer (battery ECU) mounted on the battery device. A control unit of the information processing device determines whether first information corresponding to the target battery device is registered in a predetermined management device. The first information is information for tracking the location of the battery device, and typically includes information regarding the business that removed the battery device from the vehicle, the purpose of the removal, the recipient of the battery device after removal, etc.

[0016] The first information is typically registered in a predetermined management device (e.g., a center server that manages battery information) by the business operator who removed the battery device when the battery device is removed from the vehicle. Furthermore, the control unit executes a first process for providing second information about the battery device, provided that the first information is registered in the predetermined management device. Preferably, the control unit does not execute the first process for providing the second information if the first information is not registered in the predetermined management device. In this case, if the first information is not registered in the management device when the battery device is removed from the vehicle, the second information about the battery device cannot be acquired.

[0017] The second information whose acquisition is restricted by the control unit is preferably information for evaluating the battery device, such as the battery device's usage history, deterioration status, and self-diagnosis results. If such information acquisition restrictions are imposed on the battery device, the market value of the battery device may decrease. With this configuration, the business operator or the like can be motivated to register the first information when the battery device is removed, which makes it easier to track the battery device.

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

[0019] The control unit may also execute a second process to provide third information different from the second information. That is, the control unit may provide the third information even when acquisition of the second information is restricted. The third information is preferably information necessary for running the vehicle or information necessary for ensuring safety. This configuration makes it possible to maintain the safety performance of a vehicle equipped with a reused battery while, for example, preventing access to information necessary for determining market prices. This can motivate the business operator or the like to register the first information when the battery device is removed.

[0020] The control unit may detect and store a combination of the battery device and the vehicle to which the battery device is attached. When the control unit detects the combination that is known, the control unit may execute the first process regardless of whether the first information is registered.

[0021] Specific embodiments of the present disclosure will be described below with reference to the accompanying drawings. Unless otherwise specified, the hardware configuration, module configuration, functional configuration, etc. described in each embodiment are not intended to limit the technical scope of the disclosure to those configurations.

[0022] First Embodiment An overview of a battery management system according to a first embodiment will be described with reference to FIG. 1 . The battery management system according to this embodiment is a system that uses a server device 1 to manage information about a battery pack 4 designed for an electric vehicle. The battery pack 4 is a unit in which a control computer (ECU) and the like are added to a drive battery of the vehicle. In the description of the embodiment, the battery pack is also referred to as a "battery device" or simply as a "battery." The battery pack can be removed from the original vehicle and, for example, installed in another electric vehicle or reused as a home storage battery.

[0023] The server device 1 is a computer that collects and manages information related to the battery pack installed in the vehicle. The server device 1 may be a device operated by the automobile manufacturer that manufactured the electric vehicle.

[0024] If the server device 1 is operated by an automobile manufacturer, the server device 1 may manage information about battery packs installed in automobiles manufactured by the same manufacturer. For example, the server device 1 may periodically collect information about the vehicle, such as the vehicle's identifier, location information, speed, and mileage, and store the information about the battery pack 4 in association with the collected information. This allows the server device 1 to grasp the latest status of the vehicle and the battery pack 4.

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

[0026] In the following description, the information that can be provided by the battery pack 4 will be referred to as "status information." The status information is stored in a storage device that the battery pack 4 has, and can be read out via the diagnostic device 3. When the battery pack 4 is mounted on a vehicle, the status information can also be read out by an ECU that the vehicle has.

[0027] Examples of the status information include the driving history of the vehicle equipped with the battery pack 4, the number of charge / discharge cycles, SoC (State of Charge), SoH (State of Health), etc. The status information includes information necessary for driving the vehicle (e.g., information related to SoC, voltage, current, power, etc.), information necessary for ensuring safety (e.g., temperature information and safety threshold of current), and information for evaluating the value of the battery pack 4 (e.g., SoH and the number of charge / discharge cycles).

[0028] Generally, the battery pack 4 is used while being linked to a vehicle. In this state, the automobile manufacturer can track its location via a communication device installed in the vehicle. However, if the battery pack 4 is removed from the vehicle, it becomes difficult to track the battery pack that does not have a communication device.

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

[0030] Furthermore, in this embodiment, when the diagnostic device 3 is connected to the removed battery pack 4, a process is executed to determine whether or not to permit reading of the status information. Specifically, the battery pack 4 connected to the diagnostic device 3 inquires of the server device 1 about the presence or absence of tracking information for the battery pack 4 itself, and if the tracking information is not registered in the server device 1, the provision of at least part of the status information ("second information" in this disclosure) is refused. If the tracking information is registered in the server device 1, all of the status information can be read.

[0031] According to this configuration, when a business operator removes a battery pack from a vehicle, the business operator is motivated to register the tracking information in the server device 1. This makes it possible to encourage the registration of tracking information, and makes it easier to track a battery pack removed from a vehicle.

[0032] [Hardware Configuration] Next, the hardware configuration of each device constituting the system will be described. First, the components of the server device 1 will be described. Fig. 2 is a diagram schematically illustrating 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.), a main memory device (RAM, ROM, etc.), and an auxiliary memory device (EPROM, hard disk drive, removable media, etc.). The auxiliary memory device stores an operating system (OS), various programs, various tables, etc., and by executing the programs stored therein, various functions (software modules) that meet specific purposes, as described below, can be realized. However, some or all of the functions may be realized as hardware modules using hardware circuits such as ASICs and FPGAs.

[0034] The server device 1 includes a control unit 11 , a storage unit 12 , and a communication unit 13 .

[0035] The control unit 11 is a computing unit that executes predetermined programs to realize various functions of the in-vehicle device 10. The control unit 11 can be realized by, for example, a hardware processor such as a CPU. The control unit 11 may also be configured to include a RAM, a ROM (Read Only Memory), a cache memory, etc.

[0036] The storage unit 12 is a means for storing information and includes a main storage unit and an auxiliary storage unit. The main storage unit is a memory in which the programs executed by the control unit 11 and the data used by the control programs are expanded. The auxiliary storage unit is a device in which the programs executed by the control unit 11 and the data used by the control programs are stored. The auxiliary storage unit may store the programs executed by the control unit 11 packaged as applications. It may also store an operating system for executing these applications. The programs stored in the auxiliary storage unit are loaded into the main storage unit and executed by the control unit 11, thereby performing the processing described below.

[0037] The primary storage device may include a random access memory (RAM) or a read-only memory (ROM). The secondary storage device may include an erasable programmable read-only memory (EPROM) or a hard disk drive (HDD). The secondary storage device may also include removable media, i.e., portable recording media.

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

[0039] Next, we will explain the components of the operator terminal 2. Fig. 3 is a diagram schematically illustrating an example of the hardware configuration of the operator terminal 2. Like the server device 1, the operator terminal 2 can be configured as a computer having a processor (CPU, GPU, etc.), a main storage device (RAM, ROM, etc.), and an auxiliary storage device (EPROM, hard disk drive, removable media, etc.).

[0040] The operator terminal 2 includes a control unit 21 , a storage unit 22 , a communication unit 23 , and an input / output unit 24 .

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

[0042] The storage unit 22 is a means for storing information, and is configured with storage media such as RAM, a magnetic disk, a flash memory, etc. The storage unit 22 stores programs executed by the control unit 21, data used by the programs, etc.

[0043] The communication unit 23 is a communication interface for connecting the carrier terminal 2 to a 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 operator terminal 2 and presents 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 combined into a single touch panel display. The input / output unit 24 may also include hardware interfaces such as a keyboard and a mouse.

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

[0046] The diagnostic device 3 includes a control unit 31 , a storage unit 32 , a communication unit 33 , a CAN communication unit 34 , and an input / output unit 35 .

[0047] The control unit 31 is a computing unit that executes predetermined programs to realize various functions of the diagnostic device 3. The control unit 31 can be realized by, for example, a hardware processor such as a CPU. The control unit 31 may also be configured to include RAM, ROM (Read Only Memory), cache memory, etc.

[0048] The storage unit 32 is a means for storing information, and is configured with storage media such as RAM, a magnetic disk, a flash memory, etc. The storage unit 32 stores programs executed by the control unit 31, data used by the programs, etc.

[0049] The communication unit 33 is a communication interface for connecting the diagnostic device 3 to a network. The communication unit 33 may be a wired communication interface or a wireless communication interface. Connecting the diagnostic device 3 to the network via the communication unit 33 enables communication between the diagnostic device 3 and the server device 1.

[0050] The CAN communication unit 34 is an interface 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 standard (e.g., Controller Area Network, hereinafter referred to as "CAN") adopted in the vehicle. The CAN communication unit 34 may be a CAN interface.

[0051] If the battery pack 4 is mounted on a vehicle, the diagnostic device 3 and the battery pack 4 may be connected via the vehicle. In this case, connecting the diagnostic device 3 to a port on the vehicle network enables communication between the diagnostic device 3 and the battery pack 4. The diagnostic device 3 and the battery pack 4 may also be directly connected. In this case, for example, the CAN interfaces of the diagnostic device 3 and the battery pack 4 may be connected by a cable. In this way, it is also possible to connect the battery pack 4 removed from the vehicle 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 presents 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 the liquid crystal display are combined into a single touch panel display. The input / output unit 35 may also include hardware interfaces such as a keyboard and a mouse.

[0053] Next, the battery pack 4 will be described. Fig. 5 is a diagram schematically illustrating an example of the hardware configuration of the battery pack 4. The battery pack 4 is a unit in which a battery main body (battery 44) such as a lithium ion battery is added with a computer (ECU 41) for controlling the charging and discharging of the battery, a CAN communication unit 42, and a storage unit 43.

[0054] The ECU 41 cooperates with the vehicle's ECU to control the charging and discharging of the battery. The ECU 41 can also read and provide status information stored therein in response to an external request. The status information includes, for example, information for evaluating the battery pack 4, such as the number of charging and discharging cycles, as well as information necessary for vehicle operation, such as the remaining battery charge (state of charge).

[0055] The status information may be requested by the diagnostic device 3, or may be requested by an ECU of a vehicle equipped with the battery pack 4. For example, information necessary for vehicle operation (e.g., remaining battery charge) and information necessary for safety management (e.g., temperature information) are also part of the status information.

[0056] The diagnostic device 3 requests, as status information, information for evaluating the battery pack 4 (for example, SoH and the number of charge / discharge cycles). In this embodiment, when the ECU 41 receives a request for status information from the diagnostic device 3, the ECU 41 inquires of the server device 1 via the diagnostic device 3 whether tracking information has been registered. If the ECU 41 can confirm the existence of tracking information, the ECU 41 provides the status information to the diagnostic device 3. If the ECU 41 cannot confirm the existence of tracking information, the ECU 41 refuses to provide the status information.

[0057] When a request is made to provide status information necessary for vehicle operation or status information necessary for safety management (the "third information" in this disclosure), the ECU 41 unconditionally provides the information. The third information does not include the second information described above.

[0058] The CAN communication unit 42 is an interface for connecting the battery pack 4 to a vehicle or the diagnostic device 3. The CAN communication unit 42 is used for direct connection with the diagnostic device 3 and also for communication with the vehicle. When the battery pack 4 is mounted on a vehicle, the CAN communication unit 42 is connected to an interface on the vehicle side. In this case, the battery pack 4 and the diagnostic device 3 can communicate with each other via an in-vehicle network.

[0059] The storage unit 43 is a means for storing information, and is configured with a storage medium such as a RAM, a magnetic disk, a flash memory, etc. The storage unit 43 stores programs executed by the ECU 41, data used by the programs, etc.

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

[0061] In this embodiment, the control unit 11 of the server device 1 is configured to have two software modules: an information registration unit 111 and an information provision unit 112. Each software module may be realized by the control unit 11 (e.g., a CPU) executing a program stored in the storage unit 12 (described later). The information processing executed by the software module is synonymous with the information processing executed by the control unit 11 (e.g., a CPU).

[0062] In response to a request from the business operator terminal 2, the information registration unit 111 acquires information (tracking information) about a specific battery pack from the business operator terminal 2. As described above, the business operator who removed the battery pack 4 from the diagnostic device 3 uses the business operator terminal 2 to transmit information for tracking the battery pack 4 to the server device 1. The information registration unit 111 receives the information and stores it in the memory unit 12 (tracking information table). Note that there may be cases where a record for 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 may generate a new record in the tracking information table based on the received information.

[0063] 7 is an example of a tracking information table. As shown in the figure, the tracking information table includes information such as an ID (battery ID) used by the automobile manufacturer to uniquely identify the battery, the battery model number, the date the battery was removed, and the owner of the battery at the time of removal. The tracking information table may also include information such as the purpose of removing the battery and the recipient of the battery. By referencing the tracking information table, for example, it is possible to identify the recipient of the battery, thereby obtaining information for estimating the current location of the battery.

[0064] In response to an inquiry sent from the diagnostic device 3 or the battery pack 4, the information providing unit 112 determines whether or not a record corresponding to the specified battery pack exists in the tracing information table stored in the storage unit 12. For example, in the example of Fig. 7, when an inquiry is received from a battery pack having a battery ID of "B001", the information providing unit 112 returns a response indicating that "a tracing information record exists for the specified battery pack."

[0065] The storage unit 12 stores the tracking information table described above.

[0066] Next, a description will be given of the software configuration of the business operator terminal 2. Fig. 8 is a diagram schematically showing the software configuration of the business operator terminal 2 according to this embodiment.

[0067] The control unit 21 of the business operator terminal 2 is configured to have a registration unit 211 as a functional module. This functional module may be realized by executing a stored program by a CPU. The registration unit 211 acquires tracking information regarding the target battery pack 4 via the input / output unit 24 and transmits the acquired tracking information to the server device 1 as battery information. The registration unit 211 accepts input from an operator information such as an ID (battery ID) for identifying the target battery pack, the battery model number, the date the battery was removed, and the owner of the battery at the time of removal, and transmits this information to the server device 1. Note that if the reuse destination or transfer destination of the removed battery pack is known, this information may be included in the tracking information.

[0068] Next, a description will be given of the software configuration of the diagnostic device 3. Fig. 9 is a diagram schematically showing the software configuration of the diagnostic device 3 according to this embodiment.

[0069] The control unit 31 of the diagnostic device 3 is configured to have an information acquisition unit 311 as a functional module. This functional module may be realized by executing a stored program by a CPU. The information acquisition unit 311 acquires and outputs status information from a target battery pack 4 based on instructions from an operator of the device. For example, the information acquisition unit 311 instructs the connected battery pack 4 to read the status information and outputs the status information transmitted from the battery pack 4 via the input / output unit 35. Note that the information acquisition unit 311 may also instruct the battery pack 4 to perform a self-diagnosis. If the status information is generated in response to the execution of a self-diagnosis, the status information may be acquired after the self-diagnosis is completed.

[0070] Next, a description will be given of the software configuration of the battery pack 4. Fig. 10 is a diagram schematically showing the software configuration of the battery pack 4 according to this embodiment.

[0071] The ECU 41 of the battery pack 4 is configured to have two functional modules: a management unit 411 and an information providing unit 412. These functional modules may be realized by executing stored programs by a CPU.

[0072] The management unit 411 cooperates with the vehicle-side ECU to control charging and discharging of the battery main body. The management unit 411 may periodically acquire information about the battery and store it in the storage unit 43 as status information. Examples of the information about the battery include the mileage of the vehicle equipped with the battery pack 4, the number of times the battery 44 has been charged and discharged, temperature information about the battery 44, information about the maximum output of the battery 44, and information about the maximum capacity of the battery 44. The management unit 411 is also configured to be able to perform additional functions such as self-diagnosis of the battery. For example, the self-diagnosis calculates the battery's State of Health (SoH). The diagnosis results may be stored in the storage unit 43 as part of the status information.

[0073] The information providing unit 412 reads out the status information stored in the storage unit 43 based on a request received from the outside and provides it.

[0074] The request for providing status information may be received from the diagnostic device 3 or from an ECU provided in the vehicle. When a request for providing status information necessary for driving or status information necessary for safety management is received from the ECU provided in the vehicle, the information providing unit 412 provides this status information unconditionally.

[0075] When the information providing unit 412 receives a request to provide status information from the diagnostic device 3, the information providing unit 412 provides the status information on the condition that tracking information corresponding to the device itself is registered in the server device 1. Specifically, the information providing unit 412 transmits data via the diagnostic device 3 to the server device 1 inquiring whether tracking information corresponding to the device itself is registered.

[0076] The information providing unit 412 receives a response sent from the server device 1 in response to the inquiry. For example, if the response indicates that "there is no tracking information for the battery pack related to the inquiry," the information providing unit 412 refuses to provide the requested status information or provides only part of the requested status information. When restricting the provision of only part of the status information, the information providing unit 412 may determine the information to be restricted based on the information stored in the storage unit 43.

[0077] 2 to 6 and 8 to 10 are merely examples, and all or part of the illustrated functions may be performed using dedicated circuits. Furthermore, programs may be stored or executed using a combination of a main memory device and an auxiliary memory device other than those illustrated.

[0078] Next, the processing executed by each device included in the system will be described. Fig. 11 is a sequence diagram of the processing in which the server device 1 acquires information about a battery pack 4 removed from a specific vehicle from the business operator terminal 2. The illustrated processing is executed when the battery pack 4 is removed from the vehicle. The processing may be started by operating the business operator terminal 2 owned by the business operator that removed the battery pack 4.

[0079] First, in step S11, the business operator terminal 2 accepts input of tracking information for the target battery pack. As shown in FIG. 7 , the tracking information may include an identifier for uniquely identifying the battery, the business operator performing the removal, the original owner, the purpose of the removal, etc. Furthermore, if the battery has already been removed, the tracking information may also include the removal date, the recipient, etc. The input tracking information is transmitted to the server device 1.

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

[0081] Next, a description will be given of a process executed by the diagnostic device 3 when reading out status information from the battery pack 4. Fig. 12 is a sequence diagram showing an example of a process executed by the diagnostic device 3 when acquiring status information from the battery pack 4.

[0082] When the diagnostic device 3 is connected to the battery pack 4, the diagnostic device 3 is able to communicate with the ECU 41 of the battery pack 4. As a result, the ECU 41 recognizes that it has been attached to the diagnostic device 3 (step S21).

[0083] In step S22, the diagnostic device 3 receives an instruction to read status information from the connected battery pack 4. The diagnostic device 3 generates data (provision request) requesting the provision of status information and transmits this to the battery pack 4.

[0084] Upon receiving the request for providing status information, the ECU 41 generates data for inquiring of the server device 1 as to whether or not tracking information of the ECU 41 itself has been registered (step S23). The inquiry includes the battery pack identifier (battery ID). The inquiry is transmitted to the server device 1 via the diagnostic device 3.

[0085] The server device 1 (information provider 112) that has received the inquiry searches the tracking information table using the battery ID included in the inquiry as a key and extracts a matching record (step S24). As a result, if one or more records that match the battery ID are extracted, the server device 1 generates a response (positive response) indicating that the battery related to the inquiry is registered and transmits it to the diagnostic device 3. If there is no record that matches the battery ID, the server device 1 generates a response (negative response) indicating that the battery related to the inquiry is not registered and transmits it to the diagnostic device 3. The diagnostic device 3 transfers 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 a negative response, the battery pack 4 (ECU 41) transmits information (a refusal response) indicating that the status information cannot be provided to the diagnostic device 3. If the response from the server device 1 is a positive response, the process proceeds to step S26, where the ECU 41 reads out predetermined status information from the storage unit 43.

[0087] The ECU 41 may refuse to read the status information if the transmission of the inquiry fails or if no response is received from the server device 1. That is, the ECU 41 may refuse to provide the status information if no positive response is received from the server device 1 within a predetermined period of time. The status information is output by the diagnostic device 3 and provided to the operator of the device (step S27).

[0088] As described above, the battery management system according to this embodiment executes a process for authenticating a battery pack when the battery pack to be managed is connected to the diagnostic device 3. Furthermore, if information for tracking the battery pack (tracking information) is not registered in the server device 1, reading of status information from the battery pack is restricted. A battery pack with a restriction on reading of status information has a lower market value compared to a battery pack without such a restriction. This creates motivation to register tracking information when removing a battery pack, making it easier for vehicle manufacturers and the like to track the battery. Note that even if a restriction on reading of status information is imposed, the restriction may be lifted by subsequently registering tracking information. This achieves the objective of enabling tracking of the battery pack.

[0089] Second Embodiment In the first embodiment, the ECU 41 included in the battery pack 4 makes an inquiry to the server device 1. On the other hand, the inquiry to the server device 1 may be made by the diagnostic device 3. In the second embodiment, the diagnostic device 3 makes an inquiry to the server device 1 and determines whether or not to provide status information.

[0090] 13 is a sequence diagram showing an example of processing executed when the diagnostic device 3 acquires status information from the battery pack 4. The steps indicated by dotted lines are the same as those in the first embodiment.

[0091] When the diagnostic device 3 is connected to the battery pack 4, the diagnostic device 3 becomes able to communicate with the ECU 41 of the battery pack 4. This allows the ECU 41 to recognize that it has been attached to the diagnostic device 3 (step S21). In step S22, the diagnostic device 3 receives an instruction to read status information from the connected battery pack 4.

[0092] When an instruction to request reading of the status information is given to the diagnostic device 3, the diagnostic device 3 generates a query to the server device 1 to confirm whether or not tracking information of the battery pack 4 has been registered (step S23A). The query includes the identifier (battery ID) of the battery pack. The query is sent to the server device 1.

[0093] The server device 1 (information providing unit 112 ) that has received the inquiry generates an affirmative response or a negative response by the same process as in step S 24 of the first embodiment, and transmits it to the diagnostic device 3 .

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

[0095] In this way, it is also possible to have the diagnostic device 3 execute some of the processing that was executed by the battery pack 4 in the first embodiment.

[0096] Third Embodiment In the first embodiment, the battery pack 4 makes an inquiry to the server device 1 every time it receives a provision request. However, if the battery pack 4 is mounted on a vehicle and the combination of the vehicle and the battery pack has not changed, it may be possible to omit the inquiry to the server device 1. In the third embodiment, the battery pack 4 stores the combination of the vehicle and the battery pack itself, and omits the inquiry to the server device 1 if the combination has not changed.

[0097] 14 is a sequence diagram showing an example of processing executed when the diagnostic device 3 acquires status information from the battery pack 4. The steps indicated by dotted lines are the same as those in the first embodiment.

[0098] In the third embodiment, after reading the status information in step S26, the battery pack 4 executes a step (step S32) of storing a vehicle identifier (e.g., an identifier of the vehicle ECU) in the storage unit 43. This step can also be considered as a step in which the battery pack 4 associates itself with the vehicle and stores the association. Note that if the battery pack 4 is not attached to the vehicle, this step is omitted.

[0099] In the third embodiment, the battery pack 4 executes step S31 at the timing when the battery pack 4 receives the provision request.

[0100] In step S31, the battery pack 4 determines whether the identifier of the vehicle in which it is currently installed is stored in the storage unit 43. For example, if the battery pack 4 is not installed in the vehicle (e.g., if communication with the vehicle's ECU is not established), or if the identifier of the vehicle in which the battery pack 4 is currently installed is different from the identifier stored in step S32, a negative determination is made in this step. If the identifier of the vehicle in which the battery pack 4 is installed is the same as the identifier stored in step S32, a positive determination is made in this step. A positive determination in this step means that the combination of the battery pack 4 and the vehicle has not changed since the last time the status information was read. In this case, the battery pack 4 skips querying the server device 1 and instead reads the status information. If a negative determination is made in this step, the battery pack 4 queries the server device 1 using the method previously described.

[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 the battery pack 4 is attached. However, the information may be stored in the diagnostic device 3.

[0102] 15 is a sequence diagram showing an example of processing executed when the diagnostic device 3 acquires status information from the battery pack 4. The steps indicated by dotted lines are the same as those in the second embodiment.

[0103] In this modification, after providing the status information in step S27, the diagnostic device 3 executes a step (step S34) of storing a combination of the vehicle identifier (e.g., the identifier of the vehicle ECU) and the identifier of the battery pack 4 (e.g., the identifier of the ECU 41) in the storage unit 32. Note that if the battery pack 4 is not attached to the vehicle, this step is omitted.

[0104] In this modification, the diagnostic device 3 executes step S33 at the timing when a request to read out the status information is received.

[0105] In step S33, the diagnostic device 3 determines whether the combination of the identifier of the currently connected battery pack 4 and the identifier of the vehicle is stored in the storage unit 43. For example, if the battery pack 4 and the diagnostic device 3 are directly connected, or if the combination of the identifier of the battery pack 4 and the identifier of the vehicle is different from that stored in step S34, the determination in this step is negative. If the combination of the identifier of the battery pack 4 and the identifier of the vehicle is the same as that stored in step S34, the determination in this step is positive. If the determination here is positive, it means that the combination of the battery pack 4 and the vehicle has not changed since the last time the status information was read. In this case, the diagnostic device 3 omits querying the server device 1 and executes reading of the status information. If the determination in this step is negative, the diagnostic device 3 queries the server device 1 using the method previously described.

[0106] (Modifications) The above-described embodiment is merely an example, and the present disclosure may be modified as appropriate within the scope of the gist thereof. For example, the processes and means described in the present disclosure may be freely combined and implemented as long as no technical contradiction occurs.

[0107] Furthermore, in each embodiment, an example has been described in which the status information is stored in the battery pack 4, but it is also possible that the status information is collected and managed by the server device 1. In this case, the diagnostic device 3 (or the business operator terminal 2) may request the status information of a given battery pack 4 from the server device 1. In this case, the server device 1 may determine whether or not tracking information about the specified battery pack 4 is stored in a predetermined database, and if so, provide the requested status information.

[0108] 16 is a sequence diagram showing an example of the processing executed when the business operator terminal 2 acquires status information from the server device 1. The steps indicated by dotted lines are the same as those in the second embodiment. In this modification, the business operator terminal 2, rather than the diagnostic device 3, generates and transmits an inquiry to the server device 1 (steps S22 to S23A). The server device 1 extracts tracking information by processing similar to that in step S24.

[0109] In step S41, the server device 1 determines whether tracking information for the specified battery pack 4 is registered in the tracking information table. If registration is found, the process proceeds to step S42, where the server device 1 acquires status information for the specified battery pack 4 from a predetermined database or the like and transmits it to the business operator terminal 2. The business operator terminal 2 outputs the acquired status information (step S27). If tracking information for the specified battery pack 4 is not registered in the tracking information table, the process ends. In this way, the status information may be stored in the server device 1, rather than in the battery pack 4. In this case, the "information processing device" and the "predetermined management device" in this disclosure both correspond to the server device 1.

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

[0111] The present disclosure can also be realized by supplying a computer program that implements the functions described in the above embodiments to a computer, and having one or more processors in the computer read and execute the program. Such a computer program may be provided to the computer on a non-transitory computer-readable storage medium connectable to the computer's system bus or via a network. Non-transitory computer-readable storage media include, for example, any type of disk, such as a magnetic disk (e.g., a floppy disk, a hard disk drive (HDD), etc.), an optical disk (e.g., a CD-ROM, a DVD disk, a Blu-ray disk), a read-only memory (ROM), a random access memory (RAM), an EPROM, an EEPROM, a magnetic card, a flash memory, an optical card, or any type of medium suitable for storing electronic instructions.

[0112] REFERENCE SIGNS LIST 1... Server device 2... Business operator terminal 3... Diagnostic device 4... Battery pack

Claims

1. An information processing device that provides information about a battery device that can be attached to a vehicle, the information processing device having a control unit that performs the following: determining whether first information for tracking the location of the battery device is registered in a specified management device; and, on the condition that the first information is registered in the specified management device, executing a first process for providing second information about the battery device.

2. The information processing device according to claim 1, wherein the control unit does not execute the first process if the first information is not registered in the predetermined management device.

3. The information processing device according to claim 1, wherein the first processing is processing for reading the second information from a predetermined storage device.

4. The information processing device according to claim 3, wherein the predetermined storage device is a storage device included in the battery device.

5. The information processing device according to claim 2, wherein the control unit executes a second process for providing third information different from the second information.

6. The information processing device according to claim 5, wherein the third information includes information necessary for driving the vehicle.

7. The information processing device according to claim 1, wherein the second information includes information relating to a deterioration state of the battery device.

8. The information processing device according to claim 1, wherein the control unit detects and stores a combination of the battery device and the vehicle to which the battery device is attached.

9. The information processing device according to claim 8, wherein the control unit executes the first process when a known combination is detected, regardless of whether the first information is registered in the specified management device.

10. An information processing system including a first information processing device that manages first information for tracking the location of a battery device that can be attached to a vehicle, and a second information processing device that provides information about the battery device, wherein the first information processing device performs the following: when the battery device is removed from a first vehicle, accepting registration of the first information about the battery device; and the second information processing device performs the following: determining in the first information processing device whether the first information corresponding to the battery device has been registered; and performing a first process to provide second information about the battery device, on condition that the first information has been registered in the first information processing device.

11. The information processing system according to claim 10, wherein the second information processing device does not execute the first process if the first information is not registered in the first information processing device.

12. The information processing system according to claim 10, wherein the first processing is processing for reading the second information from a predetermined storage device.

13. The information processing system according to claim 12, wherein the predetermined storage device is a storage device included in the battery device.

14. The information processing system according to claim 11, wherein the second information processing device executes a second process for providing third information different from the second information.

15. The information processing system according to claim 14, wherein the third information includes information necessary for running the vehicle.

16. The information processing system according to claim 10, wherein the second information includes information relating to a deterioration state of the battery device.

17. The information processing system according to claim 10, wherein the second information processing device detects and stores the combination of the battery device and the vehicle to which the battery device is attached.

18. The information processing system according to claim 17, wherein the second information processing device executes the first process when a known combination is detected, regardless of whether the first information is registered in the first information processing device.

19. An information processing method executed by an information processing device that provides information about a battery device that can be attached to a vehicle, the information processing method including: determining whether first information for tracking the location of the battery device is registered in a specified management device; and executing a first process for providing second information about the battery device, on the condition that the first information is registered in the specified management device.

Images