DE102019112942A1 - Cloud-managed recovery of a high-voltage battery profile - Google Patents

Abstract

This disclosure provides a cloud managed recovery of a high voltage battery profile. A system includes a memory that stores a battery profile that corresponds to a battery identifier of a high voltage battery of a vehicle, and a processor. The processor is programmed to periodically send the battery profile to a server and, in response to detecting a change in the battery identifier, prompting the server to send a battery profile corresponding to the changed battery identifier.

Description

TECHNICAL AREA

Aspects of the disclosure generally relate to the cloud management of battery profiles for storage and recovery.

GENERAL PRIOR ART

Battery capacity is an important parameter for a successful battery monitoring system. For example, the exact battery capacity is critical to the accurate estimation of the state of charge. The battery capacity also determines how much energy is stored in the battery and thus determines the EV range for an electrified vehicle. The battery capacity may decrease with the age of the battery, especially if the battery is used intensively. Therefore, electric vehicles include systems for learning information indicating the capacity of the vehicle battery.

SUMMARY

In one or more illustrative examples, a system includes a memory that stores a battery profile that corresponds to a battery identifier of a high voltage battery of a vehicle, and a processor. The processor is programmed to periodically send the battery profile to a server and, in response to detecting a change in the battery identifier, prompting the server to send a battery profile corresponding to the changed battery identifier.

In one or more illustrative examples, a method includes, in response to detecting a change in a battery identifier of a battery of a vehicle, prompting a server connected to the vehicle via a wide area network to send a battery profile corresponding to the battery identifier to the vehicle ; and using the battery profile to customize a battery control strategy for the battery.

In one or more illustrative examples, a non-transitory computer-readable medium includes instructions that, when executed by a processor of a vehicle, cause the vehicle to prompt a server that is in communication with the vehicle in response to detection of a change in a battery identifier of a battery of the vehicle a wide area network is connected to send a battery profile corresponding to the battery identifier to the vehicle; and using the battery profile to customize a battery control strategy for the battery.

list of figures

• 1 illustrates an exemplary system for providing battery profiles for vehicles.
• 2 illustrates an exemplary hybrid electric vehicle;
• 3 illustrates an exemplary process for providing battery profiles for vehicles; and
• 4 illustrates an example process for using the battery age as a factor in providing battery profiles for vehicles.

DETAILED DESCRIPTION

As needed, detailed embodiments of the present invention are disclosed herein; however, it should be understood that the disclosed embodiments are merely exemplary of the invention, which may be embodied in various and alternative forms. The figures are not necessarily to scale; some features can be zoomed in or out to show details of specific components. Thus, specific structural and functional details disclosed herein are not to be construed as limiting, but merely as a representative basis for teaching one skilled in the art to variously employ the present invention.

For a hybrid or battery electric vehicle to function optimally, a vehicle's battery energy control (BECM) module is configured to utilize certain battery characteristics (such as battery pack capacity and battery performance). These features are normally learned during vehicle operation by the BECM, and if they change, the battery control strategy is adjusted accordingly.

If a BECM fails or if a battery is replaced, these features are lost or become unknown. For example, a discharged battery pack may be replaced with a charged battery pack to speed up the charging of the vehicle. In the event of failure and replacement of the BECM, the new BECM would require time to learn the characteristics of the existing battery. In a case where another battery is being loaded into the vehicle, the existing BECM would require time to learn the characteristics of the replacement battery. However, the vehicle operating time required by the BECM to learn the battery characteristics is time, in which vehicle powertrain may not operate optimally, which affects vehicle efficiency and range.

Remotely stored battery profiles can be used to quickly recover learned features for a given battery and transmit those features to the BECM. The spread of embedded modems in vehicles allows the BECM to periodically upload a battery profile to a cloud database. The battery profile may include a unique identifier that corresponds to a specific battery pack. When a BECM of a vehicle communicates with a battery on board the vehicle with an unrecognized identifier, the BECM may instruct the vehicle to request the most recent battery profile associated with that battery pack from a remote database via the vehicle's embedded modem. The cloud manager may then respond with the requested profile forwarded by the vehicle to the BECM, thereby allowing the battery control strategy to return to operating at an optimal level.

