Apparatus, methods, and systems for tracking vehicle battery usage with a blockchain

Apparatus, systems, and methods for tracking vehicle battery usage with a blockchain. One such method includes detecting, using one or more sensors, one or more operating parameters of a vehicle, at least one of the one or more operating parameters being associated with a battery of the vehicle. A battery-critical event is identified based on the detected one or more operating parameters of the vehicle. Information associated with the detected one or more operating parameters of the vehicle is communicated via a network and to a central server; information associated with the detected one or more operating parameters of the vehicle and the identified battery-critical event is aggregated in a blockchain using the central server. The information associated with the detected one or more operating parameters of the vehicle and the identified battery-critical event is queried from the blockchain to ascertain a usage history of the battery.

TECHNICAL FIELD

The present disclosure relates generally to tracking battery usage and, more particularly, to apparatus, systems, and methods for tracking vehicle battery usage with a blockchain.

BACKGROUND

Logging the age of a vehicle's battery together with the number of charge cycles the battery has been through provides only a limited understanding of the battery's usage history. However, with the increasing availability of electric vehicles in the marketplace, a finer understanding of a battery's usage history is needed. Moreover, once the original vehicle in which the battery was installed has worn out or been otherwise decommissioned, the vehicle battery may be recycled to power another vehicle, making it difficult to track the usage history of a particular battery over time. It would therefore be desirable to provide a more detailed (and immutable) accounting of vehicle battery usage to better assess a residual value of the battery. Therefore, what is needed is an apparatus, system, and/or method that addresses one or more of the foregoing issues, and/or one or more other issues.

SUMMARY

The present disclosure provides apparatus, systems, and methods for tracking vehicle battery usage with a blockchain. A generalized method for tracking vehicle battery usage with a blockchain includes detecting, using one or more sensors, one or more operating parameters of a vehicle, at least one of the one or more operating parameters being associated with a battery of the vehicle. A battery-critical event is identified based on the detected one or more operating parameters of the vehicle. Information associated with the detected one or more operating parameters of the vehicle is communicated via a network and to a central server; information associated with the detected one or more operating parameters of the vehicle and the identified battery-critical event is aggregated in a blockchain using the central server. The information associated with the detected one or more operating parameters of the vehicle and the identified battery-critical event is queried from the blockchain to ascertain a usage history of the battery.

A generalized system for tracking vehicle battery usage with a blockchain includes a vehicle having a battery adapted to power the vehicle. One or more sensors are adapted to detect one or more operating parameters of the vehicle, at least one of the one or more operating parameters being associated with the battery of the vehicle. Information associated with the detected one or more operating parameters of the vehicle is adapted to be communicated to a central server via a network. Information associated with the detected one or more operating parameters of the vehicle and a battery-critical event is adapted to be aggregated in a blockchain using the central server, and the information associated with the detected one or more operating parameters of the vehicle and the identified battery-critical event is adapted to be queried from the blockchain to ascertain a usage history of the battery. The battery-critical event is identified based on the detected one or more operating parameters of the vehicle.

A generalized apparatus for tracking vehicle battery usage with a blockchain includes a non-transitory computer readable medium and a plurality of instructions stored on the non-transitory computer readable medium and executable by one or more processors. The plurality of instructions include instructions that, when executed, cause the one or more processors to detect, using one or more sensors, one or more operating parameters of a vehicle, at least one of the one or more operating parameters being associated with a battery of the vehicle. The plurality of instructions also include instructions that, when executed, cause the one or more processors to identify, based on the detected one or more operating parameters of the vehicle, a battery-critical event. The plurality of instructions also include instructions that, when executed, cause the one or more processors to communicate, via a network and to a central server, information associated with the detected one or more operating parameters of the vehicle. The plurality of instructions also include instructions that, when executed, cause the one or more processors to aggregate, using the central server and in a blockchain, information associated with the detected one or more operating parameters of the vehicle and the identified battery-critical event. Finally, the plurality of instructions also include instructions that, when executed, cause the one or more processors to query, from the blockchain, the information associated with the detected one or more operating parameters of the vehicle and the identified battery-critical event to ascertain a usage history of the battery.

DETAILED DESCRIPTION

The present disclosure leverages the trusted characteristics of a blockchain to provide a detailed accounting of how a vehicle's battery has been used in order to better assess a residual value of the battery. In some embodiments, this includes, but is not limited to, logging the number of charge cycles and battery age. More particularly, the present system uses a blockchain to track aspects specific to electric vehicles. For example, the present system may track cycles of an electric vehicle's battery including charges/discharges and/or other conditions associated with the battery such as, for example, overcharges, general characteristics, location, environmental conditions over the battery's lifespan, accident history, and the like. In some embodiments, the battery may include a unique identifier (e.g., an RFID tag) that is used to link information logged within the blockchain to the battery and to a vehicle within which the battery is installed. The blockchain can include a distributed application and a trusted interface within the vehicle that automatically logs the relevant information as the battery is used. In various embodiments, the system can score the usage to provide a quick reference about the current condition of the battery along with providing the complete usage history. In further aspects, the system can specifically identify any critical combination of events that may lead to degradation of battery life (e.g., exposure to extreme heat when overcharged, wet conditions when charging battery, etc.). The system can then assess this information to learn characteristics of battery life, know when to change the battery, and assess battery value when the vehicle or battery is sold.

