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

Abstract

To urge registration of information for tracking a battery mounted on a vehicle.SOLUTION: For a battery device mountable on a vehicle, it is determined whether predetermined information for tracking the location of the battery device is registered in a predetermined management device, and when it is determined that the predetermined information is not registered, at least a part of functions provided by the battery device mounted on the vehicle is invalidated.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to vehicle technology. [Background technology]

[0002] There is known a technology 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 the user of the need to replace the battery. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-191159 Summary of the Invention [Problem to be solved by the invention]

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

[0005] One aspect of the present disclosure is The information processing device has a control unit that determines whether or not specified information for tracking the location of a battery device that can be attached to a vehicle is registered in a specified management device, and if it is determined that the registration is not present, disables at least some of the functions provided by the battery device attached to the vehicle.

[0006] One aspect of the present disclosure is An information processing system including a first device that manages specified information for tracking the location of a battery device that can be attached to a vehicle, and a second device that can communicate with a battery control device possessed by the battery device, wherein the first device executes accepting registration of the specified information for the battery device when the battery device is removed from a first vehicle, and the second device executes determining whether the specified information corresponding to the battery device has been registered in the first device, and when it is determined that the registration has not occurred, disabling at least some of the functions provided by the battery device attached to a second vehicle.

[0007] One aspect of an embodiment of the present disclosure is This is an information processing method in which an information processing device determines whether or not specified information for tracking the location of a battery device that can be attached to a vehicle is registered in a specified management device, and if it is determined that the registration is not present, disables at least some of the functions provided by the battery device attached to the vehicle.

[0008] Another aspect of the present invention is a program for causing a computer to execute the above-described method, or a computer-readable storage medium that non-transitoryly stores the program. [Effects of the Invention]

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

[0010] [Figure 1] 1 is a schematic diagram of a battery management system according to a first embodiment; [Figure 2] FIG. 2 is a hardware configuration diagram of a server device according to the first embodiment. [Figure 3] FIG. 2 is a hardware configuration diagram of a carrier terminal according to the first embodiment. [Figure 4]FIG. 2 is a hardware configuration diagram of a vehicle according to the first embodiment. [Figure 5] FIG. 2 is a hardware configuration diagram of the battery pack according to the first embodiment. [Figure 6] FIG. 2 is a software configuration diagram of a server device according to the first embodiment. [Figure 7] 10 shows an example of tracking information stored in a server device. [Figure 8] FIG. 2 is a software configuration diagram of a carrier terminal according to the first embodiment. [Figure 9] FIG. 2 is a software configuration diagram of the vehicle according to the first embodiment. [Figure 10] FIG. 2 is a software configuration diagram of the battery pack according to the first embodiment. [Figure 11] 10 is an example of a function list stored in a battery pack. [Figure 12] FIG. 10 is a sequence diagram of a process for registering tracking information in a server device. [Figure 13] FIG. 10 is a first sequence diagram of processing executed when the battery pack is attached. [Figure 14] FIG. 10 is a second sequence diagram of the processing executed when the battery pack is attached. [Figure 15] FIG. 10 is a third sequence diagram of the process executed when the battery pack is attached. [Figure 16] FIG. 10 is a fourth sequence diagram of the processing executed when the battery pack is attached. DETAILED DESCRIPTION OF THE INVENTION

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

[0012] As electric vehicles become more widespread, it is predicted that the business of removing batteries from used cars and buying and selling them will become more active. However, used car batteries can be harmful to 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 specified by the vehicle manufacturer. To solve these problems, it would be desirable for manufacturers (vehicle manufacturers, etc.) to be able to track batteries that have been removed from vehicles. However, at present, it is difficult for vehicle manufacturers, etc. to track the whereabouts of a battery once it has been separated from the vehicle. The information processing device according to the present disclosure solves such problems.

[0013] An information processing device according to one aspect of the present disclosure has a control unit that determines whether or not specified information for tracking the location of a battery device that can be attached to a vehicle is registered in a specified management device, and if it is determined that the registration is not present, disables at least some of the functions provided by the battery device attached to the vehicle.