1 illustrates an exemplary system 100 for providing battery profiles 110 for vehicles 102 , As shown, the system includes 100 a vehicle 102 in communication with a battery profile server 108 over a wide area network 104 , The vehicle 102 is for wireless communication with base stations 106 configured with the wide area network 104 are connected. For the sake of clarity, there is only one base station 106 However, it should be noted that the systems 100 typically many base stations 106 which are arranged to cover a large geographical area. Although in 1 an exemplary system 100 is shown, the exemplary components shown are not intended to be limiting. In fact, the system can 100 contain more or less components and additional or alternative components and / or reactions may be used. As an example, the system 100 more or less vehicles 102 , Base stations 106 and / or battery profile server 108 include. In other examples, the vehicle may 102 over other connections than via the base station 106 with the battery profile server 108 communicate, such as via WiFi, dedicated short range communication (DSRC) or other communication protocol over which battery profiles 110 can be sent and / or received.

At the vehicles 102 These may include various types of automobiles, crossover utility vehicles (CUVs), sport utility vehicles (SUVs), recreational vehicles (RVs), boats, airplanes, or other mobile transporting or transporting machines to trade goods. In many cases, the vehicle can 102 be driven by an internal combustion engine. Another possibility is the vehicle 102 a hybrid electric vehicle (HEV) powered by both an internal combustion engine and one or more electric motors, such as a series hybrid electric vehicle (SHEV), a parallel hybrid electric vehicle (PHEV), or a parallel / series hybrid Electric vehicle (PSHEV). In other examples, the vehicle may 102 a hydrogen powered vehicle 102 his. Because the type and configuration of the vehicle 102 can also vary the capabilities of the vehicle 102 vary accordingly. As some other options, the vehicles can 102 different abilities in terms of passenger capacity, hitch and load and storage space. Other aspects of the functions of the vehicle 102 be referring to 2 discussed in detail.

The wide area network 104 may include one or more interconnected communications networks, such as, but not limited to, the Internet, a cable television distribution network, a satellite communications network, a local area network, and a telephone network. By accessing the wide area network 104 can the vehicle 102 to be able to get output data from the vehicle 102 to network destinations in the wide area network 104 to send and input data to the vehicle 102 of network destinations in the wide area network 104 to recieve.

The base stations 106 may include system hardware configured to allow mobile transceivers of the vehicle 102 on the communication services of the wide area network 104 access. In one example, the base stations 106 Be part of a Global System for Mobile communication (GSM) mobile service provider. In another example, the base stations 106 Be part of a Code Division Multiple Access (CDMA) mobile service provider. The base stations 106 can support several different technologies and data transfer rates.

The battery profile server 108 may include computing hardware configured to provide data services related to the transmission of battery profiles 110 to the vehicles 102 and / or receiving battery profiles 110 from the vehicles 102 provide. The battery profiles 110 can provide information about the characteristics of a HV battery 112 of the vehicle 102 include. These features For example, a measure of the battery capacity of the HV battery 112 include, over time, monitoring the use of the HV battery 112 was determined. The battery profiles 110 may further include a unique identifier corresponding to a specific battery pack.

2 illustrates further aspects of the vehicle 102 , 2 illustrates representative relationships between the components. The physical location and orientation of the components within the vehicle may vary. The vehicle 102 includes a gearbox 202 and is powered by at least one electric machine 204 . 206 with selective support from an internal combustion engine 208 driven. As shown, the transmission can 202 have a power split configuration in which the transmission 202 the first electric machine 204 and a second electric machine 206 includes. The electric machine (s) 204 . 206 can in one example be electric motors with alternating current (AC). The electric machine 204 receives electrical power and provides torque for vehicle propulsion. The second electric machine 206 It also serves as a generator for converting mechanical power into electrical power and optimizing power flow through the transmission 202 , In other embodiments, the transmission 202 no power split configuration and can use only a single electric machine for drive and generation. It is understood that in 2 illustrated scheme is merely exemplary in nature and is not intended to be limiting. In fact, other configurations of the internal combustion engine 208 and the electrical machines 204 . 206 for transmission of power through the transmission 202 considered.