Referring toFIG. 1, in an embodiment, a battery usage tracking system is generally referred to by the reference numeral100and includes a vehicle105, such as an automobile, and a vehicle control unit110located on the vehicle105. The vehicle105may include a front portion115a(including a front bumper), a rear portion115b(including a rear bumper), a right side portion115c(including a right front quarter panel, a right front door, a right rear door, and a right rear quarter panel), a left side portion115d(including a left front quarter panel, a left front door, a left rear door, and a left rear quarter panel), and wheels115e. A communication module120is operably coupled to, and adapted to be in communication with, the vehicle control unit110. The communication module120is adapted to communicate wirelessly with a central server125via a network130(e.g., a 3G network, a 4G network, a 5G network, a Wi-Fi network, or the like). The central server125includes a blockchain135adapted to track and account for, among other things, the vehicle105's battery usage, as will be described in further detail below.

An operational equipment engine140is operably coupled to, and adapted to be in communication with, the vehicle control unit110. The operational equipment engine140is connectable to a charging station145, as will be described in further detail below. A sensor engine150is operably coupled to, and adapted to be in communication with, the vehicle control unit110. The sensor engine150is adapted to monitor various components of, for example, the operational equipment engine140, as will be described in further detail below. An interface engine155is operably coupled to, and adapted to be in communication with, the vehicle control unit110. In addition to, or instead of, being operably coupled to, and adapted to be in communication with, the vehicle control unit110, the communication module120, the operational equipment engine140, the sensor engine150, and/or the interface engine155may be operably coupled to, and adapted to be in communication with, another of the components via wired or wireless communication (e.g., via an in-vehicle network). In some embodiments, as inFIG. 1, the vehicle control unit110is adapted to communicate with the communication module120, the operational equipment engine140, the sensor engine150, and the interface engine155to at least partially control the interaction of data with and between the various components of the battery usage tracking system100.

The term “engine” is meant herein to refer to an agent, instrument, or combination of either, or both, agents and instruments that may be associated to serve a purpose or accomplish a task-agents and instruments may include sensors, actuators, switches, relays, power plants, system wiring, computers, components of computers, programmable logic devices, microprocessors, software, software routines, software modules, communication equipment, networks, network services, and/or other elements and their equivalents that contribute to the purpose or task to be accomplished by the engine. Accordingly, some of the engines may be software modules or routines, while others of the engines may be hardware and/or equipment elements in communication with the vehicle control unit110, the communication module120, the network130, the central server125, the charging station145, and/or the blockchain135.

Referring toFIG. 2, in an embodiment, an apparatus is generally referred to by the reference numeral160and includes several components of the battery usage tracking system100, which components are given the same reference numerals. Although not shown inFIG. 2, the apparatus160also includes the vehicle105, in which the other components of the apparatus160may be located either permanently or temporarily. The vehicle control unit110includes a processor165and a memory170. In some embodiments, as inFIG. 2, the communication module120, which is operably coupled to, and adapted to be in communication with, the vehicle control unit110, includes a transmitter175and a receiver180. In some embodiments, one or the other of the transmitter175and the receiver180may be omitted according to the particular application for which the communication module120is to be used. In some embodiments, the transmitter175and the receiver180are combined into a transceiver capable of both sending and receiving wireless signals. In any case, the transmitter175and the receiver180are adapted to send/receive data to/from the central server125, as indicated by arrow185.

In some embodiments, as inFIG. 2, the operational equipment engine140, which is operably coupled to, and adapted to be in communication with, the vehicle control unit110, includes a plurality of devices configured to facilitate driving of the vehicle105. In this regard, the operational equipment engine140may be designed to exchange communication with the vehicle control unit110, so as to not only receive instructions, but to provide information on the operation of the operational equipment engine140. For example, the operational equipment engine140may include a vehicle battery190, a motor195, a drivetrain200, a steering system205, and a braking system210. The vehicle battery190provides electrical power to the motor195to drive the wheels115eof the vehicle105via the drivetrain200. In some embodiments, in addition to providing power to the motor195to drive the wheels115eof the vehicle105via the drivetrain200, the vehicle battery190provides electrical power to another component of the operational equipment engine140, the vehicle control unit110, the communication module120, the sensor engine150, the interface engine155, or any combination thereof. In some embodiments, as inFIG. 2, the vehicle battery190includes a battery identification device215. The battery identification device215is adapted to communicate with one or more components of the sensor engine150, as will be described in further detail below. The battery identification device215stores data identifying the vehicle battery190such as, for example, manufacturing information (e.g., production date, production facility, etc.), battery characteristic(s) information, battery identification number information, electric vehicle compatibility information, or the like.