[0014] The information processing device is, for example, a computer (vehicle ECU) mounted on a vehicle, or a computer (battery ECU) mounted on a battery device. The control unit of the information processing device determines whether predetermined information about the target battery device is registered in a predetermined management device. The predetermined information is information for tracking the location of the battery device, such as information about the business that removed the battery device from the vehicle, the purpose of the removal, and the recipient after removal.

[0015] The predetermined information is typically registered in a predetermined management device (for example, a center server) when the battery device is removed from the vehicle. The predetermined management device may be the information processing device itself. Furthermore, if the predetermined information is not registered in the management device, the control unit disables at least some of the functions provided by the battery device newly installed in the vehicle. For example, if predetermined information is not registered in the management device when the battery device is removed from the vehicle, at least some of the functions of the battery device will become unavailable when the battery device is re-installed in the vehicle.

[0016] The battery device may provide multiple functions, such as a function necessary for driving the vehicle and a function for providing historical information, etc. The control unit may selectively disable these functions. If the function is disabled in this way, the market value of the battery device may decrease. With this configuration, it is possible to motivate businesses and the like to register information when removing a battery device, and it is possible to obtain the effect of making it easier to track the battery.

[0017] The information processing device may be a device (for example, an ECU mounted on a vehicle) that can communicate with a control device (ECU, etc.) built into the battery device. In this case, if the target battery device is not registered, the control unit may instruct the control device built into the battery device to disable a function. Alternatively, the control unit may disable a function by restricting communication between the control device and the information processing device itself.

[0018] Furthermore, the control unit may disable a second function of the plurality of functions provided by the battery device without disabling a first function. The first function is preferably a function necessary for vehicle operation or a function for ensuring safety. In this case, the second function may be a function for providing additional information. This configuration makes it possible to maintain the safety performance of vehicles equipped with reused batteries while, for example, disabling the provision of additional information, which can motivate businesses and others to register information when removing the battery device.

[0019] Furthermore, when the control unit detects that the battery device has been mounted on the vehicle, the control unit may determine whether or not the predetermined information has been registered. For example, in the case where the information processing device is mounted on the vehicle side, when new communication is established with the control device of the battery device, it may be determined that the battery device has been attached to the vehicle.

[0020] Furthermore, when predetermined information corresponding to a battery device is registered in a predetermined management device, the control unit may store a combination of the vehicle on which the battery device is installed and the battery device. Furthermore, when the combination of the vehicle on which the battery device is installed and the battery device is already stored in the storage unit, the control unit may not determine whether the predetermined 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 a vehicle 3, which is an electric vehicle. The battery pack 4 is a unit in which a control computer is added to a drive battery of the vehicle. In the description of the embodiment, the battery pack is also simply referred to as a battery. The battery pack can be removed from the original vehicle and, for example, installed in another electric vehicle or reused for purposes such 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 vehicle 3.