The vehicle 102 includes an energy storage device such as a traction HV battery 112 for storing electrical energy. In the traction battery 112 it is a high voltage battery capable of delivering electrical power to the electrical machines 204 . 206 to operate. The HV battery 112 also gets electrical power from the electrical machines 204 . 206 when they work as generators. The HV battery 112 is a battery pack consisting of a plurality of battery modules (not shown), each battery module containing a plurality of battery cells (not shown). A high-voltage bus connects the HV battery 112 by Sagittarius 212 electrically with the electrical machines 204 . 206 so the HV battery 112 with the electrical machines 204 . 206 connected when the shooter 212 are electrically activated, and of the electrical machines 204 . 206 is separated when the shooter 212 are electrically disabled. The HV battery 112 can also use a battery identifier 210 Associated, for example, on the HV battery 112 be stored on and from a vehicle bus or a dedicated connection with the HV battery 112 can be accessed. In another example, the battery identifier 210 be identified by a barcode coming from the HV battery 112 is read out.

The vehicle 102 also includes a LV battery 214 , which is connected to a low voltage bus, the low voltage loads 216 of the vehicle 102 powered. As some examples may be a cellular modem 218 , a WiFi modem 220 and a BLUETOOTH modem 222 to the low voltage loads 216 belong. A battery monitoring sensor 224 is with the low voltage battery 214 and provides a voltage measurement signal that can be used to determine the state of charge (SoC) of the low voltage battery 214 to measure and / or to calculate. A temperature sensor 236 will also be inside the vehicle 102 provided to provide a signal that is the temperature of the environment of the LV battery 214 and / or the vehicle 102 indicates.

The vehicle 102 also includes a DC / DC converter 226 or a variable voltage converter (WC). The converter 226 is electrically connected between the high voltage bus (the traction battery 112 and the first electric machines 204 . 206 connects) and the low voltage bus coming from the low voltage battery 214 operated, connected. The converter 226 reduces or reduces the voltage potential of the electrical power that the low-voltage battery 214 from the high voltage battery 112 provided. The converter 226 In addition, the voltage potential of the electrical power coming from the low-voltage battery 214 is provided, intensify or increase to the side of the high voltage battery 112 of the converter 226 operate in some embodiments.

The vehicle 102 Also includes various controllers configured to control the operation of the drive components of the vehicle 102 manage. The illustration shows the vehicle 102 a powertrain control unit (PCU) 228 , which is configured to the internal combustion engine 208 to control; a hybrid powertrain control module (HPCM) 230 that is configured to the transmission 202 to control; a high voltage battery electronic control module (BECM) 232 , which is configured to the high voltage battery 112 , Sagittarius 212 and control other high voltage components; and one and one Body control module (BCM) 234 , which is configured to additional low-voltage functions of the vehicle 102 such as headlamps or door locks.

While each of these controls is illustrated as independent control, the PCM 228 , the HPCM 230 , the BECM 232 and the BCM 234 each part of a larger control system and may be from each other or from different other controls throughout the vehicle 102 to be controlled. It is therefore understood that the PCM 228 , the HPCM 230 , the BECM 232 and the BCM 234 and one or more other controllers may be collectively referred to as a "system controller". The system controller controls various actuators in response to signals from various sensors to control functions, such as starting / stopping the internal combustion engine 208 , Operating the electrical machines 204 . 206 to provide wheel torque or the high voltage battery 112 To charge, gearboxes with the transmission 202 The controller or controllers may include a microprocessor or central processing unit (CPU) connected to various types of computer readable storage devices or media. Computer-readable storage devices or media may include volatile and nonvolatile memory, such as read-only memory (ROM), random-access memory (RAM), and keep-alive memory (KAM). A CAM is a persistent or non-volatile memory that can be used to store different operating variables while the CPU is shutting down. Computer-readable storage devices or media may be implemented using any of a number of known memory devices, such as programmable read-only memory (PROMs), EPROMs (electrical PROMs), EEPROMs (electrically erasable PROMs), flash memory, or any others electric, magnetic, optical or combination storage devices capable of storing data, some of which represent executable instructions used by the controller in controlling the internal combustion engine or vehicle.