In some embodiments, as inFIG. 2, the sensor engine150, which is operably coupled to, and adapted to be in communication with, the vehicle control unit110, includes include devices such as sensors, meters, detectors, or other devices configured to measure or sense a parameter related to a driving operation of the vehicle105, as will be described in further detail below. For example, the sensor engine150may include a global positioning system220, a humidity sensor225, a temperature sensor230, a barometric pressure sensor235, a magnetic sensor240, a shock/vibration sensor245, a vehicle impact sensor250, an airbag sensor255, a braking sensor260, an accelerometer265, a speedometer270, a tachometer275, a battery load sensor280, a vehicle identification device285, or any combination thereof. The sensors or other detection devices are generally configured to sense or detect activity, conditions, and circumstances in an area to which the device has access. Sub-components of the sensor engine150may be deployed at any operational area where information on the driving of the vehicle105may occur. Readings from the sensor engine150are fed back to the vehicle control unit110. The reported data may include the sensed data, or may be derived, calculated, or inferred from sensed data. The vehicle control unit110may send signals to the sensor engine150to adjust the calibration or operating parameters of the sensor engine150in accordance with a control program in the vehicle control unit110. The vehicle control unit110is adapted to receive and process data from the sensor engine150or from other suitable source(s), and to monitor, store (e.g., in the memory170), and/or otherwise process (e.g., using the processor165) the received data.

The global positioning system220is adapted to track the location of the vehicle105and to communicate the location information to the vehicle control unit110. The humidity sensor225is adapted to detect environmental humidity levels and to communicate the humidity information to the vehicle control unit110. The temperature sensor230is adapted to detect environmental temperature levels and to communicate the temperature information to the vehicle control unit110. The barometric pressure sensor235is adapted to detect environmental barometric pressure levels and to communicate the barometric pressure information to the vehicle control unit110. The magnetic sensor240is adapted to detect the presence and strength of magnetic fields and to communicate the magnetic field information to the vehicle control unit110. The shock/vibration sensor245is adapted to detect shock and/or vibration and to communicate the shock and/or vibration information to the vehicle control unit110. In some embodiments, the humidity sensor225, the temperature sensor230, the barometric pressure sensor235, the magnetic sensor240, the shock/vibration sensor245, or any combination thereof are positioned at or near the vehicle battery190(e.g., in a battery compartment of the vehicle105) to monitor humidity, temperature, barometric pressure, magnetic field, shock, and/or vibration in or around the vehicle battery190. In addition to, or instead of, being positioned at or near the vehicle battery190to monitor conditions in or around the vehicle battery190, the humidity sensor225, the temperature sensor230, the barometric pressure sensor235, the magnetic sensor240, and/or the shock/vibration sensor245may be located elsewhere on the vehicle105to monitor ambient conditions.

The vehicle impact sensor250is adapted to detect an impact of the vehicle with another vehicle or object, and to communicate the impact information to the vehicle control unit110. In some embodiments, the vehicle impact sensor250is or includes a G-sensor. In some embodiments, the vehicle impact sensor250is or includes a microphone. In some embodiments, the vehicle impact sensor250includes multiple vehicle impact sensors, respective ones of which may be incorporated into the front portion115a(e.g., the front bumper), the rear portion115b(e.g., the rear bumper), the right side portion115c(e.g., the right front quarter panel, the right front door, the right rear door, and/or the right rear quarter panel), and/or the left side portion115d(e.g., the left front quarter panel, the left front door, the left rear door, and/or the left rear quarter panel) of the vehicle105. The airbag sensor255is adapted to activate and/or detect deployment of the vehicle105's airbag(s) and to communicate the airbag deployment information to the vehicle control unit110. The braking sensor260is adapted to monitor usage of the vehicle105's braking system210(e.g., an antilock braking system210) and to communicate the braking information to the vehicle control unit110.

The accelerometer265is adapted to monitor acceleration of the vehicle105and to communicate the acceleration information to the vehicle control unit110. The accelerometer265may be, for example, a two-axis accelerometer265or a three-axis accelerometer265. In some embodiments, the accelerometer265is associated with an airbag of the vehicle105to trigger deployment of the airbag. The speedometer270is adapted to monitor speed of the vehicle105and to communicate the speed information to the vehicle control unit110. In some embodiments, the speedometer270is associated with a display unit of the vehicle105such as, for example, a display unit of the interface engine155, to provide a visual indication of vehicle speed to a driver of the vehicle105. The tachometer275is adapted to monitor the working speed (e.g., in revolutions-per-minute) of the vehicle105's motor195and to communicate the angular velocity information to the vehicle control unit110. In some embodiments, the tachometer275is associated with a display unit of the vehicle105such as, for example, a display unit of the interface engine155, to provide a visual indication of the motor195's working speed to the driver of the vehicle105. The battery load sensor280is adapted to monitor charging, discharging, and/or overcharging of the vehicle battery190and to communicate the charging, discharging, and/or overcharging information to the vehicle control unit110.