[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 3, 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 3 and the battery pack 4.

[0025] Generally, the battery pack 4 is used while being linked to the vehicle 3. However, if the battery pack 4 is removed from the vehicle 3, it becomes difficult to track the battery pack, which does not have a communication device.

[0026] Therefore, in this embodiment, when the battery pack 4 is removed from the vehicle 3, the server device 1 acquires and manages information for tracking the target battery pack 4 ("predetermined 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.

[0027] Furthermore, in this embodiment, when a removed battery pack is transferred and installed in another vehicle, a process for authenticating the battery pack is executed. Specifically, a battery pack newly connected to a vehicle inquires of the server device 1 about the presence or absence of tracking information about itself, and if the tracking information is not registered in the server device 1, predetermined functions among the multiple functions provided by the battery pack are disabled. If the tracking information is registered in the server device 1, no functional restrictions are imposed, and all functions of the battery pack become available. In this specification, this series of processes is referred to as "reattachment authentication."

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

[0029] [Hardware configuration] Next, the hardware configuration of each device that constitutes the system will be described. First, a description will be given of the components of the server device 1. Fig. 2 is a diagram showing an example of a hardware configuration of the server device 1.

[0030] 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 match predetermined 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, FPGAs, etc.

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

[0032] The control unit 11 executes a predetermined program to realize various functions of the server device 1. The control unit 11 can be realized by a hardware processor such as a CPU, for example. The control unit 11 may also be configured to include a RAM, a ROM (Read Only Memory), a cache memory, and the like.

[0033] 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.

[0034] The main memory may include RAM (Random Access Memory) and ROM (Read Only Memory). The auxiliary memory may include EPROM (Erasable Programmable ROM) and hard disk. It may also include a disk drive (HDD, Hard Disk Drive). may include removable media, i.e., portable recording media.

[0035] 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.

[0036] Next, a description will be given of 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 memory device (RAM, ROM, etc.), and an auxiliary memory device (EPROM, hard disk drive, removable media, etc.).

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

[0038] 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.

[0039] 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.

[0040] The communication unit 23 is a communication interface for connecting the operator terminal 2 to a network. The communication unit 23 may be a wired communication interface or a wireless communication interface.

[0041] 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 composed of a single touch panel display. Note that the input / output unit 24 may also include hardware interfaces such as a keyboard and a mouse.

[0042] Next, a description will be given of the vehicle 3. Fig. 4 is a diagram schematically illustrating an example of the hardware configuration of the vehicle 3. The vehicle 3 is an electric vehicle equipped with a battery pack 4. The vehicle 3 is typically a BEV (Battery EV), but may be, for example, a plug-in hybrid vehicle, etc., as long as it is a vehicle powered by a drive battery. The vehicle 3 is wirelessly connected to the server device 1. The vehicle 3 is also communicably connected to the battery pack 4 via an in-vehicle network (CAN network).

[0043] The vehicle 3 includes an ECU 31 , a wireless communication unit 32 , and a CAN communication unit 33 . The ECU 31 is an electronic control unit that controls the running of the vehicle 3. The ECU 31 controls components necessary for running the vehicle, such as the engine and motor, and also communicates with the battery pack 4 (described later) and relays data necessary for authenticating the re-installation of the battery pack 4.

[0044] The wireless communication unit 32 is a wireless communication interface for connecting the vehicle 3 to a network. The wireless communication unit 32 is configured to be able to communicate with the server device 1 via, for example, a wireless LAN or a mobile communication service such as 3G, 4G, or 5G. The CAN communication unit 33 is a communication interface with an in-vehicle network provided in the vehicle 3. The CAN communication unit 33 communicates with the vehicle 3 via a CAN (Controller Area Network) network. Communicate.

[0045] Next, a description will be given of the battery pack 4. 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 computer (ECU 41) for controlling charging and discharging of the battery, a CAN communication unit 42, and a storage unit 43 are added to a battery main body (battery 44) such as a lithium ion battery. The ECU 41 controls charging and discharging of the battery body in cooperation with the ECU 31 of the vehicle 3. Furthermore, when the ECU 41 is connected to a new vehicle, the ECU 41 performs re-attachment authentication of the ECU 41.

[0046] In this embodiment, when the vehicle 3 and the battery pack 4 are newly connected, the ECU 41 detects this and inquires of the server device 1 via the vehicle 3 about the presence or absence of tracking information. If the presence of tracking information is confirmed, the ECU 41 enables all functions of the device itself. If the presence of tracking information is not confirmed, the ECU 41 disables certain functions provided by the device itself (i.e., makes the functions unavailable).

[0047] The CAN communication unit is an interface for connecting the battery pack 4 to an in-vehicle network of the vehicle 3. The ECU 41 can communicate with the vehicle 3 (CAN communication unit 33) via the CAN communication unit . 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.

[0048] [Software configuration] Next, the software configuration of each device that constitutes the system will be described. Fig. 6 is a diagram that schematically shows the software configuration of the server device 1 according to this embodiment.

[0049] In this embodiment, the control unit 11 of the server device 1 includes an information registration unit 111 and an information The information providing unit 112 includes two software modules. Each software module may be realized by the control unit 11 (CPU, etc.) 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 (CPU, etc.).

[0050] In response to a request from the business operator terminal 2, the information registration unit 111 acquires information (tracking information) about a predetermined battery pack from the business operator terminal 2. As described above, the business operator who has removed the battery pack 4 from the vehicle 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) as shown in FIG. 6. Note that there may be a case where a record for the target battery pack already exists in the tracking information table stored in the server device 1. In this case, the information registration unit 111 may generate a new record for the tracking information table based on the received information.

[0051] 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 in question.

[0052] In response to an inquiry sent from the vehicle 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."

[0053] The tracking information table is stored in the storage unit 12. The "ID information" in FIG.

[0054] 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.

[0055] The control unit 21 of the operator terminal 2 is configured to have a registration unit 211 as a functional module. The functional module may be realized by executing a stored program by a CPU. The registration unit 211 acquires tracking information related to the target battery pack 4 via the input / output unit 24, and transmits the acquired tracking information to the server device 1. The registration unit 211 receives input from the operator information such as an ID (battery ID) for identifying the target battery pack, the model number of the battery, 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.

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

[0057] The ECU 31 of the vehicle 3 is configured to have a relay unit 311 as a functional module. The functional module is realized by executing a stored program by a CPU. That's fine. The relay unit 311 serves to relay data transmitted from the battery pack 4 connected to the vehicle 3 to the server device 1. For example, the relay unit 311 transfers an inquiry transmitted from the battery pack 4 to the server device 1, and transfers a response transmitted from the server device 1 to the battery pack 4. This enables the battery pack 4, which does not have a communication function, to interact with the server device 1.

[0058] 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.

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

[0060] The management unit 411 controls charging and discharging of the battery main body in cooperation with the ECU 31 of the vehicle 3. The management unit 411 also provides a plurality of functions exemplified in this specification. The management unit 411 is an example of a "battery control device" in the present disclosure.

[0061] When the device is newly connected to a vehicle, the function restriction unit 412 performs re-attachment authentication of the device. Specifically, the function restriction unit 412 detects that the device has been newly connected to the vehicle 3, and transmits data to the server device 1 via the vehicle 3 inquiring whether tracking information corresponding to the device has been registered. The fact that the device has been newly connected to the vehicle 3 can be determined based on, for example, the identifier of the ECU 31 of the vehicle 3. For this reason, the function restriction unit 412 may store information (such as a list of ECU identifiers) relating to the history of vehicles 3 to which the device has been connected in the past.

[0062] The function restriction unit 412 receives a reply sent from the server device 1 in response to the inquiry. For example, if the reply indicates that "there is no tracking information for the battery pack related to the inquiry," the function restriction unit 412 performs processing to restrict (disable) a predetermined function from among the multiple functions possessed by the function restriction unit 412. For example, the function restriction unit 412 issues an instruction to the management unit 411 to disable the predetermined function.

[0063] The function restriction unit 412 determines the functions to be disabled based on the function list stored in the storage unit 43. Fig. 11 shows an example of the function list. Here, it is assumed that the battery pack 4 has four functions as shown in the figure. The first function (function ID: F001) is a function that performs communication necessary for the vehicle to run with the vehicle's ECU. The second function (function ID: F002) is a function to ensure driving safety, such as an overcurrent prevention function and a temperature monitoring function. The third function (function ID: F003) is a function to provide status information of the battery pack 4. The status information may be information about battery deterioration, such as the number of charge / discharge cycles and SoH (State of Health). The fourth function (Function ID: F004) is the self-diagnosis function. By running the self-diagnosis, the status information is updated to the latest information. In the example shown, only two functions, F003 and F004, are to be disabled. If these functions are disabled, it will no longer be possible to perform self-diagnosis, generate status information, or read that status information.

[0064] 2 to 6 and 8 to 10 are merely examples, and all or part of the illustrated functions may be executed using dedicated circuits. The program may be stored and / or executed by a combination of the device and secondary storage device.

[0065] Next, the processes executed by each device included in the system will be described. 12 is a sequence diagram of a process in which the server device 1 acquires, from the business operator terminal 2, information about a battery pack 4 that has been removed from a predetermined vehicle 3. The illustrated process is executed at the timing when the battery pack 4 is removed from the vehicle 3. The process may be started by operating the business operator terminal 2 owned by the business operator that has removed the battery pack 4.

[0066] 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 include the removal date, the recipient, etc. The input tracking information is transmitted to the server device 1.

[0067] 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.

[0068] Next, a process to be executed when the removed battery pack 4 is attached to another vehicle will be described. Fig. 13 is a sequence diagram showing an example of a process to be executed when the battery pack 4 is reattached to another vehicle.

[0069] When the battery pack 4 is newly installed in the vehicle 3, the ECU 41 of the battery pack 4 becomes capable of communicating with the ECU 31 of the vehicle 3. As a result, the ECU 41 recognizes that the ECU 41 itself has been installed in the vehicle 3 (step S21). The ECU 41 may be configured to store the identifiers of vehicle-side ECUs with which communication has been established in the past, thereby enabling the ECU 41 to determine whether the battery pack 4 has been installed for the first time in the target vehicle 3. The ECU 41 may execute the process described below only when it has not previously communicated with the ECU 31 with which it is to communicate.

[0070] When the ECU 41 recognizes that its own device has been installed in the vehicle 3, the ECU 41 generates data for inquiring of the server device 1 as to whether tracking information of its own device has been registered (step S22). The inquiry includes an identifier of the battery pack (battery ID). The inquiry is transmitted to the server device 1 via the vehicle 3 (ECU 31).

[0071] 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 S23). 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 this to the vehicle 3 (ECU 31). 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 this to the vehicle 3 (ECU 31). The ECU 31 transfers the received response to the battery pack 4 (ECU 41).