The system controller communicates with various engine / vehicle sensors and actuators via an input / output (I / O) interface, which may be implemented as a single integrated interface, providing various raw data or signal conditioning, processing and / or conversion, Short circuit protection and the like provides. Alternatively, one or more dedicated hardware or firmware chips may be used to condition and process certain signals before they are applied to the CPU. Although not explicitly illustrated, the system controller may send signals to and / or from the transmission 202 , the electrical machines 204 . 206 , the internal combustion engine 208 , the shooter 212 , the converter 226 and the battery monitoring sensor 224 communicate. Representative examples of parameters, systems and / or components which may be directly or indirectly controlled using control logic executed by the system controller include fuel injection timing, rate and duration, throttle position, spark timing Spark plugs (spark ignited internal combustion engines), intake and exhaust valve timing and duration, front-end accessory drive (FEAD) components such as an alternator, air conditioning compressor, battery charger, regenerative braking, engine Generator operation, clutch pressures for the gearbox 202 and the same. Sensors that communicate inputs through the I / O interface may be used, such as turbocharger boost, crankshaft position (PIP), engine speed (RPM), wheel speed (WS1, WS2), wheel speed Vehicle speed (VSS), coolant temperature (ECT), intake manifold pressure (MAP), accelerator pedal position (PPS), ignition switch position (IGN), throttle position ( throttle valve position - TP), an air temperature (TMP), an exhaust gas oxygen (EGO), or a concentration or presence of some other constituent of the exhaust gas, an intake air flow (MAF), a gear, a Transmission or a mode of the transmission, a transmission oil temperature (TOT), a turbine speed of the transmission turbine speed (TS), a status of the torque converter bypass clutch (TCC) 34, a deceleration or shift mode (MDE) indicate.

The control logic or functions performed by the system controller may be represented in one or more figures by flowcharts or similar diagrams. These figures provide representative control strategies and / or representative control logic that may be implemented using one or more processing strategies, such as event-driven, interrupt-driven, multi-tasking, multi-threading, and the like, can / can be implemented. Thus, various illustrated steps or functions may be performed in the illustrated order or concurrently, or omitted in some instances. Although not always explicitly illustrated, one of ordinary skill in the art will recognize that one or more of the illustrated steps or functions may be repeatedly performed depending on the particular processing strategy employed. Likewise, the order of processing is not necessarily required to achieve the features and advantages described herein, but rather is to facilitate illustration and description. The control logic may be implemented primarily in software executed by a microprocessor-based vehicle, engine, and / or powertrain control, such as the PCM 228 in an example. Of course, depending on the specific application, the control logic may be implemented as software, hardware or a combination of software and hardware in one or more controllers. For example, in some examples, all or part of the control logic may be executed by a cloud service that is not on board the vehicle 102 located. When implemented in software, the control logic may be provided in one or more computer-readable storage devices or media having stored thereon data representing code or instructions executed by a computer for controlling the vehicle or its subsystems /become. The computer-readable storage devices or media may include one or more of a number of known physical devices that utilize electronic, magnetic, and / or optical data storage to store executable instructions and associated calibration information, operating variables, and the like.

3 illustrates an example process 300 for providing battery profiles 110 for vehicles 102 , The process 300 be implemented using the system control described in detail above.

At process 302 The system control determines whether an updated battery profile 110 to the battery profile server 108 to send. In one example, the system controller may be programmed to control the battery profile 110 periodically from the vehicle 102 to the battery profile server 108 to send. For example, this period may be a period, such as a day, a week, or a month. Additionally or alternatively, the period may be a predefined covered distance of the vehicle 102 (eg 100 kilometers, 500 kilometers, 1000 kilometers). If the system controller determines an updated battery profile 110 to send, the controller goes to action 304 about. Otherwise, the control remains in process 302 ,

at 304 the system controller sends the battery profile 110 of the HV battery pack 112 to the battery profile server 108 , In one example, the system controller may do this by the BECM 232 currently used battery profile 110 and a unique identifier of the HV battery 112 Interrogate. This information can be obtained by using the cellular modem 218 (or the WiFi modem 220 ) to the battery profile server 108 be sent.