In some embodiments, as inFIG. 2, the vehicle identification device285stores data identifying the vehicle105such as, for example, manufacturing information (e.g., make, model, production date, production facility, etc.), vehicle characteristic(s) information, vehicle identification number (“VIN”) information, battery compatibility information, or the like. The vehicle identification device285is adapted to communicate with the battery identification device215(or vice versa), as indicated by arrow286. For example, the vehicle identification device285may be adapted to communicate with the battery identification device215(or vice versa) via near field communication (NFC), radio-frequency identification (RFID), Bluetooth, infrared, proximity inference via, for example, global positioning system220(GPS) or triangulation, other indirect technologies, and/or any combination thereof. In some embodiments, in addition to, or instead of, the vehicle identification device285communicating with the battery identification device215(or vice versa), the vehicle identification device285and the battery identification device215each communicate with the vehicle control unit110. In any case, the identifying information communicated between the vehicle identification device285, the battery identification device215, and/or the vehicle control unit110may be relayed to the central server125(e.g., via the communication module120, the charging station145, and/or the network130) to link the vehicle battery190with the vehicle105so that the battery usage tracking system100can recognize and record if and when the vehicle battery190is exchanged for another vehicle battery or is placed in another vehicle (other than the vehicle105).

In some embodiments, the vehicle identification device285may be or include an active device and the battery identification device215may be or include a passive device so that the vehicle identification device285provides power (i.e., wirelessly) to the battery identification device215to read or “interrogate” the identifying data stored on the battery identification device215. In addition, or instead, the battery identification device215may be or include an active device and the vehicle identification device285may be or include a passive device so that the battery identification device215provides power (i.e., wirelessly) to the vehicle identification device285to read or “interrogate” the identifying data stored on the vehicle identification device285.

In some embodiments, as inFIG. 2, the interface engine155, which is operably coupled to, and adapted to be in communication with, the vehicle control unit110, includes at least one input and output device or system that enables a user to interact with the vehicle control unit110and the functions that the vehicle control unit110provides. For example, the interface engine155may include a display unit290and an input/output (“I/O”) device295. The display unit290may be, include, or be part of multiple display units. For example, in some embodiments, the display unit290may include one, or any combination, of a central display unit associated with a dash of the vehicle105, an instrument cluster display unit associated with an instrument cluster of the vehicle105, and/or a heads-up display unit associated with the dash and a windshield of the vehicle105; accordingly, as used herein the reference numeral290may refer to one, or any combination, of the display units. The I/O device295may be, include, or be part of a communication port (e.g., a USB port), a Bluetooth communication interface, a tough-screen display unit, soft keys associated with a dash, a steering wheel, or another component of the vehicle105, and/or similar components. Other examples of sub-components that may be part of the interface engine155include, but are not limited to, audible alarms, visual alerts, telecommunications equipment, and computer-related components, peripherals, and systems.

In some embodiments, a portable user device300belonging to an occupant of the vehicle105may be coupled to, and adapted to be in communication with, the interface engine155. For example, the portable user device300may be coupled to, and adapted to be in communication with, the interface engine155via the I/O device295(e.g., the USB port and/or the Bluetooth communication interface). In an embodiment, the portable user device300is a handheld or otherwise portable device which is carried onto the vehicle105by a user who is a driver or a passenger on the vehicle105. In addition, or instead, the portable user device300may be removably connectable to the vehicle105, such as by temporarily attaching the portable user device300to the dash, a center console, a seatback, or another surface in the vehicle105. In another embodiment, the portable user device300may be permanently installed in the vehicle105. In some embodiments, the portable user device300is, includes, or is part of one or more computing devices such as personal computers, personal digital assistants, cellular devices, mobile telephones, wireless devices, handheld devices, laptops, audio devices, tablet computers, game consoles, cameras, and/or any other suitable devices. In several embodiments, the portable user device300is a smartphone such as, for example, an iPhone® by Apple Incorporated.

In some embodiments, as inFIG. 2, the charging station145includes a power supply305, a transmitter310, a receiver315, a processor320, and a memory325. In some embodiments, one or the other of the transmitter310and the receiver315may be omitted according to the particular application for which the charging station145is to be used. In some embodiments, the transmitter310and the receiver315are combined into a transceiver capable of both sending and receiving wireless signals. In any case, the transmitter310and the receiver315are adapted to send/receive data to/from the central server125, as indicated by arrow326. The charging station145is adapted to recharge the vehicle battery190, as indicated by arrow328. In some embodiments, as inFIG. 2, before, during, and/or after the recharging of the battery by the charging station145, the charging station145is further adapted to send/receive data to/from the vehicle control unit110, as indicated by arrow330.

Referring toFIG. 3, with continuing reference toFIGS. 1 and 2, in operation, the vehicle control unit110and the operational equipment engine140receive driver input(s) to control driving operation(s) of the vehicle105(e.g., accelerating, braking, steering, etc.), as indicated by arrows332and334, respectively. In addition, or instead, the operational equipment engine140may receive control signals from the vehicle control unit110to control the driving operation(s) of the vehicle105, as indicated by arrow336. For example, the motor195, the drivetrain200, the steering system205, and/or the braking system210may receive the driver input(s) and/or the control signals from the vehicle control unit110to control the driving operation(s) of the vehicle105. In response to receiving the driver input(s) and/or the control signals from the vehicle control unit110, the operational equipment engine140executes the driving operation(s) of the vehicle105. The sensor engine150measures or senses various operating parameters related to the driving operation(s) of the vehicle105executed by the operational equipment engine140, as indicated by arrow338. In this regard, in some embodiments, as inFIG. 3, the sensor engine150includes battery sensor(s)345associated with the vehicle battery190and vehicle sensor(s)350associated with the vehicle105.