[0072] In step S24, the battery pack 4 (ECU 41) determines the content of the response. If the response is a positive response, the process ends. If the response is a negative response, the process ends. The process proceeds to step S25, where the ECU 41 disables the target function based on the function list stored in the storage unit 43. For example, in the example of FIG. 11, disabling the target functions restricts the provision of the "status information providing function" and the "self-diagnosis function."

[0073] The ECU 41 may disable the target function if the transmission of the inquiry fails or if no response is received from the server device 1. That is, the ECU 41 may disable the target function if no positive response is received from the server device 1 within a predetermined period of time.

[0074] As described above, the battery management system according to this embodiment executes a process (reinstallation authentication) to authenticate a battery pack when the battery pack to be managed is removed from a vehicle and reinstalled in another vehicle. If, during reinstallation authentication, information for tracking the battery pack (tracking information) is not registered in the server device 1, functional restrictions are imposed on the battery pack. A battery pack for which tracking information is not registered cannot provide full functionality compared to a battery pack for which tracking information is registered, and therefore its value in the market decreases. This creates motivation to register tracking information when removing a battery pack, making it easier for vehicle manufacturers and the like to track batteries. Even if a restriction is placed on reading the status information, the restriction may be lifted by subsequently registering tracking information, thereby achieving the purpose of enabling tracking of the battery pack.