At process 306 the system controller determines if there is an identifier of the HV battery pack 112 has changed. In one example, the system controller may select the battery identifier 210 from the HV battery pack 112 Interrogate. If the battery identifier 210 Since the last query changed, the control goes to action 308 about. Otherwise, the control returns to operation 302 back.

at 308 the system control asks for a battery profile 110 of the HV battery pack 112 that by the new battery identifier 210 is identified at the event 306 was specified. In one example, the system controller requests the cellular modem 218 (or the WiFi modem 220) on the battery profile server 108 over the wide area network 104 access to request that the battery profile server 108 a battery profile 110 sends, that of the battery identifier 210 equivalent. The system controller receives the requested battery profile 110 at 310 , in response to the request 308 ,

At process 312 the system control updates with the received battery profile 110 , Accordingly, the BECM 232 with the features of the current HV battery pack 112 Updated without wasting time for the BECM 232 to learn the new features. After operation 312 the controller returns to operation 302 back.

4 illustrates an example process 400 to use the battery age as a factor in providing battery profiles 110 for vehicles 102 , Like the process 300 can the process 400 be implemented using the system control described in detail above.

At process 402 The system controller calculates an age of the HV battery pack 112 , In one example, the system controller calls a date of manufacture from the HV battery pack 112 from. Based on the date of manufacture, the system controller determines a state of the HV battery packs 112 , For example, the battery age may be a factor in battery condition.

at 404 The system control saves the age of the HV battery pack 112 into the BECM 232 , In one example, the system controller writes the battery age to the BECM via a predefined DID 232 , The DID (Data Identifier) diagnostic mechanism is defined in SAE J1979 (also referred to as PID) and allows an ECU to store a predefined set of information at an address that can be called via a diagnostic procedure. DIDs can contain information that provides insight into system status and performance. A specific DID can be used, for example, to maintain the battery age.

At process 406 the system controller calculates battery characteristics of the HV battery pack 112 based on the battery age. In one example, these features include the capacity and performance of the pack.

at 408 The system controller determines whether the updated battery age information is the battery profile 110 to the battery profile server 108 to be sent. In one example, the system controller may be programmed to periodically dispense the battery age from the vehicle 102 to the battery profile server 108 to send. For example, this period may be a period, such as a day, a week, or a month. Additionally or alternatively, the period may be a predefined covered distance of the vehicle 102 (eg 100 kilometers, 500 kilometers, 1000 kilometers). If the system controller determines to send an updated battery age, control goes to action 410 about. Otherwise, the control returns to operation 402 back.

at 410 the system controller sends the battery age to the battery profile server 108 , In one example, the system controller may do this by the BECM 232 currently used battery age and a unique identifier of the HV battery 112 Interrogate. This information can be obtained by using the cellular modem 218 (or the WiFi modem 220 ) to the battery profile server 108 be sent.

at 412 the system controller determines if there is an identifier of the HV battery pack 112 has changed. In one example, the system controller may select the battery identifier 210 from the HV battery pack 112 Interrogate. If the battery identifier 210 Since the last query changed, the control goes to action 414 about. Otherwise, the control returns to operation 402 back.

at 414 The system controller requests the battery age from the battery profile server 108 on. In one example, the system controller requests the cellular modem 218 (or the WiFi modem 220) on the battery profile server 108 over the wide area network 104 access to request that the battery profile server 108 a battery age sends that of the battery identifier 210 equivalent. The system controller receives the requested battery age 416 in response to the request at 414.

at 418 Control Panel updates the BECM 232 with the battery age received. In one example, the system controller writes the battery age to the BECM via a predefined DID (for example, 0x4810) 232 , After operation 418 the controller goes to action 402 about.

In general, computing systems and / or devices may employ any one of a number of computer operating systems, including, but not limited to, versions and / or variants of the Microsoft Windows® operating system, Unix operating system (eg, the Solaris® operating system, distributed by the Oracle Corporation in Redwood Shores, California), the AIX UNIX operating system, distributed by International Business Machines of Armonk, New York, the Linux operating system, the Mac OS X operating system, and iOS distributed by Apple Inc. of Cupertino, California, of the BlackBerry OS, distributed by Research In Motion of Waterloo, Canada, and the Android operating system, developed by the Open Handset Alliance.