During the operational equipment engine140's execution of the driving operation(s), the battery sensor(s)345detect and monitor various operating parameters associated with the vehicle battery190. For example, in some embodiments, the battery sensor(s)345may be or include the humidity sensor225, the temperature sensor230, the barometric pressure sensor235, the magnetic sensor240, and/or the shock/vibration sensor245. Moreover, during the operational equipment engine140's execution of the driving operation(s), the vehicle sensor(s)350detect and monitor various operating parameters associated with the vehicle105. For example, in some embodiments, the vehicle sensor(s)350may be or include the global positioning system220, the vehicle impact sensor(s)250, the airbag sensor255, the braking sensor260, the accelerometer265, the speedometer270, and/or the tachometer275. The measured operating parameters associated with the vehicle battery190and/or the vehicle105are then communicated (e.g., intermittently or continuously) to the vehicle control unit110, as indicated by arrows352and354, respectively.

The vehicle control unit110may aggregate one or more of the measured operating parameters (i.e., associated with the vehicle battery190and/or the vehicle105) in the memory170. In addition, or instead, the processor165of the vehicle control unit110may execute programming stored in the memory170to identify one or more battery-critical event(s) based on the data received from the sensor engine150(i.e., the battery sensor(s)345and/or the vehicle sensor(s)350), and to aggregate operating parameters measured by the sensor engine150before, during, and/or after occurrence of the one or more battery-critical event(s) in the memory170. The one or more battery-critical event(s) identified using the vehicle control unit110may include, but is/are not limited to: long term unfavorable and/or harmful conditions in or around the vehicle battery190(e.g., insufficient or excess moisture, heat, cold, barometric pressure, shock, vibration, magnetic field, etc.) (as measured by the humidity sensor225, the temperature sensor230, the barometric pressure sensor235, the magnetic sensor240, the shock/vibration sensor245, the battery load sensor280, another sensor or system, or any combination thereof); charging, discharging, and/or overcharging events/patterns of the vehicle battery190(e.g., exposure to extreme heat when overcharged, wet conditions when charging, etc.) (as detected by the battery load sensor280, the humidity sensor225, the temperature sensor230, the barometric pressure sensor235, the magnetic sensor240, the shock/vibration sensor245, another sensor or system, or any combination thereof); local weather events/patterns (e.g., environmental precipitation, humidity, barometric pressure, etc.) (as detected by the humidity sensor225, the temperature sensor230, the barometric pressure sensor235, other sensors/systems external to the vehicle105such as, for example, local, regional, or national weather services, another sensor or system, or any combination thereof) correlated with the location of the vehicle105(e.g., as tracked by the global positioning system); and driving events/patterns of the vehicle105(e.g., accidents, driving habits, road conditions, etc.) (as detected by the shock/vibration sensor245, the vehicle impact sensor(s)250, the airbag sensor255, the braking sensor260, the accelerometer265, the speedometer270, the tachometer275, another sensor or system, or any combination thereof).

During the operational equipment engine140's execution of the driving operation, the vehicle control unit110communicates (e.g., continuously) one or more of the measured operating parameters to the interface engine155for display to the driver of the vehicle105, as indicated by arrow356. For example, the speed of the vehicle105as measured by the speedometer270may be displayed to the driver of the vehicle105via the display unit290. Furthermore, the communication module120relays (e.g., via the network130) (either continuously or intermittently, depending on connectivity with the network130) the operating parameters aggregated in the memory170to the central server125, as indicated by arrows358and360. In addition to, or instead of, the vehicle control unit110identifying the battery-critical event(s) before, during, or after which to aggregate data measured by the sensor engine150in the memory170, the central server125itself may identify the battery-critical event(s) based on data received from the communication module120, and aggregate operating parameters measured by the sensor engine150(and communicated to the central server125by the communication module120) before, during, and/or after occurrence of the one or more battery-critical event(s).

The charging station145is operably coupleable to the operational equipment engine140of the vehicle105to recharge the vehicle battery190with electrical power, as indicated by arrow362. More particularly, during the recharging of the vehicle105by the charging station145, power flows from the power supply305of the charging station145to the vehicle battery190of the vehicle105. Moreover, in some embodiments, as inFIG. 3, during the recharging of the vehicle105by the charging station145, the charging station145relays (e.g., via the network130) (either continuously or intermittently, depending on connectivity with the network130) the operating parameters aggregated in the memory170from the vehicle control unit110to the central server125, as indicated by arrows364and366. In addition to, or instead of, the vehicle control unit110identifying the battery-critical event(s) before, during, or after which to aggregate data measured by the sensor engine150in the memory170, the charging station145itself may identify (e.g., using programming executed by the processor320) the battery-critical event(s) based on data received from the vehicle control unit110, and aggregate operating parameters measured by the sensor engine150before, during, and/or after occurrence of the one or more battery-critical event(s) in the memory325. In such embodiments, the charging station145then communicates the operating parameters aggregated in the memory325to the central server125. Finally, the central server125communicates the aggregated data received from the communication module120and the charging station145to the blockchain135, as indicated by arrow367.