[0075] (Second embodiment) In the first embodiment, the ECU 41 of the battery pack 4 determines whether or not to disable the target function. However, the ECU 31 on the vehicle side may determine whether or not to disable the target function. In the second embodiment, the ECU 31 of the vehicle 3 detects the re-attachment of the battery pack 4 and determines whether or not to disable the function.

[0076] FIG. 14 is a sequence diagram showing an example of a process executed when the battery pack 4 is reattached to the vehicle.

[0077] When the battery pack 4 is attached to the vehicle 3, the ECU 41 of the battery pack 4 becomes capable of communicating with the ECU 31 of the vehicle 3. As a result, the ECU 31 of the vehicle 3 recognizes that the battery pack 4 has been attached to the vehicle (step S21A).

[0078] The ECU 31 may be configured to store the identifier of an ECU of a battery pack 4 with which communication has been established in the past. This allows the ECU 31 to determine whether the battery pack 4 has been installed in the vehicle for the first time. The ECU 31 may execute the process described below only when it has not previously communicated with the ECU 41 that is to be the communication partner.

[0079] When the ECU 31 recognizes that the battery pack 4 has been attached to the vehicle, the ECU 31 generates an inquiry to the server device 1 to check whether tracking information for the battery pack 4 has been registered (step S22A). The inquiry includes an identifier (battery ID) of the battery pack. The inquiry is transmitted to the server device 1.