Computing devices, such as those of the system controller, generally include computer-executable instructions that may be executable by one or more processors of the computing devices. Computer-executable instructions may be compiled or evaluated by computer programs created using a variety of programming languages and / or technologies, including without limitation and either alone or in combination Java ™, C, C ++, VISUAL BASIC, JAVA SCRIPT, PERL etc. Generally, a processor or microprocessor receives instructions, e.g. From a random access memory, a computer readable medium, etc., and executes these instructions, thereby performing one or more processes, including one or more of the processes described in this document. Such instructions and other data may be stored and transmitted using a variety of computer-readable media.

A computer-readable medium (also referred to as a processor-readable medium) includes any nonvolatile (eg, physical) medium used to provide data (e.g. Instructions) that may be read by a computer (eg, by a processor of a computing device). Such a medium can take many forms, including, but not limited to, nonvolatile media and volatile media. Non-volatile media may include, for example, optical disks or magnetic disks, and other permanent random access memories. For example, volatile media may include dynamic random access memory (DRAM), which is typically a main memory. Such instructions may be transmitted through one or more transmission media, including coaxial cables, copper wire and optical fibers, including the wires comprising a system bus coupled to a processor of a computer. Common forms of computer-readable media include, for example, a floppy disk, a film storage disk, a hard disk, a magnetic tape, any other magnetic media, a CD-ROM, a DVD, any other optical media, punched cards, perforated tape, any other physical media with perforated patterns, a RAM, a PROM, an EPROM, a FLASH EEPROM, any other memory chip, or any other memory cartridge or medium that can be read by a computer.

In some examples, system elements may be implemented as computer-readable instructions (eg, software) on one or more computing devices (eg, servers, personal computers, etc.) that reside on associated computer-readable media (eg, data carriers, random access memories, etc.). are stored. A computer program product may include such instructions stored on computer-readable media for performing the functions described herein. Some or all of the processes disclosed herein, as performed by the system controller as disclosed herein, may be such computer program products. In some examples, these computer program products may be provided as software that, when executed by one or more processors, provides the operations described herein. Alternatively, the computer program products may be provided as hardware or firmware or combinations of software, hardware, and / or firmware.

While embodiments are described above, these embodiments are not intended to describe all possible forms of the invention. Rather, the terms used in the specification are words of description rather than limitation, and it is to be understood that various changes may be made without departing from the spirit and scope of the invention. Additionally, the features of different embodiments may be combined to form further embodiments of the invention.

According to the present invention, there is provided a system comprising: a working memory storing a battery profile corresponding to a battery identifier of a high-voltage battery of a vehicle; and a processor programmed to: periodically send the battery profile to a server, and in response to detecting a change in the battery identifier, prompting the server to send a battery profile corresponding to the changed battery identifier.

According to one embodiment, the battery profile includes information indicating a storage capacity and a battery capacity of the battery, which indicates a general condition of the battery.

In one embodiment, the processor is further programmed to utilize the battery profile to customize a battery control strategy.

In one embodiment, the processor is further programmed to periodically send the battery profile in response to the vehicle traveling a predefined distance.

In one embodiment, the processor is further programmed to periodically send the battery profile in response to a predefined period of time having elapsed.

In one embodiment, the processor is further programmed to identify the battery identifier with a vehicle bus via a connection of a system including the high voltage battery.

In one embodiment, the processor is further programmed to identify the battery identifier in response to receiving bar code information scanned from the battery.

According to the present invention, there is provided a method comprising: in response to detecting a change of a battery identifier of a battery of a vehicle, prompting a server connected to the vehicle via a wide area network to apply a battery profile corresponding to the battery identifier to the vehicle To send vehicle; and using the battery profile to customize a battery control strategy for the battery.

In one embodiment, the invention is further characterized by updating the battery profile in response to power measurements of the battery.

In one embodiment, the invention is further characterized by transmitting the updated battery profile to the server in response to a predefined time period having elapsed since a previous transmission of the battery profile to the server.