Referring toFIG. 4, with continuing reference toFIGS. 1-3, in an embodiment, multiple vehicles1051-i(which are substantially identical to the vehicle105) and/or multiple charging stations1451-i(which are substantially identical to the charging station145) may be part of or include the battery usage tracking system100. As a result, one or more operating parameters measured by sensor engines (which are substantially identical to the sensor engine150) of the respective vehicles1051-imay be communicated to the central server125and stored in the blockchain135. In this manner, the blockchain135may be used to track battery usage for an entire fleet of the vehicles1051-i. For example, as indicated by reference numeral368inFIG. 4, the blockchain135may aggregate data detected by the sensor engine of the vehicle1051and communicated to the central server125(e.g., via the network130) using a communication module (which is substantially identical to the communication module120) of the vehicle1051, the data being associated with battery-critical events having been identified using programming executed by the vehicle control unit (which is substantially identical to the vehicle control unit110) of the vehicle1051. For another example, as indicated by reference numeral370inFIG. 4, the blockchain135may aggregate data detected by the sensor engine of the vehicle1052and communicated to the central server125(e.g., via the network130) using the charging station1451, the data being associated with battery-critical events having been identified using programming executed by the charging station1451and/or the vehicle control unit (which is substantially identical to the vehicle control unit110) of the vehicle1051. Still other examples in which the blockchain135aggregates data communicated to the central server125from the vehicle1052, the charging station1453, the vehicle105i, and the charging station145iare also shown inFIG. 4.

Referring toFIG. 5, in an embodiment, a method of operating the battery usage tracking system100is generally referred to by the reference numeral400. The method400is carried out in response to receiving data readings from the global positioning system220, the humidity sensor225, the temperature sensor230, the barometric pressure sensor235, the magnetic sensor240, the shock/vibration sensor245, the vehicle impact sensor(s)250, the airbag sensor255, the braking sensor260, the accelerometer265, the speedometer270, the tachometer275, the battery load sensor280, the vehicle identification device285, the battery identification device215, or any combination thereof. The method400includes, at a step405, detecting, using one or more sensors, one or more operating parameters of a vehicle105, at least one of the one or more operating parameters being associated with a battery190of the vehicle105. At a step410, a battery-critical event is identified based on the detected one or more operating parameters of the vehicle105. In some embodiments, the battery-critical event is identified using the vehicle control unit110of the vehicle105; and the method further includes communicating, via the network130and to the central server125, information associated with the identified battery-critical event. For example, the information associated with the identified battery-critical event may be communicated, via the network130and to the central server125, using the communication module120of the vehicle105. In other embodiments, the battery-critical event is identified using the central server125. In still other embodiments, the battery-critical event is identified using the charging station145. In some embodiments, the method400further includes communicating, via the network130and to the central server125, information associated with the identified battery-critical event.

At a step415, information associated with the detected one or more operating parameters of the vehicle105is communicated via the network130and to the central server125. In some embodiments, the information associated with the detected one or more operating parameters of the vehicle105is communicated, via the network130and to the central server125, using the communication module120of the vehicle105. In some embodiments, the method further includes recharging, using the charging station145, the battery190of the vehicle105; and the information associated with the detected one or more operating parameters of the vehicle105is communicated, via the network130and to the central server125, using the charging station145. At a step420, information associated with the detected one or more operating parameters of the vehicle105and the identified battery-critical event is aggregated using the central server125and in the blockchain135. Finally, at a step425, the information associated with the detected one or more operating parameters of the vehicle105and the identified battery-critical event is queried from the blockchain135to ascertain a usage history of the battery190.

In some embodiments, the operation of the system100and/or the execution of the method400provides a finer understanding of the vehicle battery190's usage history. In some embodiments, the operation of the system100and/or the execution of the method400makes it easier to track the usage history of the vehicle battery190over time, even if the original vehicle in which the vehicle battery190was installed has worn out or been otherwise decommissioned and the vehicle battery190has been be recycled to power another vehicle. In some embodiments, the operation of the system100and/or the execution of the method400provides a more detailed (and immutable) accounting of the vehicle battery190's usage to better assess a residual value of the vehicle battery190.

Referring toFIG. 6, in an embodiment, a computing node1000for implementing one or more embodiments of one or more of the above-described elements, control units (e.g.,110), apparatus (e.g.,160), systems (e.g.,100), methods (e.g.,400) and/or steps (e.g.,405,410,415,420, and/or425), or any combination thereof, is depicted. The node1000includes a microprocessor1000a, an input device1000b, a storage device1000c, a video controller1000d, a system memory1000e, a display1000f, and a communication device1000gall interconnected by one or more buses1000h. In several embodiments, the storage device1000cmay include a floppy drive, hard drive, CD-ROM, optical drive, any other form of storage device or any combination thereof. In several embodiments, the storage device1000cmay include, and/or be capable of receiving, a floppy disk, CD-ROM, DVD-ROM, or any other form of computer-readable medium that may contain executable instructions. In several embodiments, the communication device1000gmay include a modem, network card, or any other device to enable the node1000to communicate with other nodes. In several embodiments, any node represents a plurality of interconnected (whether by intranet or Internet) computer systems, including without limitation, personal computers, mainframes, PDAs, smartphones and cell phones.