[0080] The server device 1 (information providing unit 112) that has received the inquiry generates a positive or negative response by the same process as in step S23 of the first embodiment, and transmits the response to the vehicle 3 (ECU 31 )

[0081] In step S24A, the vehicle 3 (ECU 31) determines the content of the response. If the response is a positive response, the process ends. If the response is a negative response, the process proceeds to step S25A, where the ECU 31 transmits data instructing the battery pack 4 (ECU 41) to restrict functions. Upon receiving the data, the ECU 41 disables the target functions based on the function list stored in the storage unit 43.

[0082] (Third embodiment) In the first embodiment, the target function is disabled by the ECU 41 of the battery pack 4. However, the function may be disabled by an ECU on the vehicle side.

[0083] FIG. 15 is a sequence diagram showing an example of a process executed when the battery pack 4 is reattached to the vehicle. The processing sequence in this embodiment differs from the processing sequence in the second embodiment (Figure 14) only in the processing (step S25B) performed when tracking information corresponding to the target battery pack 4 has not been registered in the server device 1.

[0084] In step S25B, the ECU 31 of the vehicle 3 executes a process of restricting access to the restricted functions among the functions provided by the battery pack 4. Note that in this step, the ECU 31 may inquire in advance of the ECU 41 about the restricted functions. For example, in the example of Figure 11, if access to the target function is restricted, "provision of status information" and "self-diagnosis" cannot be performed even if requested by a vehicle occupant. In this way, by setting access restrictions between devices, the target function can also be disabled.

[0085] (Fourth embodiment) In the first embodiment, the ECU 41 of the battery pack 4 determines whether to disable a function, and in the second and third embodiments, the ECU 31 of the vehicle 3 determines whether to disable a function. On the other hand, whether to disable a function provided by the battery pack 4 may be determined by the server device 1. In this embodiment, the server device 1 determines whether or not to disable a function provided by the battery pack 4, and the server device 1 instructs the ECU 41 of the battery pack 4 to disable the target function.

[0086] FIG. 16 is a sequence diagram showing an example of a process executed when the battery pack 4 is reattached to the vehicle. In this embodiment, like the second embodiment, the ECU 31 of the vehicle 3 detects that a new battery pack 4 has been installed (step S21A), but differs from the second embodiment in that the server device 1 determines whether or not to restrict functionality.

[0087] In this embodiment, when the ECU 31 determines that a new battery pack 4 has been installed, it transmits to the server device 1 a combination of the identifier (ECU-ID) of its own device (i.e., the ECU 31) and the identifier (ECU-ID) of the ECU (ECU 41) that the battery pack 4 has.

[0088] In this embodiment, the server device 1 is configured to be able to store combinations of ECU-IDs that have been detected in the past. The "ID information" shown in FIG. 6 is a list showing combinations of ECU-IDs that have been detected in the past by the server device 1. By referring to this list, the server device 1 can It can be determined whether the target battery pack 4 is installed in the target vehicle 3 for the first time.

[0089] The server device 1 determines whether or not the above-mentioned ECU-ID combination is acquired for the first time based on the above-mentioned ID information (step S31). If the acquired ECU-ID combination is not stored in the server device 1, this means that the target battery pack 4 has been installed in the target vehicle 3 for the first time (step S31-YES). In this case, the process proceeds to step S23. If the acquired ECU-ID combination is stored in the server device 1, the process ends.

[0090] In step S23, similarly to the second embodiment, the server device 1 extracts a record corresponding to the target battery pack from the tracking information table stored in the storage unit 12. If a record is extracted (YES in step S33), the process ends. If no record is extracted (NO in step S33), the process proceeds to step S34, where the server device 1 transmits data instructing the target battery pack 4 (ECU 41) to restrict functions via the vehicle 3 (ECU 31). Having received the data, the ECU 41 disables the target function based on the function list stored in the storage unit 43 (step S25).