In one embodiment, the invention is further characterized by transmitting the updated battery profile to the server in response to a predefined distance having been traveled to the server since a previous transmission of the battery profile.

According to one embodiment, the invention is further characterized by: maintaining the battery identifier in a data memory of a controller; and detecting a change of the battery identifier in response to reading the battery identifier from the battery and comparing the read battery identifier with the stored battery identifier.

In one embodiment, the battery is a traction battery configured to power one or more electric motors of the vehicle.

In one embodiment, the invention is further characterized by utilizing the battery profile to adapt a battery control strategy of the vehicle to characteristics of the battery.

According to the present invention, there is provided a non-transitory computer-readable medium having instructions that, when executed by a processor of a vehicle, cause the vehicle to: in response to detection of a change in a battery identifier of a battery of the vehicle; the vehicle is connected via a wide area network, a battery profile, which corresponds to the battery identifier to send to the vehicle; and using the battery profile to customize a battery control strategy for the battery.

In one embodiment, the invention is further characterized by instructions that, when executed by the processor, cause the vehicle to update the battery profile in response to power measurements of the battery.

In one embodiment, the invention is further characterized by instructions that, when executed by the processor, cause the vehicle to send the updated battery profile to the server in response to a predefined time period having elapsed since a previous transmission of the battery profile to the server.

In one embodiment, the invention is further characterized by instructions that, when executed by the processor, cause the vehicle to send the updated battery profile to the server in response to having traveled a predefined distance since a previous transmission of the battery profile to the server.

In one embodiment, the invention is further characterized by instructions that, when executed by the processor, cause the vehicle to: maintain the battery identifier in a data memory of a controller; and detecting a change of the battery identifier in response to reading the battery identifier from the battery and comparing the read battery identifier with the stored battery identifier.

In one embodiment, the battery is a traction battery configured to power one or more electric motors of the vehicle.

In one embodiment, the invention is further characterized by instructions that, when executed by the processor, cause the vehicle to utilize the battery profile to adapt a battery control strategy of the vehicle to characteristics of the battery.

Claims (14)

System comprising: a working memory storing a battery profile corresponding to a battery identifier of a high-voltage battery of a vehicle; and a processor that is programmed to periodically sending the battery profile to a server, and in response to detecting a change in the battery identifier, prompting the server to send a battery profile that corresponds to the changed battery identifier. System after Claim 1 wherein the battery profile includes information indicating a storage capacity and a battery capacity of the battery, indicating a general condition of the battery. System after Claim 1 The processor is further programmed to utilize the battery profile to customize a battery control strategy. System after Claim 1 wherein the processor is further programmed to periodically send the battery profile in response to the vehicle traveling a predefined distance. System after Claim 1 wherein the processor is further programmed to periodically send the battery profile in response to a predefined period of time having elapsed. System after Claim 1 wherein the processor is further programmed to identify the battery identifier with a vehicle bus via a connection of a system containing the high voltage battery. System after Claim 1 The processor is further programmed to identify the battery identifier in response to receiving bar code information scanned from the battery. Method, comprising: in response to detecting a change in a battery identifier of a battery of a vehicle, prompting a server connected to the vehicle via a wide area network to send a battery profile corresponding to the battery identifier to the vehicle; and Use of the battery profile to customize a battery control strategy for the battery. Method according to Claim 8 , further comprising updating the battery profile in response to power measurements of the battery. Method according to Claim 9 further comprising sending the updated battery profile to the server in response to a predefined time period having elapsed since a previous transmission of the battery profile to the server. Method according to Claim 9 further comprising sending the updated battery profile to the server in response to a predefined distance having been traveled to the server since a previous transmission of the battery profile. Method according to Claim 8 , further comprising: keeping the battery identifier in a data memory of a controller; and detecting a change of the battery identifier in response to reading the battery identifier from the battery and comparing the read battery identifier with the stored battery identifier. Method according to Claim 8 wherein the battery is a traction battery configured to power one or more electric motors of the vehicle. Method according to Claim 8 , further comprising utilizing the battery profile to adapt a battery control strategy of the vehicle to characteristics of the battery.

Images