In several embodiments, one or more of the components of any of the above-described systems include at least the node1000and/or components thereof, and/or one or more nodes that are substantially similar to the node1000and/or components thereof. In several embodiments, one or more of the above-described components of the node1000and/or the above-described systems include respective pluralities of same components.

In several embodiments, a computer system typically includes at least hardware capable of executing machine readable instructions, as well as the software for executing acts (typically machine-readable instructions) that produce a desired result. In several embodiments, a computer system may include hybrids of hardware and software, as well as computer sub-systems.

In several embodiments, hardware generally includes at least processor-capable platforms, such as client-machines (also known as personal computers or servers), and hand-held processing devices (such as smart phones, tablet computers, personal digital assistants (PDAs), or personal computing devices (PCDs), for example). In several embodiments, hardware may include any physical device that is capable of storing machine-readable instructions, such as memory or other data storage devices. In several embodiments, other forms of hardware include hardware sub-systems, including transfer devices such as modems, modem cards, ports, and port cards, for example.

In several embodiments, software includes any machine code stored in any memory medium, such as RAM or ROM, and machine code stored on other devices (such as floppy disks, flash memory, or a CD ROM, for example). In several embodiments, software may include source or object code. In several embodiments, software encompasses any set of instructions capable of being executed on a node such as, for example, on a client machine or server.

In several embodiments, combinations of software and hardware could also be used for providing enhanced functionality and performance for certain embodiments of the present disclosure. In an embodiment, software functions may be directly manufactured into a silicon chip. Accordingly, it should be understood that combinations of hardware and software are also included within the definition of a computer system and are thus envisioned by the present disclosure as possible equivalent structures and equivalent methods.

In several embodiments, computer readable mediums include, for example, passive data storage, such as a random access memory (RAM) as well as semi-permanent data storage such as a compact disk read only memory (CD-ROM). One or more embodiments of the present disclosure may be embodied in the RAM of a computer to transform a standard computer into a new specific computing machine. In several embodiments, data structures are defined organizations of data that may enable an embodiment of the present disclosure. In an embodiment, a data structure may provide an organization of data, or an organization of executable code.

In several embodiments, any networks and/or one or more portions thereof, may be designed to work on any specific architecture. In an embodiment, one or more portions of any networks may be executed on a single computer, local area networks, client-server networks, wide area networks, internets, hand-held and other portable and wireless devices and networks.

In several embodiments, a database may be any standard or proprietary database software. In several embodiments, the database may have fields, records, data, and other database elements that may be associated through database specific software. In several embodiments, data may be mapped. In several embodiments, mapping is the process of associating one data entry with another data entry. In an embodiment, the data contained in the location of a character file can be mapped to a field in a second table. In several embodiments, the physical location of the database is not limiting, and the database may be distributed. In an embodiment, the database may exist remotely from the server, and run on a separate platform. In an embodiment, the database may be accessible across the Internet. In several embodiments, more than one database may be implemented.

In several embodiments, a plurality of instructions stored on a computer readable medium may be executed by one or more processors to cause the one or more processors to carry out or implement in whole or in part the above-described operation of each of the above-described elements, control units (e.g.,110), apparatus (e.g.,160), systems (e.g.,100), methods (e.g.,400) and/or steps (e.g.,405,410,415,420, and/or425), and/or any combination thereof. In several embodiments, such a processor may include one or more of the microprocessor1000a, any processor(s) that are part of the components of the above-described systems, and/or any combination thereof, and such a computer readable medium may be distributed among one or more components of the above-described systems. In several embodiments, such a processor may execute the plurality of instructions in connection with a virtual computer system. In several embodiments, such a plurality of instructions may communicate directly with the one or more processors, and/or may interact with one or more operating systems, middleware, firmware, other applications, and/or any combination thereof, to cause the one or more processors to execute the instructions.

A method has been disclosed. The method generally includes detecting, using one or more sensors, one or more operating parameters of a vehicle, at least one of the one or more operating parameters being associated with a battery of the vehicle; identifying, based on the detected one or more operating parameters of the vehicle, a battery-critical event; communicating, via a network and to a central server, information associated with the detected one or more operating parameters of the vehicle; aggregating, using the central server and in a blockchain, information associated with the detected one or more operating parameters of the vehicle and the identified battery-critical event; and querying, from the blockchain, the information associated with the detected one or more operating parameters of the vehicle and the identified battery-critical event to ascertain a usage history of the battery.

The foregoing method embodiment may include one or more of the following elements, either alone or in combination with one another:The information associated with the detected one or more operating parameters of the vehicle is communicated, via the network and to the central server, using a communication module of the vehicle.The battery-critical event is identified using a control unit of the vehicle; and the method further includes communicating, via the network and to the central server, information associated with the identified battery-critical event.The information associated with the identified battery-critical event is communicated, via the network and to the central server, using a communication module of the vehicle.The battery-critical event is identified using the central server.The method further includes recharging, using a charging station, the battery of the vehicle; and the information associated with the detected one or more operating parameters of the vehicle is communicated, via the network and to the central server, using the charging station.The battery-critical event is identified using the charging station; and the method further includes communicating, via the network and to the central server, information associated with the identified battery-critical event.