[0091] (Variation) The above-described embodiment is merely an example, and the present disclosure can be modified and implemented as appropriate within the scope that does not deviate from the gist of the disclosure. For example, the processes and means described in this disclosure can be freely combined and implemented as long as no technical contradiction occurs.

[0092] 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.

[0093] The present disclosure can also be realized by providing a computer program implementing 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 via 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. [Explanation of symbols]

[0094] 1. Server device 2. Operator terminal 3. Vehicle 4. Battery pack

Claims

1. Determining whether or not predetermined information for tracking the location of a battery device that can be installed in a vehicle is registered in a predetermined management device; When it is determined that the registration is not made, disabling at least a part of the functions provided by the battery device mounted on the vehicle; and An information processing device having a control unit that executes the above.

2. the control unit makes the determination when detecting that the battery device is mounted on a vehicle. The information processing device according to claim 1 .

3. When the predetermined information corresponding to the battery device is registered in the predetermined management device, the control unit stores a combination of the vehicle on which the battery device is mounted and the battery device in a storage unit. The information processing device according to claim 1 .

4. when the control unit detects that the battery device is mounted on a vehicle, the control unit searches the storage unit for a combination of the vehicle on which the battery device is mounted and the battery device, and when the combination is stored in the storage unit, the control unit does not perform the determination. The information processing device according to claim 3 .

5. When it is determined that the registration is not present, the control unit issues an instruction to a battery control device included in the battery device to disable at least a part of the functions provided by the battery device. The information processing device according to claim 1 .

6. when it is determined that the registration is not present, the control unit does not disable a first function but disables a second function among the functions provided by the battery device. The information processing device according to claim 1 .

7. the first function includes a function necessary for vehicle operation and a function for safety; The second function includes a function of providing additional information. The information processing device according to claim 6 .

8. a first device that manages predetermined information for tracking the location of a battery device that can be installed in a vehicle; a second device capable of communicating with a battery control device included in the battery device, The first device comprises: When the battery device is removed from the first vehicle, receiving registration of the predetermined information about the battery device; The second device comprises: determining whether the predetermined information corresponding to the battery device is registered in the first device; When it is determined that the registration is not present, disabling at least a part of the functions provided by the battery device mounted on the second vehicle; and An information processing system that executes the above.

9. When the second device detects that the battery device is mounted on the second vehicle, In this case, the determination is made. The information processing system according to claim 8 .

10. the second device stores a combination of the second vehicle and the battery device in a storage unit when the predetermined information corresponding to the battery device is registered in the first device; The information processing system according to claim 8 .

11. when the second device detects that the battery device is mounted on a vehicle, it searches the storage unit for a combination of the vehicle on which the battery device is mounted and the battery device, and if the combination is stored in the storage unit, it does not perform the determination. The information processing system according to claim 10.

12. When it is determined that the second device is not registered, the second device issues an instruction to the battery control device to disable at least a part of the functions provided by the battery device. The information processing system according to claim 8 .

13. When it is determined that the registration is not present, the second device does not disable a first function but disables a second function among the functions provided by the battery device. The information processing system according to claim 8 .

14. the first function includes a function necessary for vehicle operation and a function for safety; The second function includes a function of providing additional information. The information processing system according to claim 13.

15. the first device accepts registration of the predetermined information from an operator terminal corresponding to an operator that has removed the battery device from the first vehicle; The information processing system according to claim 8 .

16. the predetermined information includes information regarding a business operator that removed the battery device from the first vehicle and a purpose for removing the battery device; 16. The information processing system according to claim 15.

17. The information processing device Determining whether or not predetermined information for tracking the location of a battery device that can be installed in a vehicle is registered in a predetermined management device; When it is determined that the registration is not made, disabling at least a part of the functions provided by the battery device mounted on the vehicle; and An information processing method that performs the above.

Images