A system has also been disclosed. The system generally includes a vehicle having a battery adapted to power the vehicle; one or more sensors adapted to detect one or more operating parameters of the vehicle, at least one of the one or more operating parameters being associated with the battery of the vehicle; a central server to which information associated with the detected one or more operating parameters of the vehicle is adapted to be communicated via a network; and a blockchain in which information associated with the detected one or more operating parameters of the vehicle and a battery-critical event is adapted to be aggregated using the central server, and from which the information associated with the detected one or more operating parameters of the vehicle and the identified battery-critical event is adapted to be queried to ascertain a usage history of the battery; wherein the battery-critical event is identified based on the detected one or more operating parameters of the vehicle.

The foregoing system embodiment may include one or more of the following elements, either alone or in combination with one another:The vehicle has a communication module adapted to communicate the information associated with the detected one or more operating parameters of the vehicle to the central server via the network.The vehicle has a control unit adapted to identify the battery-critical event.The vehicle has a communication module adapted to communicate information associated with the identified battery-critical event to the central server via the network.The central server is adapted to identify the battery-critical event.The system further includes a charging station adapted to recharge the battery of the vehicle; and the charging station is adapted to communicate the information associated with the detected one or more operating parameters of the vehicle to the central server via the network.The charging station is adapted to identify the battery-critical event, and to communicate information associated with the identified battery-critical event to the central server via the network.

An apparatus has also been disclosed. The apparatus generally includes a non-transitory computer readable medium; and a plurality of instructions stored on the non-transitory computer readable medium and executable by one or more processors, the plurality of instructions including: instructions that, when executed, cause the one or more processors to detect, using one or more sensors, one or more operating parameters of a vehicle, at least one of the one or more operating parameters being associated with a battery of the vehicle; instructions that, when executed, cause the one or more processors to identify, based on the detected one or more operating parameters of the vehicle, a battery-critical event; instructions that, when executed, cause the one or more processors to communicate, via a network and to a central server, information associated with the detected one or more operating parameters of the vehicle; instructions that, when executed, cause the one or more processors to aggregate, using the central server and in a blockchain, information associated with the detected one or more operating parameters of the vehicle and the identified battery-critical event; and instructions that, when executed, cause the one or more processors to query, from the blockchain, the information associated with the detected one or more operating parameters of the vehicle and the identified battery-critical event to ascertain a usage history of the battery.

The foregoing apparatus embodiment may include one or more of the following elements, either alone or in combination with one another:When the instructions that cause the one or more processors to communicate, via the network and to the central server, the information associated with the detected one or more operating parameters of the vehicle are executed, the information associated with the detected one or more operating parameters of the vehicle is communicated, via the network and to the central server, using a communication module of the vehicle.When the instructions that cause the one or more processors to identify, based on the detected one or more operating parameters of the vehicle, the battery-critical event are executed, the battery-critical event is identified using a control unit of the vehicle; and the plurality of instructions further include instructions that, when executed, cause the one or more processors to communicate, via the network and to the central server, information associated with the identified battery-critical event.When the instructions that cause the one or more processors to communicate, via the network and to the central server, the information associated with the identified battery-critical event are executed, the information associated with the identified battery-critical event is communicated, via the network and to the central server, using a communication module of the vehicle.When the instructions that cause the one or more processors to communicate, via the network and to the central server, the information associated with the identified battery-critical event are executed, the battery-critical event is identified using the central server.The plurality of instructions further include instructions that, when executed, cause the one or more processors to recharge, using a charging station, the battery of the vehicle; and, when the instructions that cause the one or more processors to communicate, via the network and to the central server, the information associated with the detected one or more operating parameters of the vehicle are executed, the information associated with the detected one or more operating parameters of the vehicle is communicated, via the network and to the central server, using the charging station.When the instructions that cause the one or more processors to identify, based on the detected one or more operating parameters of the vehicle, the battery-critical event are executed, the battery-critical event is identified using the charging station; and the plurality of instructions further include instructions that, when executed, cause the one or more processors to communicate, via the network and to the central server, information associated with the identified battery-critical event.

It is understood that variations may be made in the foregoing without departing from the scope of the present disclosure.

In some embodiments, the elements and teachings of the various embodiments may be combined in whole or in part in some or all of the embodiments. In addition, one or more of the elements and teachings of the various embodiments may be omitted, at least in part, and/or combined, at least in part, with one or more of the other elements and teachings of the various embodiments.

Although some embodiments have been described in detail above, the embodiments described are illustrative only and are not limiting, and those skilled in the art will readily appreciate that many other modifications, changes and/or substitutions are possible in the embodiments without materially departing from the novel teachings and advantages of the present disclosure. Accordingly, all such modifications, changes, and/or substitutions are intended to be included within the scope of this disclosure as defined in the following claims.