DETERMINING A FUTURE USE OF A BATTERY

Abstract

An example operation includes one or more of: determining, by a vehicle that has been damaged, a health of a battery in the vehicle, wherein the health is related to a capacity and a physical condition of the battery; determining, by the vehicle, an accessibility of the battery; and determining, by the vehicle, a future use of the battery, based on the determined health and the determined accessibility.

Description

BACKGROUND

Vehicles or transports, such as cars, motorcycles, trucks, planes, trains, etc., generally provide transportation needs to occupants and/or goods in a variety of ways. Functions related to vehicles may be identified and utilized by various computing devices, such as a smartphone or a computer located on and/or off the vehicle.

SUMMARY

One example embodiment provides a method that includes one or more of determining, by a vehicle that has been damaged, a health of a battery in the vehicle, wherein the health is related to a capacity and a physical condition of the battery; determining, by the vehicle, an accessibility of the battery; and determining, by the vehicle, a future use of the battery, based on the determined health and the determined accessibility.

Another example embodiment provides a system that includes a memory communicably coupled to a processor, wherein the processor performs one or more of: determines, by a vehicle that has been damaged, a health of a battery in the vehicle, wherein the health is related to a capacity and a physical condition of the battery; determines, by the vehicle, an accessibility of the battery; and determines, by the vehicle, a future use of the battery, based on the determined health and the determined accessibility.

A further example embodiment provides a computer readable storage medium comprising instructions, that when read by a processor, cause the processor to perform one or more of determining, by a vehicle that has been damaged, a health of a battery in the vehicle, wherein the health is related to a capacity and a physical condition of the battery; determining, by the vehicle, an accessibility of the battery; and determining, by the vehicle, a future use of the battery, based on the determined health and the determined accessibility.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates an example of a system diagram, according to example embodiments.

FIG. 1B illustrates an example of a flow diagram, according to example embodiments.

FIG. 2A illustrates a vehicle network diagram, according to example embodiments.

FIG. 2B illustrates another vehicle network diagram, according to example embodiments.

FIG. 2C illustrates yet another vehicle network diagram, according to example embodiments.

FIG. 2D illustrates a further vehicle network diagram, according to example embodiments.

FIG. 2E illustrates a flow diagram, according to example embodiments.

FIG. 2F illustrates another flow diagram, according to example embodiments.

FIG. 3A illustrates a machine learning network diagram, according to example embodiments.

FIG. 3B illustrates another machine learning network diagram, according to example embodiments.

FIG. 3C illustrates yet another machine learning network diagram, according to example embodiments.

FIG. 3D illustrates a further machine learning integrated development environment diagram, according to example embodiments.

FIG. 3E illustrates a machine learning network diagram, according to example embodiments.

FIG. 4A illustrates a diagram depicting electrification of one or more elements, according to example embodiments.

FIG. 4B illustrates a diagram depicting interconnections between different elements, according to example embodiments.

FIG. 4C illustrates a further diagram depicting interconnections between different elements, according to example embodiments.

FIG. 4D illustrates yet a further diagram depicting interconnections between elements, according to example embodiments.

FIG. 4E illustrates yet a further diagram depicting an example of vehicles performing secured Vehicle to Vehicle (V2V) communications using security certificates, according to example embodiments.

FIG. 5A illustrates an example vehicle configuration for managing database transactions associated with a vehicle, according to example embodiments.

FIG. 5B illustrates an example blockchain group, according to example embodiments.

FIG. 5C illustrates an example interaction between elements and a blockchain, according to example embodiments.

FIG. 5D illustrates an example data block interaction, according to example embodiments.

FIG. 5E illustrates a blockchain network diagram, according to example embodiments.

FIG. 5F illustrates an example new data block, according to example embodiments.

FIG. 6 illustrates an example system that supports one or more of the example embodiments.

DETAILED DESCRIPTION

It will be readily understood that the instant components, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of at least one of a method, apparatus, computer readable storage medium and system, as represented in the attached figures, is not intended to limit the scope of the application as claimed but is merely representative of selected embodiments. Multiple embodiments depicted herein are not intended to limit the scope of the solution. The computer-readable storage medium may be a non-transitory computer readable media or a non-transitory computer readable storage medium.

Communications between the vehicle(s) and certain entities, such as remote servers, other vehicles, and local computing devices (e.g., smartphones, personal computers, vehicle-embedded computers, etc.) may be sent and/or received and processed by one or more ‘components’ which may be hardware, firmware, software, or a combination thereof. The components may be part of any of these entities or computing devices or certain other computing devices. In one example, consensus decisions related to blockchain transactions may be performed by one or more computing devices or components (which may be any element described and/or depicted herein) associated with the vehicle(s) and one or more of the components outside or at a remote location from the vehicle(s).

The instant features, structures, or characteristics described in this specification may be combined in any suitable manner in one or more embodiments. For example, the usage of the phrases “example embodiments,” “some embodiments,” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one example. Thus, appearances of the phrases “example embodiments”, “in some embodiments”, “in other embodiments,” or other similar language, throughout this specification can all refer to the same embodiment. Thus, these embodiments may work in conjunction with any of the other embodiments, may not be functionally separate, and the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the figures, any connection between elements can permit one-way and/or two-way communication, even if the depicted connection is a one-way or two-way arrow. In the instant solution, a vehicle may include one or more of cars, trucks, Internal Combustion Engine (ICE) vehicles, battery electric vehicle (BEV), e-Palettes, fuel cell bus, motorcycles, scooters, bicycles, boats, recreational vehicles, planes, drones, Unmanned Aerial Vehicle (UAV) and any object that may be used to transport people and/or goods from one location to another.

In addition, while the term “message” may have been used in the description of embodiments, other types of network data, such as, a packet, frame, datagram, etc. may also be used. Furthermore, while certain types of messages and signaling may be depicted in exemplary embodiments they are not limited to a certain type of message and signaling.

Example embodiments provide methods, systems, components, non-transitory computer readable media, devices, and/or networks, which provide at least one of a transport (also referred to as a vehicle or car herein), a data collection system, a data monitoring system, a verification system, an authorization system, and a vehicle data distribution system. The vehicle status condition data received in the form of communication messages, such as wireless data network communications and/or wired communication messages, may be processed to identify vehicle status conditions and provide feedback on the condition and/or changes of a vehicle. In one example, a user profile may be applied to a particular vehicle to authorize a current vehicle event, service stops at service stations, to authorize subsequent vehicle rental services, and enable vehicle-to-vehicle communications.

Within the communication infrastructure, a decentralized database is a distributed storage system which includes multiple nodes that communicate with each other. A blockchain is an example of a decentralized database, which includes an append-only immutable data structure (i.e., a distributed ledger) capable of maintaining records between untrusted parties. The untrusted parties are referred to herein as peers, nodes, or peer nodes. Each peer maintains a copy of the database records, and no single peer can modify the database records without a consensus being reached among the distributed peers. For example, the peers may execute a consensus protocol to validate blockchain storage entries, group the storage entries into blocks, and build a hash chain via the blocks. This process forms the ledger by ordering the storage entries, as is necessary, for consistency. In public or permissionless blockchains, anyone can participate without a specific identity. Public blockchains can involve crypto-currencies and use consensus-based on various protocols such as proof of work (PoW). Conversely, a permissioned blockchain database can secure interactions among a group of entities, which share a common goal, but which do not or cannot fully trust one another, such as businesses that exchange funds, goods, information, and the like. The instant solution can function in a permissioned and/or a permissionless blockchain setting.

Smart contracts are trusted distributed applications which leverage tamper-proof properties of the shared or distributed ledger (which may be in the form of a blockchain) and an underlying agreement between member nodes, which is referred to as an endorsement or endorsement policy. In general, blockchain entries are “endorsed” before being committed to the blockchain while entries, which are not endorsed, are disregarded. A typical endorsement policy allows smart contract executable code to specify endorsers for an entry in the form of a set of peer nodes that are necessary for endorsement. When a client sends the entry to the peers specified in the endorsement policy, the entry is executed to validate the entry. After validation, the entries enter an ordering phase in which a consensus protocol produces an ordered sequence of endorsed entries grouped into blocks.

Nodes are the communication entities of the blockchain system. A “node” may perform a logical function in the sense that multiple nodes of different types can run on the same physical server. Nodes are grouped in trust domains and are associated with logical entities that control them in various ways. Nodes may include different types, such as a client or submitting-client node, which submits an entry-invocation to an endorser (e.g., peer), and broadcasts entry proposals to an ordering service (e.g., ordering node). Another type of node is a peer node, which can receive client submitted entries, commit the entries, and maintain a state and a copy of the ledger of blockchain entries. Peers can also have the role of an endorser. An ordering-service-node or orderer is a node running the communication service for all nodes and which implements a delivery guarantee, such as a broadcast to each of the peer nodes in the system when committing entries and modifying a world state of the blockchain. The world state can constitute the initial blockchain entry, which normally includes control and setup information.

A ledger is a sequenced, tamper-resistant record of all state transitions of a blockchain. State transitions may result from smart contract executable code invocations (i.e., entries) submitted by participating parties (e.g., client nodes, ordering nodes, endorser nodes, peer nodes, etc.). An entry may result in a set of asset key-value pairs being committed to the ledger as one or more operands, such as creates, updates, deletes, and the like. The ledger includes a blockchain (also referred to as a chain), which stores an immutable, sequenced record in blocks. The ledger also includes a state database, which maintains a current state of the blockchain. There is typically one ledger per channel. Each peer node maintains a copy of the ledger for each channel of which they are a member.

A chain is an entry log structured as hash-linked blocks, and each block contains a sequence of N entries where N is equal to or greater than one. The block header includes a hash of the blocks' entries, as well as a hash of the prior block's header. In this way, all entries on the ledger may be sequenced and cryptographically linked together. Accordingly, it is not possible to tamper with the ledger data without breaking the hash links. A hash of a most recently added blockchain block represents every entry on the chain that has come before it, making it possible to ensure that all peer nodes are in a consistent and trusted state. The chain may be stored on a peer node file system (i.e., local, attached storage, cloud, etc.), efficiently supporting the append-only nature of the blockchain workload.

The current state of the immutable ledger represents the latest values for all keys that are included in the chain entry log. Since the current state represents the latest key values known to a channel, it is sometimes referred to as a world state. Smart contract executable code invocations execute entries against the current state data of the ledger. To make these smart contract executable code interactions efficient, the latest values of the keys may be stored in a state database. The state database may be simply an indexed view into the chain's entry log and can therefore be regenerated from the chain at any time. The state database may automatically be recovered (or generated if needed) upon peer node startup and before entries are accepted.

A blockchain is different from a traditional database in that the blockchain is not a central storage but rather a decentralized, immutable, and secure storage, where nodes must share in changes to records in the storage. Some properties that are inherent in blockchain and which help implement the blockchain include, but are not limited to, an immutable ledger, smart contracts, security, privacy, decentralization, consensus, endorsement, accessibility, and the like.

Example embodiments provide a service to a particular vehicle and/or a user profile that is applied to the vehicle. For example, a user may be the owner of a vehicle or the operator of a vehicle owned by another party. The vehicle may require service at certain intervals, and the service needs may require authorization before permitting the services to be received. Also, service centers may offer services to vehicles in a nearby area based on the vehicle's current route plan and a relative level of service requirements (e.g., immediate, severe, intermediate, minor, etc.). The vehicle needs may be monitored via one or more vehicle and/or road sensors or cameras, which report sensed data to a central controller computer device in and/or apart from the vehicle. This data is forwarded to a management server for review and action. A sensor may be located on one or more of the interior of the vehicle, the exterior of the vehicle, on a fixed object apart from the vehicle, and on another vehicle proximate the vehicle. The sensor may also be associated with the vehicle's speed, the vehicle's braking, the vehicle's acceleration, fuel levels, service needs, the gear-shifting of the vehicle, the vehicle's steering, and the like. A sensor, as described herein, may also be a device, such as a wireless device in and/or proximate to the vehicle. Also, sensor information may be used to identify whether the vehicle is operating safely and whether an occupant has engaged in any unexpected vehicle conditions, such as during a vehicle access and/or utilization period. Vehicle information collected before, during and/or after a vehicle's operation may be identified and stored in a transaction on a shared/distributed ledger, which may be generated and committed to the immutable ledger as determined by a permission-granting consortium, and thus in a “decentralized” manner, such as via a blockchain membership group.

Each interested party (i.e., owner, user, company, agency, etc.) may want to limit the exposure of private information, and therefore the blockchain and its immutability can be used to manage permissions for each particular user vehicle profile. A smart contract may be used to provide compensation, quantify a user profile score/rating/review, apply vehicle event permissions, determine when service is needed, identify a collision and/or degradation event, identify a safety concern event, identify parties to the event and provide distribution to registered entities seeking access to such vehicle event data. Also, the results may be identified, and the necessary information can be shared among the registered companies and/or individuals based on a consensus approach associated with the blockchain. Such an approach may not be implemented on a traditional centralized database.

Various driving systems of the instant solution can utilize software, an array of sensors as well as machine learning functionality, light detection and ranging (Lidar) projectors, radar, ultrasonic sensors, etc. to create a map of terrain and road that a vehicle can use for navigation and other purposes. In some embodiments, global positioning system (GPS), maps, cameras, sensors, and the like can also be used in autonomous vehicles in place of Lidar.

The instant solution includes, in certain embodiments, authorizing a vehicle for service via an automated and quick authentication scheme. For example, driving up to a charging station or fuel pump may be performed by a vehicle operator or an autonomous vehicle and the authorization to receive charge or fuel may be performed without any delays provided the authorization is received by the service and/or charging station. A vehicle may provide a communication signal that provides an identification of a vehicle that has a currently active profile linked to an account that is authorized to accept a service, which can be later rectified by compensation. Additional measures may be used to provide further authentication, such as another identifier may be sent from the user's device wirelessly to the service center to replace or supplement the first authorization effort between the vehicle and the service center with an additional authorization effort.

Data shared and received may be stored in a database, which maintains data in one single database (e.g., database server) and generally at one particular location. This location is often a central computer, for example, a desktop central processing unit (CPU), a server CPU, or a mainframe computer. Information stored on a centralized database is typically accessible from multiple different points. A centralized database is easy to manage, maintain, and control, especially for purposes of security because of its single location. Within a centralized database, data redundancy is minimized as a single storing place of all data also implies that a given set of data only has one primary record. A blockchain may be used for storing vehicle-related data and transactions.

Any of the actions described herein may be performed by one or more processors (such as a microprocessor, a sensor, an Electronic Control Unit (ECU), a head unit, and the like), with or without memory, which may be located on-board the vehicle and/or off-board the vehicle (such as a server, computer, mobile/wireless device, etc.). The one or more processors may communicate with other memory and/or other processors on-board or off-board other vehicles to utilize data being sent by and/or to the vehicle. The one or more processors and the other processors can send data, receive data, and utilize this data to perform one or more of the actions described or depicted herein.

FIG. 1A illustrates a diagram of a system 100 in one set of embodiments. In some embodiments, the instant solution fully or partially executes in a memory 105 of a server 103, in a memory 110 of a processor 111 associated with a vehicle 102, or a memory of one or more other processors associated with devices and/or entities mentioned herein. In some embodiments, one or more of the server 103 or the processor 111 may include a microcontroller that contains one or more central processing unit (CPU) cores, along with program memory and programmable input/output peripherals. Program memory can be provided, for example, in the form of flash memory.

In some embodiments, referring to FIG. 1A, the vehicle 102 has been damaged. For example, the vehicle 102 may have been in an accident, or a mechanical failure of the vehicle 102 may have taken place. The processor 111 of the vehicle 102 determines a health of a battery 112 in the vehicle 102. For example, the health can be related to one or more of a capacity of the battery 112 or a physical condition of the battery 112. The battery 112 may be connected to a battery management system 113 configured to determine a State-of-Charge (SoC) and a charging capacity for the battery 112. The processor 111 may determine the health of the battery by communicating with the battery management system 113.

In some embodiments, referring to FIG. 1A, the processor 111 determines an accessibility of the battery 112. For example, the accessibility may comprise the relative ease or difficulty with which the battery 112 can be removed from the damaged vehicle 102, and/or a predicted amount of time that it will take to remove the battery 112 from the damaged vehicle 102. When the vehicle 102 is manufactured, the battery 112 may be placed under the floor inside the chassis of the vehicle 102 in a so-called skateboard configuration and mounted to the frame of the vehicle 102 using a plurality of bolts. The battery 112 may weigh several hundred pounds and measure several feet in length. An electrical service disconnect plug in the cabin of the vehicle 102 may have to be removed prior to performing any work on the battery 112. A high-voltage cable connector, hose connectors for battery coolant, a communication plug, and ground straps may all need to be detached from the battery 112 prior to removing the battery from the vehicle 102. When the vehicle 102 is damaged in an area proximate to the battery 112, the accessibility of the battery 112 may be degraded, relative to a situation where the vehicle 102 is damaged in an area that is not proximate to the battery 112. Likewise, the accessibility of the battery 112 may be degraded in situations where the damage to the vehicle 102 makes it difficult to access the electrical service disconnect plug, the high-voltage cable connector, the hose connectors, or the communication plug. Moreover, the accessibility of the battery 112 may be degraded in situations where the frame of the vehicle 102 has been bent or deformed, rendering the battery 112 difficult or impossible to remove from the vehicle 102.

Based on one or more of the determined health of the battery 112 or the determined accessibility of the battery 112, the processor 111 determines a future use of the battery. For example, when the battery 112 is in a good or better state of health and/or easily accessible, the future use of the battery 112 may comprise using the battery 112 on another vehicle 106. When the battery 112 is in a moderate state of health and/or moderately accessible, the future use of the battery 112 may comprise using the battery 112 in a battery pack 119 of an on-premises energy storage device 107. When the battery 112 is in a poor state of health and/or difficult to access, the materials in the battery 112 may be reclaimed.

In some embodiments, referring to FIG. 1A, in response to the vehicle 102 being damaged, the processor 111 gathers location data for the vehicle 102 from a GPS 114 unit. The processor 111 may transmit a notification over a network 104 to the server 103, where the notification includes a current location of the vehicle 102. In a further embodiment, the notification can be sent over the network 104 to a mobile device 137.

In some embodiments, referring to FIG. 1A, the processor 111 determines whether or not the charge capacity of the battery 112 is above a threshold. For example, the processor 111 may communicate with the battery management system 113 to receive data identifying the charge capacity of the battery 112. In response to the charge capacity being above the threshold, the processor 111 determines that the future use of the battery is to be deployed on another vehicle 106. In response to the charge capacity of the battery 112 being below the threshold by a first amount, the processor 111 determines that the battery 112 is to be used for at least one of a backup battery for another vehicle 106, or in the on-premises energy storage device 107. In response to the capacity being below the threshold by at least a second amount, the processor 111 determines that one or more materials are to be harvested from the battery 112. In some embodiments, the second amount is greater than the first amount.

In some embodiments, referring to FIG. 1A, in response to at least one of the physical condition or the capacity of the battery 112 being above a threshold, the processor 111 determines a first recommended amount of time for recovering the battery 112. The first recommended amount of time may be based at least in part on the determined accessibility of the battery 112. The processor 111 transmits a notification indicative of the first recommended amount of time for recovering the battery 112. In a further embodiment, the notification is transmitted over the network 104. In response to at least one of the physical condition or the capacity of the battery 112 being below the threshold, the processor 111 determines a second recommended amount of time for recovering the battery 112 based at least in part on the determined accessibility. The processor 111 transmits a notification indicative of the second recommended amount of time for recovering the battery 112. In a further embodiment, the notification is transmitted over the network 104. In a still further embodiment, the first recommended amount of time is greater than the second recommended amount of time.

In some embodiments, referring to FIG. 1A, in response to the vehicle 102 being damaged, the processor 111 gathers data associated with the battery 112 from the battery management system 113. The data may comprise one or more of the charge capacity of the battery 112, an age of the battery 112, the accessibility of the battery 112, or a charging history for the battery 112. The processor 111 transmits a notification to the server 103. The notification may include at least a portion of the data gathered by the processor 111 from the battery management system 113.

In some embodiments, referring to FIG. 1A, in response to the vehicle 102 being damaged, the processor 111 gathers data from a sensor 116 of the vehicle 102. The sensor 116 is configured to gather data associated with a condition of an occupant 115 of the vehicle 102. The processor 111 determines the physical condition of the battery 112 based at least in part on the location in the vehicle 102 of the occupant 115 and a threshold of the condition of the occupant 115. In a further embodiment, the processor 111 gathers data from a deployed air bag of the vehicle 102, the data being indicative of a location on the vehicle 102 of the deployed airbag. The processor 111 may determine the physical condition of the battery 112 based at least in part on the location on the vehicle 102 of the deployed airbag.

In some embodiments, referring to FIG. 1A, the processor 111 receives data from a telematics unit 118 of the vehicle 102. The processor 111 may send the received data over the network 104 to the server 103. The server 103 may determine a probability of an accident for the vehicle 102 by analyzing the received data. For example, the received data may comprise one or more of a speed of the vehicle 102, a change in speed of the vehicle 102 before the vehicle 102 was damaged, a change in speed of the vehicle 102 after the vehicle 102 was damaged, or a number of days for which the vehicle 102 has not been driven. The server 103 determines the physical condition of the battery 112 based on the determined probability of the accident. In an alternate embodiment, the processor 111 and the telematics unit 118 may be combined and integrated together into a single unit.

FIG. 1B illustrates an example of a flow diagram 150 in one set of embodiments. In some embodiments, the instant solution fully or partially executes in the memory 105 (FIG. 1A) of the server 103, in the memory 110 of the processor 111 associated with the vehicle 102, or a memory of one or more other processors associated with devices and/or entities mentioned herein. In some embodiments, one or more of the server 103 or the processor 111 may include a microcontroller that contains one or more central processing unit (CPU) cores, along with program memory and programmable input/output peripherals. Program memory can be provided, for example, in the form of flash memory.

In some embodiments, a crash of the vehicle 102 takes place (FIG. 1B, block 152). The processor 111 (FIG. 1A) receives data from the telematics unit 118 of the vehicle 102 and transmits at least a portion of this data over the network 104 to the server 103. The data may include a latest known location for the vehicle, a vehicle speed, a vehicle acceleration, an air bag status, and/or a number of air bags deployed (FIG. 1B, block 154). The server determines an amount of time that has elapsed since the latest data transmission of the telematics unit (block 156). The server determines a probability of the vehicle being totaled (block 158). The probability can be based on the data received from the telematics unit and/or the amount of time that has elapsed since data was last received from the telematics unit. Based on the probability of the vehicle being totaled, a test is performed at block 160 to ascertain whether or not an attempt should be made to locate the vehicle. If not, the program loops back to block 152 and waits until a crash of another vehicle takes place. The affirmative branch from block 160 leads to block 162 where the server searches one or more databases using a vehicle identifier such as a vehicle identification number (VIN) and/or a vehicle license plate number. For example, with reference to FIG. 1A, the one or more databases may comprise an insurance records database 123, a police/Department of Motor Vehicles (DMV) database 125, a National Motor Vehicle Title Information System (NMVTIS) database 127, a junk/salvage yards database 129, or a satellite images database 131.

Returning to FIG. 1B, a test is performed at block 164 to ascertain whether or not the server was able to find the vehicle in the one or more databases. If so, the program advances to block 166 where the server transmits the location of the totaled vehicle over the network 104 (FIG. 1A). The negative branch from block 164 (FIG. 1B) leads to block 168 where the server performs a secondary localization procedure by determining a make and a color for the vehicle. For example, the data previously sent to the server at block 154 may contain information that identifies a make and a color for the vehicle. At block 170, the server identifies one or more vehicle junk/salvage yards within a radius of the latest know vehicle location from the junk/salvage yards database 129 (FIG. 1A). At block 172 (FIG. 1B), the server obtains satellite images of the one or more identified junk/salvage yards from the satellite images database 131 (FIG. 1A). In a further embodiment, the images in the satellite images database 131 are updated on a regular, periodic, or recurring basis. At block 174 (FIG. 1B), the server transmits the satellite images to a deep neural network 133 (FIG. 1A) that performs an image classification procedure to identify the vehicle. The program then advances to block 166 (FIG. 1B) where the server transmits the location of the vehicle over the network.

In one embodiment, the system encompasses an automatic accident response communication system. The system is equipped with sensors and algorithms to detect an accident immediately when it occurs. The sensors include impact sensors, sudden deceleration data, and other telematics indicators. Upon detecting an accident, the system assesses the battery's health, focusing on immediate risks such as the potential for fire, chemical leakage, or electrical hazards. The assessment considers factors like battery integrity, temperature, and any breaches in the battery casing. The system sends an automated alert to local emergency services. The alert includes critical information such as the vehicle's exact location (using GPS data), the nature and severity of the accident, and a detailed report on the battery's condition. The data ensures that responders are adequately prepared for the specific risks of the situation, especially crucial for electric vehicle (EV) related accidents. As emergency services mobilize, the system continues to transmit real-time data, including live updates on battery conditions, potential changes in the risk profile (like increasing temperatures), and other relevant accident scene information. The system provides immediate safety instructions to the vehicle's occupants, tailored to the specific accident scenario. For example, if the battery is compromised, instructions may include evacuating the vehicle safely or avoiding specific actions that may exacerbate risks. The system also interfaces with smart city traffic management systems. For example, it may automatically signal traffic lights to change, create a clear path for emergency vehicles, or update digital road signs to warn other drivers. The system can also facilitate necessary reporting for insurance and legal purposes, including transmitting a detailed accident report to the owner's insurance provider or relevant legal authorities, streamlining the post-accident administrative process. The system collects and analyzes data to identify patterns and potential improvements in vehicle design, battery safety, and accident response protocols.

The system integrates vehicle battery health and accident data for streamlined insurance processing in one embodiment. The system is equipped with sensors and software to detect accidents immediately. Upon detection, it collects comprehensive data, including the severity of the impact, location, and time of the accident. Simultaneously, it assesses the health and damage to the vehicle's battery, which is crucial for EVs. Post-accident, the system performs a detailed analysis of the vehicle's battery health, assessing any damage to the battery, potential risks (like fire or chemical leakage), and the overall impact on the battery's future functionality. The system considers factors like battery integrity, temperature, and electrical stability. The system automatically notifies the vehicle owner's insurance provider. The notification includes all relevant accident data, a comprehensive report on the battery's condition, and an initial estimate of repair costs and implications for battery replacement or repair. The system streamlines the claims process by providing accurate and detailed information directly to the insurance provider. The system also interfaces with the insurance provider's database to assist in adjusting insurance premiums based on real-time data. For example, if a vehicle's battery consistently shows excellent health and the vehicle is involved in fewer accidents, this may positively impact insurance premiums.

In one embodiment, a vehicle communicates battery health and accident status to nearby vehicles. The system immediately assesses the battery's condition when a vehicle is involved in an accident. The assessment includes checking for potential hazards like battery fires, chemical leaks, or electrical risks. The system automatically broadcasts this information to nearby vehicles through a Vehicle-to-Vehicle (V2V) network protocol. Vehicles receiving the data can then alert their drivers of potential hazards ahead. This is particularly crucial for EV-related accidents, where battery-related hazards may not be immediately visible. It can prevent secondary accidents and allow drivers to take alternate routes. The system also communicates with emergency response teams, providing them with real-time data about the accident scene, including specific risks associated with the damaged EV's battery, ensuring that first responders arrive at the scene fully informed and prepared for the specific challenges they might face. The V2V network also integrates with smart traffic management systems. Upon detecting an accident, it automatically signals changes in traffic light patterns or updates digital road signs, helping to manage traffic flow and reduce the risk of congestion or further accidents. The system collects and stores data regarding the battery's condition before and after the accident, which manufacturers and safety regulators can use to understand the impact of collisions on EV batteries and improve vehicle and battery designs.

In one embodiment, the system estimates a vehicle's resale value based on its battery health over its lifespan. The system continuously monitors and records the EV's battery health, including tracking battery capacity, charge cycles, temperature exposures, and any incidents of damage or degradation. The vehicle's onboard diagnostics and battery management systems collect the data. The collected battery health data is integrated with the vehicle's overall history report, which includes maintenance records, accident history, mileage, and other pertinent information, creating a comprehensive profile of the vehicle's condition over time. The system employs a sophisticated algorithm that analyzes the battery health data in conjunction with the vehicle's history to estimate its resale value. The algorithm considers factors like the expected battery life, potential future maintenance costs, and the impact of battery condition on overall vehicle performance. The system also accesses real-time market data, comparing similar models and conditions to ensure the estimated resale value aligns with current market trends. The comparison accounts for regional variations in demand and pricing for used EVs. The system integrates with online car-selling platforms and dealerships, allowing instant valuation of a used EV when listed for sale and providing potential buyers with immediate and accurate pricing information. The system can generate customizable reports tailored to different users' needs. For example, a detailed report for a potential buyer might focus on the battery's remaining lifespan and performance, while a dealer might receive a report emphasizing market trends and pricing. The algorithm and data models are regularly updated to reflect new insights from the EV market and advancements in battery technology.

In one embodiment, the system automatically connects with roadside assistance and repair services when a vehicle accident happens. When a vehicle is involved in a collision, the system immediately assesses the damage, paying special attention to the state of the EV's battery. This involves evaluating the extent of physical damage, potential safety hazards like battery leaks or electrical risks, and the overall functionality of the battery post-incident. Once the assessment is complete, the system activates a communication protocol with a network of roadside assistance providers and repair facilities. The protocol is designed to automatically suggest service stations capable of handling the specific type of damage identified, particularly specialized battery damage in the case of EVs. The system considers the accident's location, the availability of nearby services, and their capability to address the specific issues of the damaged vehicle. In scenarios where the battery is severely damaged and poses a risk to safe transportation, the system coordinates with specialized services for battery disposal or recycling. For less severe damages, the system facilitates the immediate ordering of necessary parts and schedules repairs to minimize vehicle downtime and ensure a faster return to functionality. The system is designed to be interactive, allowing vehicle owners to track the repair process, receive updates, and even reschedule appointments as needed. The system can also be used for regular maintenance and service needs. The system can monitor the vehicle's health over time, scheduling regular check-ups and maintenance work, thus ensuring the vehicle remains in optimal condition.

In one embodiment, the system determines the health of a battery related to a damaged vehicle. A damaged vehicle equipped with a battery management system and a telematics unit performs a series of determinations to assess the state and potential future applications of a battery housed within the vehicle. Upon an event that causes damage to the vehicle, the system initiates an assessment protocol. The system communicates with the battery management system to ascertain the health of the battery, wherein health encompasses the battery's capacity to hold charge as well as its physical integrity. Determining the battery's health is critical in deciding the subsequent steps in the protocol. The system, further considering the information from the telematics unit regarding the nature and extent of the vehicle's damage, evaluates the accessibility of the battery, determining how easily the battery can be extracted from the vehicle. Using the data on the battery's health and accessibility, the system then determines the future use of the battery. The decision-making process involves considering whether the battery is fit for use in another vehicle, suitable for incorporation into an on-premises energy storage device, or if its materials should be reclaimed due to poor health and accessibility. The system manages the outcome of the vehicle's battery post-damage, promoting efficient resource use and contributing to sustainability efforts in the automotive industry.

In one embodiment, the system gathers location data from a damaged vehicle and sends it to a remote destination. Following an event in which a vehicle is damaged, the vehicle, which includes a processor, a global positioning system (GPS), and a network communication interface, activates a location data gathering sequence through the GPS unit. The system, configured to communicate with the GPS unit, retrieves the current geographical coordinates of the vehicle. The geolocation retrieval is crucial, especially in scenarios where the vehicle may not be easily accessible post-damage, such as in remote areas or when the vehicle has been moved from the accident site. The system transmits a notification once the GPS unit determines the current location. The notification, containing the precise current location of the vehicle, is sent over a network to a remote server. The remote server, which may be operated by entities such as emergency services, insurance companies, or automotive assistance providers, receives the notification and processes it accordingly. This may involve dispatching recovery services to the vehicle's location, initiating insurance claim protocols, or notifying emergency contacts listed by the vehicle owner.

In one embodiment, the system determines the future use of a damaged vehicle's battery based on its capacity threshold. Upon experiencing damage, the system evaluates the battery's capacity. The battery management system communicates with the system and provides detailed data on the battery's state of charge (SoC) and overall capacity. The system, programmed with predetermined thresholds, compares the battery's current capacity against the thresholds to determine the future use of the battery. When the battery's capacity is above the predetermined threshold, the system designates the battery as suitable for deployment in another vehicle. The decision is based on the battery maintaining a sufficient health and charge capacity, indicating that it can reliably serve in a new vehicular environment. When the capacity is below the threshold, the system engages in further analysis. It determines if the capacity shortfall is within a first amount below the threshold. It may earmark the battery for alternative uses, including serving as a backup power source for another vehicle or integrating into an on-premises energy storage device. If the battery's capacity is below the threshold by a second or greater amount, the system, communicating further with the battery management system, concludes that the battery is unsuitable for energy storage purposes in its current state. The system identifies the battery as a candidate for material reclamation, where valuable components may be extracted and repurposed, thus contributing to sustainable practices.

In one embodiment, the system optimizes the recovery process of a damaged vehicle's battery. Upon the vehicle incurring damage, the system initiates a sequence to assess the health and accessibility of the battery, utilizing the vehicle's battery management system. The system, leveraging the data acquired from the battery management system, evaluates the battery's capacity and physical condition. When the battery's health is determined to be above a specified threshold, indicating a relatively undamaged state and sufficient energy capacity, the system calculates a first recommended amount of time for recovering the battery. The calculation considers the assessed accessibility of the battery, accounting for factors such as the extent of vehicle damage that may impede battery removal. The system then communicates the first recommended recovery time, sending a notification over a network to a remote server.

Conversely, the system computes a second recommended recovery time when the battery's health falls below the predetermined threshold, signifying diminished capacity or significant physical deterioration. The time frame is likely shorter, as the battery's compromised state may necessitate more immediate attention or indicate a reduced complexity in recovery due to the battery being deemed unsalvageable. The system transmits the second recommended recovery time to the remote server. The communication between the system, the vehicle's battery management system, and the remote server is a critical aspect of this embodiment, ensuring that recovery efforts can be properly planned and executed based on the precise conditions of the battery post-damage.

The system gathers and transmits battery data from a damaged vehicle in one embodiment. The system includes a vehicle that has suffered damage; after that, it takes action to assess and transmit information about its battery. Utilizing the vehicle's battery management system, the system gathers detailed data concerning the battery's condition. The data includes the battery's charge capacity, its age, how accessible it is for removal or service, and its charging history, which provides insights into its longevity and reliability. Once the data is collected, the system sends a notification from the vehicle to a remote server. The server is configured to receive the notification. The information transmitted in the notification is critical for remote diagnostics and determining whether to repair, repurpose, or recycle the battery. The vehicle's battery management system ensures accurate and up-to-date information about the battery's state is used in decision-making processes. The system's ability to send the data to a remote server helps prevent further damage or deterioration of the battery, optimizing the vehicle's maintenance and operational efficacy post-damage.

In one embodiment, the system gathers data on the condition of a damaged vehicle's occupant. The system, utilizing sensors on a vehicle, detects that the vehicle has been damaged, possibly due to an accident. The vehicle, equipped with a sensor designed to assess the condition of an occupant, collects data pertinent to the occupant's state. The sensor can also gauge the severity of the occupant's condition post-accident. The system receives the collected vehicle sensor data. Upon obtaining the information, the system evaluates the physical condition of the vehicle's battery, considering the occupant's location, the battery's position, and the severity of the occupant's condition as measured against predetermined thresholds. The implication here is that the impact on the occupant may correlate with the impact on the battery, wherein a more severe condition of the occupant might suggest a higher likelihood of significant battery damage.

Furthermore, the system is configured to communicate with the vehicle's battery management system to determine the battery's state of charge (SoC) and overall physical condition post-accident. For example, a severe accident may not only physically damage the battery but also impact its charge capacity and longevity. The system actively communicates with a remote server, transmitting data that includes the vehicle's location via GPS, the occupant's condition, and the battery's health. The comprehensive dataset allows the server to assist in decision-making concerning the battery's future use. For example, if the battery is deemed in good condition and easily accessible, it may be repurposed for another vehicle. Conversely, if the battery is in poor condition or inaccessible, the system might determine that material reclamation is the most appropriate action.

In one embodiment, the system determines the probability of a vehicle accident by analyzing vehicle telematics. A vehicle is equipped with an integrated telematics unit. When an incident occurs, resulting in damage to the vehicle, the telematics unit collects a variety of data, including the vehicle's speed, changes in speed both before and after the vehicle was damaged, and the number of days the vehicle has been stationary. The data is crucial in determining the likelihood of an accident having occurred and the potential severity of such an accident. In communication with the vehicle's telematics unit, the system receives and analyzes the data to determine the probability of an accident. The probability assessment is based on algorithms or criteria that consider the abruptness of speed changes, which can indicate the severity of an accident, and the duration of inactivity, which suggests abandonment or irreparable damage. Upon determining the probability of an accident, the system evaluates the physical condition of the battery. The battery evaluation includes reading the battery's current state and a sophisticated analysis to predict the battery's functionality and safety for future use. The system uses the telematics data, combined with the probability of an accident, to provide a robust picture of the battery's condition post-accident. The system continuously communicates with a server, transmitting the data gathered from the telematics unit. The server further refines the accident probability assessment and the battery condition evaluation. The server also aggregates data from multiple instances to update and refine the criteria for determining accident probabilities and battery condition assessments, improving the system's accuracy over time. When the physical condition of the battery is compromised based on the accident probability and telematics data, the server, in coordination with the system, initiates protocols for battery disposal or recycling. Conversely, if the battery is serviceable, the server authorizes its reclamation in another vehicle or energy storage.

Flow diagrams depicted herein, such as FIG. 1A, FIG. 1B, FIG. 2C, FIG. 2D, FIG. 2E, and FIG. 2F, are separate examples but may be the same or different embodiments. Any of the operations in one flow diagram may be adopted and shared with another flow diagram. No example operation is intended to limit the subject matter of any embodiment or corresponding claim.

It is important to note that all the flow diagrams and corresponding processes derived from FIG. 1A, FIG. 1B, FIG. 2C, FIG. 2D, FIG. 2E, and FIG. 2F, may be part of a same process or may share sub-processes with one another thus making the diagrams combinable into a single preferred embodiment that does not require any one specific operation but which performs certain operations from one example process and from one or more additional processes. All the example processes are related to the same physical system and can be used separately or interchangeably.

The instant solution can be used in conjunction with one or more types of vehicles: battery electric vehicles, hybrid vehicles, fuel cell vehicles, internal combustion engine vehicles and/or vehicles utilizing renewable sources.

FIG. 2A illustrates a vehicle network diagram 200, according to example embodiments. The network comprises elements including a vehicle 202 including a processor 204, as well as a vehicle 202′ including a processor 204′. The vehicles 202, 202′ communicate with one another via the processors 204, 204′, as well as other elements (not shown) including transceivers, transmitters, receivers, storage, sensors, and other elements capable of providing communication. The communication between the vehicles 202, and 202′ can occur directly, via a private and/or a public network (not shown), or via other vehicles and elements comprising one or more of a processor, memory, and software. Although depicted as single vehicles and processors, a plurality of vehicles and processors may be present. One or more of the applications, features, steps, solutions, etc., described and/or depicted herein may be utilized and/or provided by the instant elements.

FIG. 2B illustrates another vehicle network diagram 210, according to example embodiments. The network comprises elements including a vehicle 202 including a processor 204, as well as a vehicle 202′ including a processor 204′. The vehicles 202, 202′ communicate with one another via the processors 204, 204′, as well as other elements (not shown), including transceivers, transmitters, receivers, storage, sensors, and other elements capable of providing communication. The communication between the vehicles 202, and 202′ can occur directly, via a private and/or a public network (not shown), or via other vehicles and elements comprising one or more of a processor, memory, and software. The processors 204, 204′ can further communicate with one or more elements 230 including sensor 212, wired device 214, wireless device 216, database 218, mobile phone 220, vehicle 222, computer 224, input/output (I/O) device 226, and voice application 228. The processors 204, 204′ can further communicate with elements comprising one or more of a processor, memory, and software.

Although depicted as single vehicles, processors and elements, a plurality of vehicles, processors and elements may be present. Information or communication can occur to and/or from any of the processors 204, 204′ and elements 230. For example, the mobile phone 220 may provide information to the processor 204, which may initiate the vehicle 202 to take an action, may further provide the information or additional information to the processor 204′, which may initiate the vehicle 202′ to take an action, may further provide the information or additional information to the mobile phone 220, the vehicle 222, and/or the computer 224. One or more of the applications, features, steps, solutions, etc., described and/or depicted herein may be utilized and/or provided by the instant elements.

FIG. 2C illustrates yet another vehicle network diagram 240, according to example embodiments. The network comprises elements including a vehicle 202, a processor 204, and a non-transitory computer readable medium 242C. The processor 204 is communicably coupled to the computer readable medium 242C and elements 230 (which were depicted in FIG. 2B). The vehicle 202 may be a vehicle, server, or any device with a processor and memory.

The processor 204 performs one or more of determining, by a vehicle that has been damaged, a health of a battery in the vehicle, wherein the health is related to a capacity and a physical condition of the battery 244C; determining, by the vehicle, an accessibility of the battery 246C; and determining, by the vehicle, a future use of the battery, based on the determined health and the determined accessibility 248C.

FIG. 2D illustrates a further vehicle network diagram 250, according to example embodiments. The network comprises elements including a vehicle 202 a processor 204, and a non-transitory computer readable medium 242D. The processor 204 is communicably coupled to the computer readable medium 242D and elements 230 (which were depicted in FIG. 2B). The vehicle 202 may be a vehicle, server or any device with a processor and memory.

The processor 204 performs one or more of: in response to the vehicle being damaged, gathering, by the vehicle, location data of the vehicle; and transmitting, by the vehicle, a notification to a server remote from the vehicle, the notification including a current location of the vehicle 244D; determining whether or not the capacity of the battery is above a threshold; in response to the capacity being above the threshold, determining that the future use of the battery is to be deployed on another vehicle; in response to the capacity being below the threshold by a first amount, determining that the battery is to be used for at least one of a backup battery for the another vehicle, or in an on-premises energy storage device; and in response to the capacity being below the threshold by a second amount, determining that one or more materials are to be harvested from the battery, wherein the second amount is greater than the first amount 245D; in response to at least one of the physical condition or the capacity of the battery being above a threshold, determining a first recommended amount of time for recovering the battery based at least in part on the determined accessibility, and transmitting a notification indicative of the first recommended amount of time for recovering the battery; and in response to at least one of the physical condition or the capacity of the battery being below the threshold, determining a second recommended amount of time for recovering the battery based at least in part on the determined accessibility, and transmitting a notification indicative of the second recommended amount of time for recovering the battery; wherein the first recommended amount of time is greater than the second recommended amount of time 246D; in response to the vehicle being damaged, gathering by the vehicle, data from the battery, the data comprising one or more of the capacity of the battery, an age of the battery, the accessibility of the battery or a charging history of the battery; and transmitting, by the vehicle, a notification to a server remote from the vehicle, the notification including at least a portion of the data gathered from the battery 247D; in response to the vehicle being damaged, the vehicle gathering data from a condition of an occupant in the vehicle; and determining the physical condition of the battery based at least in part on the location in the vehicle of the occupant and a threshold of the condition of the occupant 248D; and receiving data from a telematics unit of the vehicle; determining a probability of an accident for the vehicle by analyzing the received data, wherein the received data comprises one or more of: a speed of the vehicle, a change of speed of the vehicle before the vehicle was damaged, a change of speed of the vehicle after the vehicle was damaged, or a number of days for which the vehicle has not been driven; and determining the physical condition of the battery based upon the determined probability of the accident 249D.

While this example describes in detail only one vehicle 202, multiple such nodes may be connected to a blockchain. It should be understood that the vehicle 202 may include additional components and that some of the components described herein may be removed and/or modified without departing from a scope of the instant solution. The vehicle 202 may have a computing device or a server computer, or the like, and may include a processor 204, which may be a semiconductor-based microprocessor, a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), and/or another hardware device. Although a single processor 204 is depicted, it should be understood that the vehicle 202 may include multiple processors, multiple cores, or the like without departing from the scope of the instant solution. The vehicle 202 may be a vehicle, server or any device with a processor and memory.

The processor 204 performs one or more of receiving a confirmation of an event from one or more elements described or depicted herein, wherein the confirmation comprises a blockchain consensus between peers represented by any element 230 and executing a smart contract to record the confirmation on a blockchain-based on the blockchain consensus. Consensus is formed between one or more of any element 230 and/or any element described or depicted herein, including a vehicle, a server, a wireless device, etc. In another example, the vehicle 202 can be one or more of any element 230 and/or any element described or depicted herein, including a server, a wireless device, etc.

The processors and/or computer readable medium 242D may fully or partially reside in the interior or exterior of the vehicles. The steps or features stored in the computer readable medium 242D may be fully or partially performed by any of the processors and/or elements in any order. Additionally, one or more steps or features may be added, omitted, combined, performed at a later time, etc.

FIG. 2E illustrates a flow diagram 260, according to example embodiments. Referring to FIG. 2E, the flow comprises determining, by a vehicle that has been damaged, a health of a battery in the vehicle, wherein the health is related to a capacity and a physical condition of the battery 244E; determining, by the vehicle, an accessibility of the battery 246E; and determining, by the vehicle, a future use of the battery, based on the determined health and the determined accessibility 248E.

FIG. 2F illustrates another flow diagram 270, according to example embodiments. Referring to FIG. 2F, the flow comprises in response to the vehicle being damaged, gathering, by the vehicle, location data of the vehicle; and transmitting, by the vehicle, a notification to a server remote from the vehicle, the notification including a current location of the vehicle 244F; determining whether or not the capacity of the battery is above a threshold; in response to the capacity being above the threshold, determining that the future use of the battery is to be deployed on another vehicle; in response to the capacity being below the threshold by a first amount, determining that the battery is to be used for at least one of a backup battery for the another vehicle, or in an on-premises energy storage device; and in response to the capacity being below the threshold by a second amount, determining that one or more materials are to be harvested from the battery, wherein the second amount is greater than the first amount 245F; in response to at least one of the physical condition or the capacity of the battery being above a threshold, determining a first recommended amount of time for recovering the battery based at least in part on the determined accessibility, and transmitting a notification indicative of the first recommended amount of time for recovering the battery; and in response to at least one of the physical condition or the capacity of the battery being below the threshold, determining a second recommended amount of time for recovering the battery based at least in part on the determined accessibility, and transmitting a notification indicative of the second recommended amount of time for recovering the battery; wherein the first recommended amount of time is greater than the second recommended amount of time 246F; in response to the vehicle being damaged, gathering by the vehicle, data from the battery, the data comprising one or more of the capacity of the battery, an age of the battery, the accessibility of the battery or a charging history of the battery; and transmitting, by the vehicle, a notification to a server remote from the vehicle, the notification including at least a portion of the data gathered from the battery 247F; in response to the vehicle being damaged, the vehicle gathering data from a condition of an occupant in the vehicle; and determining the physical condition of the battery based at least in part on the location in the vehicle of the occupant and a threshold of the condition of the occupant 248F; receiving data from a telematics unit of the vehicle; determining a probability of an accident for the vehicle by analyzing the received data, wherein the received data comprises one or more of: a speed of the vehicle, a change of speed of the vehicle before the vehicle was damaged, a change of speed of the vehicle after the vehicle was damaged, or a number of days for which the vehicle has not been driven; and determining the physical condition of the battery based upon the determined probability of the accident 249F.

Referring now to FIG. 3A, a diagram depicting a machine learning vehicle network diagram 300A. The machine learning subsystem 306A contains a learning model 308A, which is an artifact created by a machine learning training system 310A that generates predictions by finding patterns in one or more training data sets. In some embodiments, the machine learning subsystem 306A resides in the vehicle node 302A. An artifact is used to describe an output created by a training process, such as a checkpoint, a file, or a model. In other embodiments, the machine learning subsystem 306A resides outside of the vehicle node 302A.

The vehicle 302A sends data from the one or more sensors 304A to the machine learning subsystem 306A. The machine learning subsystem 306A provides the one or more sensor 304A data to the learning model 308A, which returns one or more predictions. The machine learning subsystem 306A sends one or more instructions to the vehicle 302A based on the predictions from the learning model 308A.

In a further embodiment, the vehicle 302A may send the one or more sensor 304A data to the machine learning training system 310A. In yet another example, the machine learning subsystem 306A may send the sensor 304A data to the machine learning subsystem 306A. One or more of the applications, features, steps, solutions, etc., described and/or depicted herein may utilize the machine learning network as described herein.

The example embodiments may communicate with a host platform 320, as shown in the examples of FIGS. 3B-3E. The system 300B may be hosted by or otherwise communicate with the host platform 320 shown in FIGS. 3B-3E. That is, the methods, systems, and processes described herein may interact with the processes and systems in the examples shown and described in FIGS. 3B-3E.

For example, FIG. 3B illustrates a process 300B of executing a machine learning model via the host platform 320. The host platform 320 may host a process 322 within a live runtime environment that is accessible to other software programs, applications, and the like, via a network such as the Internet. Here, the host process 322 may have a uniform resource locator (URL), endpoint, application programming interface (API), etc., which is publicly available on the Internet.

In this example, the host process 322 may control access to and execution of models that are stored within a model repository 323. For example, the models may include artificial intelligence (AI) models, machine learning (ML) models, neural networks, or the like. The system 302 may trigger the execution of a model from the model repository 323 via invocation of an application programming interface (API) 321 of the host process 322. The request may include an identifier of a model or models to be executed, a payload of data (e.g., to be input to the model during execution), and the like. The host process 322 may receive the invocation from the system 302 and retrieve the corresponding model from the model repository 323, deploy the model within a live runtime environment, execute the model on the input data, and return a result of the execution to the system 302. The result of the execution may include an output result from the execution of the model.

In some embodiments, the system 302 may provide feedback from the output provided by the model. For example, a user may input a confirmation that the prediction output by the model is correct or provide a notification that the model is incorrect. This information may be added to the results of execution and stored within a log 324. The log data may include an identifier of the input, an identifier of the output, an identifier of the model used, and feedback from the recipient. This information may be used to subsequently retrain the model, for example, using the model development environment shown in the example of FIG. 3C.

FIG. 3C illustrates a process 300C of training a machine learning model 330 according to example embodiments. Referring to FIG. 3C, the host platform 320 may host an integrated development environment (IDE) 340 where machine learning models, AI models, and the like may be developed, trained, retrained, and the like. In this example, the IDE 340 may include a software application with a user interface accessible by the system 302. For example, the IDE 340 may be embodied as a web application that can be accessed by a device at a network address, URL, etc. As another example, the IDE 340 may be locally or remotely installed on a computing device used by a user.

The process 300C may be used to design a model (via a user interface of the IDE), such as a machine learning model, etc. The model can then be executed/trained based on the training data established via the user interface. For example, the user interface may be used to build a new model. The training data for training such a new model may be provided from a training data store 325, which includes training samples from the web, from customers, and the like. Here, the model is executed on the training data via the host platform 320 to generate a result. The execution of the model causes the model to learn based on the input training data. When the model is fully trained, it may be stored within the model repository 323 via the IDE 340, or the like.

As another example, the IDE 340 may be used to retrain an existing model. Here, the training process may use executional results previously generated/output by the model 330 (including any feedback, etc.) to retrain the model 330. For example, predicted outputs that are identified as accurate, best, good, etc., may be distinguished from outputs that are inaccurate, incorrect, bad, etc. One or more of these types of outputs can be identified and used for retraining the model to help the model provide better outputs.

FIG. 3D illustrates a process 300D of designing a new machine learning model via a user interface 350 of the system according to example embodiments. As an example, a model may be output as part of the software application, which interacts with the IDE 340 shown in FIG. 3C, however, embodiments are not limited thereto. Referring to FIG. 3D, a user can use an input mechanism from a menu 352 of a user interface 350 to add pieces/components to a model being developed within a workspace 354 of the user interface 350.

In the example of FIG. 3D, the menu 352 includes a plurality of graphical user interface (GUI) menu options which can be selected to reveal additional components that can be added to the model design shown in the workspace 354. Here, the GUI menu includes options for adding features such as neural networks, machine learning models, AI models, data sources, conversion processes (e.g., vectorization, encoding, etc.), analytics, etc. The user can continue to add features to the model and connect them using edges or other means to create a flow within the workspace 354. For example, the user may add a node 356 to a flow of a new model within the workspace 354. For example, the user may connect the node 356 to another node in the flow via an edge 358, creating a dependency within the flow. When the user is done, the user can save the model for subsequent training/testing.

In another example, the name of the object can be identified from a web page or a user interface 350 where the object is visible within a browser or the workspace 354 on the user device. A pop-up within the browser or the workspace 354 can be overlayed where the object is visible, which includes an option to navigate to the identified web page corresponding to the alternative object via a rule set.

FIG. 3E illustrates a process 300E of accessing an object 362 from an object storage 360 of the host platform 320 according to example embodiments. For example, the object storage 360 may store data that is used by the AI models and machine learning (ML) models 330, training data, expected outputs for testing, training results, and the like. The object storage 360 may also store any other kind of data. Each object may include a unique identifier, a data section 363, and a metadata section 364, which provides a descriptive context associated with the data, including data that can later be extracted for purposes of machine learning. The unique identifier may uniquely identify an object with respect to all other objects in the object storage 360. The data section 363 may include unstructured data such as web pages, digital content, images, audio, text, and the like.

Instead of breaking files into blocks stored on disks in a file system, the object storage 360 handles objects as discrete units of data stored in a structurally flat data environment. Here, the object storage may not use folders, directories, or complex hierarchies. Instead, each object may be a simple, self-contained repository that includes the data, the metadata, and the unique identifier that a client application can use to locate and access it. In this case, the metadata is more descriptive than a file-based approach. The metadata can be customized with additional context that can later be extracted and leveraged for other purposes, such as data analytics.

The objects that are stored in the object storage 360 may be accessed via an application programming interface (API) 361. The API 361 may be a Hypertext Transfer Protocol (HTTP)-based RESTful API (also known as a RESTful Web service). The API 361 can be used by the client application to query an object's metadata to locate the desired object (data) via the Internet from anywhere on any device. The API 361 may use HTTP commands such as “PUT” or “POST” to upload an object, “GET” to retrieve an object, “DELETE” to remove an object, and the like.

The object storage 360 may provide a directory 365 that uses the metadata of the objects to locate appropriate data files. The directory 365 may contain descriptive information about each object stored in the object storage 360, such as a name, a unique identifier, a creation timestamp, a collection name, etc. To query the object within the object storage 360, the client application may submit a command, such as an HTTP command, with an identifier of the object 362, a payload, etc. The object storage 360 can store the actions and results described herein, including associating two or more lists of ranked assets with one another based on variables used by the two or more lists of ranked assets that have a correlation above a predetermined threshold.

FIG. 4A illustrates a diagram 400A depicting the electrification of one or more elements. In one example, a vehicle 402B may provide power stored in its batteries to one or more elements, including other vehicle(s) 408B, charging station(s) 406B, and electric grid(s) 404B. The electric grid(s) 404B is/are coupled to one or more of the charging stations 406B, which may be coupled to one or more of the vehicles 408B. This configuration allows the distribution of electricity/power received from the vehicle 402B. The vehicle 402B may also interact with the other vehicle(s) 408B, such as via Vehicle to Vehicle (V2V) technology, communication over cellular, Wi-Fi, and the like. The vehicle 402B may also interact wirelessly and/or wired with other vehicles 408B, the charging station(s) 406B and/or with the electric grid(s) 404B. In one example, the vehicle 402B is routed (or routes itself) in a safe and efficient manner to the electric grid(s) 404B, the charging station(s) 406B, or the other vehicle(s) 408B. Using one or more embodiments of the instant solution, the vehicle 402B can provide energy to one or more of the elements depicted herein in various advantageous ways as described and/or depicted herein. Further, the safety and efficiency of the vehicle may be increased, and the environment may be positively affected as described and/or depicted herein.

The term ‘energy’, ‘electricity’, ‘power’, and the like may be used to denote any form of energy received, stored, used, shared, and/or lost by the vehicles(s). The energy may be referred to in conjunction with a voltage source and/or a current supply of charge provided from an entity to the vehicle(s) during a charge/use operation. Energy may also be in the form of fossil fuels (for example, for use with a hybrid vehicle) or via alternative power sources, including but not limited to lithium-based, nickel-based, hydrogen fuel cells, atomic/nuclear energy, fusion-based energy sources, and energy generated during an energy sharing and/or usage operation for increasing or decreasing one or more vehicles energy levels at a given time.

In one example, the charging station 406B manages the amount of energy transferred from the vehicle 402B such that there is sufficient charge remaining in the vehicle 402B to arrive at a destination. In one example, a wireless connection is used to wirelessly direct an amount of energy transfer between vehicles 408B, wherein the vehicles may both be in motion. In one embodiment, wireless charging may occur via a fixed charger and batteries of the vehicle in alignment with one another (such as a charging mat in a garage or parking space). In one example, an idle vehicle, such as a vehicle 402B (which may be autonomous) is directed to provide an amount of energy to a charging station 406B and return to the original location (for example, its original location or a different destination). In one example, a mobile energy storage unit (not shown) is used to collect surplus energy from at least one other vehicle 408B and transfer the stored surplus energy at a charging station 406B. In one example, factors determine an amount of energy to transfer to a charging station 406B, such as distance, time, as well as traffic conditions, road conditions, environmental/weather conditions, the vehicle's condition (weight, etc.), an occupant(s) schedule while utilizing the vehicle, a prospective occupant(s) schedule waiting for the vehicle, etc. In one example, the vehicle(s) 408B, the charging station(s) 406B and/or the electric grid(s) 404B can provide energy to the vehicle 402B.

In one embodiment, a location such as a building, a residence, or the like (not depicted), communicably coupled to one or more of the electric grid 404B, the vehicle 402B, and/or the charging station(s) 406B. The rate of electric flow to one or more of the location, the vehicle 402B, the other vehicle(s) 408B is modified, depending on external conditions, such as weather. For example, when the external temperature is extremely hot or extremely cold, raising the chance for an outage of electricity, the flow of electricity to a connected vehicle 402B/408B is slowed to help minimize the chance for an outage.

In one embodiment, vehicles 402B and 408B may be utilized as bidirectional vehicles. Bidirectional vehicles are those that may serve as mobile microgrids that can assist in the supplying of electrical power to the grid 404B and/or reduce the power consumption when the grid is stressed. Bidirectional vehicles incorporate bidirectional charging, which in addition to receiving a charge to the vehicle, the vehicle can transfer energy from the vehicle to the grid 404B, otherwise referred to as “V2G”. In bidirectional charging, the electricity flows both ways, to the vehicle and from the vehicle. When a vehicle is charged, alternating current (AC) electricity from the grid 404B is converted to direct current (DC). This may be performed by one or more of the vehicle's own converter or a converter on the charging station 406B. The energy stored in the vehicle's batteries may be sent in an opposite direction back to the grid. The energy is converted from DC to AC through a converter usually located in the charging station 406B, otherwise referred to as a bidirectional charger. Further, the instant solution as described and depicted with respect to FIG. 4B can be utilized in this and other networks and/or systems.

FIG. 4B is a diagram showing interconnections between different elements 400B. The instant solution may be stored and/or executed entirely or partially on and/or by one or more computing devices 414C, 418C, 424C, 428C, 432C, 436C, 406C, 442C, and 410C associated with various entities, all communicably coupled and in communication with a network 402C. A database 438C is communicably coupled to the network and allows for the storage and retrieval of data. In one example, the database is an immutable ledger. One or more of the various entities may be a vehicle 404C, one or more service provider 416C, one or more public buildings 422C, one or more traffic infrastructure 426C, one or more residential dwellings 430C, an electric grid/charging station 434C, a microphone 440C, and/or another vehicle 408C. Other entities and/or devices, such as one or more private users using a smartphone 412C, a laptop 420C, an augmented reality (AR) device, a virtual reality (VR) device, and/or any wearable device may also interwork with the instant solution. The smartphone 412C, laptop 420C, the microphone 440C, and other devices may be connected to one or more of the connected computing devices 414C, 418C, 424C, 428C, 432C, 436C, 406C, 442C, and 410C. The one or more public buildings 422C may include various agencies. The one or more public buildings 422C may utilize a computing device 424C. The one or more service provider 416C may include a dealership, a tow truck service, a collision center, or other repair shop. The one or more service provider 416C may utilize a computing apparatus 418C. These various computer devices may be directly and/or communicably coupled to one another, such as via wired networks, wireless networks, blockchain networks, and the like. The microphone 440C may be utilized as a virtual assistant, in one example. In one example, the one or more traffic infrastructure 426C may include one or more traffic signals, one or more sensors including one or more cameras, vehicle speed sensors or traffic sensors, and/or other traffic infrastructure. The one or more traffic infrastructure 426C may utilize a computing device 428C.

In one embodiment, anytime an electrical charge is given or received to/from a charging station and/or an electrical grid, the entities that allow that to occur are one or more of a vehicle, a charging station, a server, and a network communicably coupled to the vehicle, the charging station, and the electrical grid.

In one example, a vehicle 408C/404C can transport a person, an object, a permanently or temporarily affixed apparatus, and the like. In one example, the vehicle 408C may communicate with vehicle 404C via V2V communication through the computers associated with each vehicle 406C and 410C and may be referred to as a car, vehicle, automobile, and the like. The vehicle 404C/408C may be a self-propelled wheeled conveyance, such as a car, a sports utility vehicle, a truck, a bus, a van, or other motor or battery-driven or fuel cell-driven vehicle. For example, vehicle 404C/408C may be an electric vehicle, a hybrid vehicle, a hydrogen fuel cell vehicle, a plug-in hybrid vehicle, or any other type of vehicle with a fuel cell stack, a motor, and/or a generator. Other examples of vehicles include bicycles, scooters, trains, planes, boats, and any other form of conveyance that is capable of transportation. The vehicle 404C/408C may be semi-autonomous or autonomous. For example, vehicle 404C/408C may be self-maneuvering and navigate without human input. An autonomous vehicle may have and use one or more sensors and/or a navigation unit to drive autonomously. All the data described or depicted herein can be stored, analyzed, processed and/or forwarded by one or more of the elements in FIG. 4B.

FIG. 4C is another block diagram showing interconnections between different elements in one example 400C. A vehicle 412D is presented and includes ECUs 410D, 408D, and a Head Unit (otherwise known as an Infotainment System) 406D. An Electrical Control Unit (ECU) is an embedded system in automotive electronics controlling one or more of the electrical systems or subsystems in a vehicle. ECUs may include but are not limited to the management of a vehicle's engine, brake system, gearbox system, door locks, dashboard, airbag system, infotainment system, electronic differential, and active suspension. ECUs are connected to the vehicle's Controller Area Network (CAN) bus 416D. The ECUs may also communicate with a vehicle computer 404D via the CAN bus 416D. The vehicle's processors/sensors (such as the vehicle computer) 404D can communicate with external elements, such as a server 418D via a network 402D (such as the Internet). Each ECU 410D, 408D, and Head Unit 406D may contain its own security policy. The security policy defines permissible processes that can be executed in the proper context. In one example, the security policy may be partially or entirely provided in the vehicle computer 404D.

ECUs 410D, 408D, and Head Unit 406D may each include a custom security functionality element 414D defining authorized processes and contexts within which those processes are permitted to run. Context-based authorization to determine validity if a process can be executed allows ECUs to maintain secure operation and prevent unauthorized access from elements such as the vehicle's Controller Area Network (CAN) Bus. When an ECU encounters a process that is unauthorized, that ECU can block the process from operating. Automotive ECUs can use different contexts to determine whether a process is operating within its permitted bounds, such as proximity contexts, nearby objects, distance to approaching objects, speed, and trajectory relative to other moving objects, and operational contexts such as an indication of whether the vehicle is moving or parked, the vehicle's current speed, the transmission state, user-related contexts such as devices connected to the transport via wireless protocols, use of the infotainment, cruise control, parking assist, driving assist, location-based contexts, and/or other contexts.

Referring to FIG. 4D, an operating environment 400D for a connected vehicle is illustrated according to some embodiments. As depicted, the vehicle 410E includes a Controller Area Network (CAN) bus 408E connecting elements 412E-426E of the vehicle. Other elements may be connected to the CAN bus and are not depicted herein. The depicted elements connected to the CAN bus include a sensor set 412E, Electronic Control Units 414E, autonomous features or Advanced Driver Assistance Systems (ADAS) 416E, and the navigation system 418E. In some embodiments, the vehicle 410E includes a processor 420E, a memory 422E, a communication unit 424E, and an electronic display 426E.

The processor 420E includes an arithmetic logic unit, a microprocessor, a general-purpose controller, and/or a similar processor array to perform computations and provide electronic display signals to a display unit 426E. The processor 420E processes data signals and may include various computing architectures, including a complex instruction set computer (CISC) architecture, a reduced instruction set computer (RISC) architecture, or an architecture implementing a combination of instruction sets. The vehicle 410E may include one or more processors 420E. Other processors, operating systems, sensors, displays, and physical configurations that are communicably coupled to one another (not depicted) may be used with the instant solution.

Memory 422E is a non-transitory memory storing instructions or data that may be accessed and executed by the processor 420E. The instructions and/or data may include code to perform the techniques described herein. The memory 422E may be a dynamic random-access memory (DRAM) device, a static random-access memory (SRAM) device, flash memory, or another memory device. In some embodiments, the memory 422E also may include non-volatile memory or a similar permanent storage device and media, which may include a hard disk drive, a floppy disk drive, a compact disc read only memory (CD-ROM) device, a digital versatile disk read only memory (DVD-ROM) device, a digital versatile disk random access memory (DVD-RAM) device, a digital versatile disk rewritable (DVD-RW) device, a flash memory device, or some other mass storage device for storing information on a permanent basis. A portion of the memory 422E may be reserved for use as a buffer or virtual random-access memory (RAM). The vehicle 410E may include one or more memories 422E without deviating from the current solution.

The memory 422E of the vehicle 410E may store one or more of the following types of data: navigation route data 418E, and autonomous features data 416E. In some embodiments, the memory 422E stores data that may be necessary for the navigation application 418E to provide the functions.

The navigation system 418E may describe at least one navigation route including a start point and an endpoint. In some embodiments, the navigation system 418E of the vehicle 410E receives a request from a user for navigation routes wherein the request includes a starting point and an ending point. The navigation system 418E may query a real-time data server 404E (via a network 402E), such as a server that provides driving directions, for navigation route data corresponding to navigation routes, including the start point and the endpoint. The real-time data server 404E transmits the navigation route data to the vehicle 410E via a wireless network 402E, and the communication system 424E stores the navigation data 418E in the memory 422E of the vehicle 410E.

The ECU 414E controls the operation of many of the systems of the vehicle 410E, including the ADAS systems 416E. The ECU 414E may, responsive to instructions received from the navigation system 418E, deactivate any unsafe and/or unselected autonomous features for the duration of a journey controlled by the ADAS systems 416E. In this way, the navigation system 418E may control whether ADAS systems 416E are activated or enabled so that they may be activated for a given navigation route.

The sensor set 412E may include any sensors in the vehicle 410E generating sensor data. For example, the sensor set 412E may include short-range sensors and long-range sensors. In some embodiments, the sensor set 412E of the vehicle 410E may include one or more of the following vehicle sensors: a camera, a light detection and ranging (Lidar) sensor, an ultrasonic sensor, an automobile engine sensor, a radar sensor, a laser altimeter, a manifold absolute pressure sensor, an infrared detector, a motion detector, a thermostat, a sound detector, a carbon monoxide sensor, a carbon dioxide sensor, an oxygen sensor, a mass airflow sensor, an engine coolant temperature sensor, a throttle position sensor, a crankshaft position sensor, a valve timer, an air-fuel ratio meter, a blind spot meter, a curb feeler, a defect detector, a Hall effect sensor, a parking sensor, a radar gun, a speedometer, a speed sensor, a tire-pressure monitoring sensor, a torque sensor, a transmission fluid temperature sensor, a turbine speed sensor (TSS), a variable reluctance sensor, a vehicle speed sensor (VSS), a water sensor, a wheel speed sensor, a GPS sensor, a mapping functionality, and any other type of automotive sensor. The navigation system 418E may store the sensor data in the memory 422E.

The communication unit 424E transmits and receives data to and from the network 402E or to another communication channel. In some embodiments, the communication unit 424E may include a dedicated short-range communications (DSRC) transceiver, a DSRC receiver, and other hardware or software necessary to make the vehicle 410E a DSRC-equipped device.

The vehicle 410E may interact with other vehicles 406E via V2V technology. V2V communication includes sensing radar information corresponding to relative distances to external objects, receiving GPS information of the vehicles, setting areas where the other vehicles 406E are located based on the sensed radar information, calculating probabilities that the GPS information of the object vehicles will be located at the set areas, and identifying vehicles and/or objects corresponding to the radar information and the GPS information of the object vehicles based on the calculated probabilities, in one example.

For a vehicle to be adequately secured, the vehicle must be protected from unauthorized physical access as well as unauthorized remote access (e.g., cyber-threats). To prevent unauthorized physical access, a vehicle is equipped with a secure access system such as a keyless entry in one example. Meanwhile, security protocols are added to a vehicle's computers and computer networks to facilitate secure remote communications to and from the vehicle in one example.

Electronic Control Units (ECUs) are nodes within a vehicle that control tasks such as activating the windshield wipers to tasks such as an anti-lock brake system. ECUs are often connected to one another through the vehicle's central network, which may be referred to as a controller area network (CAN). State-of-the-art features such as autonomous driving are strongly reliant on implementing new, complex ECUs such as advanced driver-assistance systems (ADAS), sensors, and the like. While these new technologies have helped improve the safety and driving experience of a vehicle, they have also increased the number of externally communicating units inside of the vehicle, making them more vulnerable to attack. Below are some examples of protecting the vehicle from physical intrusion and remote intrusion.

In one embodiment, a CAN includes a CAN bus with a high and low terminal and a plurality of electronic control units (ECUs), which are connected to the CAN bus via wired connections. The CAN bus is designed to allow microcontrollers and devices to communicate with each other in an application without a host computer. The CAN bus implements a message-based protocol (i.e., ISO 11898 standards) that allows ECUs to send commands to one another at a root level. Meanwhile, the ECUs represent controllers for controlling electrical systems or subsystems within the vehicle. Examples of the electrical systems include power steering, anti-lock brakes, air-conditioning, tire pressure monitoring, cruise control, and many other features.

In this example, the ECU includes a transceiver and a microcontroller. The transceiver may be used to transmit and receive messages to and from the CAN bus. For example, the transceiver may convert the data from the microcontroller into a format of the CAN bus and also convert data from the CAN bus into a format for the microcontroller. Meanwhile, the microcontroller interprets the messages and also decide what messages to send using ECU software installed therein in one example.

To protect the CAN from cyber threats, various security protocols may be implemented. For example, sub-networks (e.g., sub-networks A and B, etc.) may be used to divide the CAN into smaller sub-CANs and limit an attacker's capabilities to access the vehicle remotely. In one embodiment, a firewall (or gateway, etc.) may be added to block messages from crossing the CAN bus across sub-networks. If an attacker gains access to one sub-network, the attacker will not have access to the entire network. To make sub-networks even more secure, the most critical ECUs are not placed on the same sub-network, in one example.

In addition to protecting a vehicle's internal network, vehicles may also be protected when communicating with external networks such as the Internet. One of the benefits of having a vehicle connection to a data source such as the Internet is that information from the vehicle can be sent through a network to remote locations for analysis. Examples of vehicle information include GPS, onboard diagnostics, tire pressure, and the like. These communication systems are often referred to as telematics because they involve the combination of telecommunications and informatics. Further, the instant solution as described and depicted can be utilized in this and other networks and/or systems, including those that are described and depicted herein.

FIG. 4E illustrates an example 400E of vehicles 402I and 408I performing secured V2V communications using security certificates, according to example embodiments. Referring to FIG. 4E, the vehicles 402I and 408I may communicate via V2V communications over a short-range network, a cellular network, or the like. Before sending messages, the vehicles 402I and 408I may sign the messages using a respective public key certificate. For example, the vehicle 402I may sign a V2V message using a public key certificate 404I. Likewise, the vehicle 408I may sign a V2V message using a public key certificate 410I. The public key certificates 404I and 410I are associated with the vehicles 402I and 408I, respectively, in one example.

Upon receiving the communications from each other, the vehicles may verify the signatures with a certificate authority 4061 or the like. For example, the vehicle 408I may verify with the certificate authority 4061 that the public key certificate 404I used by vehicle 402I to sign a V2V communication is authentic. If the vehicle 408I successfully verifies the public key certificate 404I, the vehicle knows that the data is from a legitimate source. Likewise, the vehicle 402I may verify with the certificate authority 4061 that the public key certificate 410I used by the vehicle 408I to sign a V2V communication is authentic. Further, the instant solution as described and depicted with respect to FIG. 4E can be utilized in this and other networks and/or systems including those that are described and depicted herein.

In some embodiments, a computer may include a security processor. In particular, the security processor may perform authorization, authentication, cryptography (e.g., encryption), and the like, for data transmissions that are sent between ECUs and other devices on a CAN bus of a vehicle, and also data messages that are transmitted between different vehicles. The security processor may include an authorization module, an authentication module, and a cryptography module. The security processor may be implemented within the vehicle's computer and may communicate with other vehicle elements, for example, the ECUs/CAN network, wired and wireless devices such as wireless network interfaces, input ports, and the like. The security processor may ensure that data frames (e.g., CAN frames, etc.) that are transmitted internally within a vehicle (e.g., via the ECUs/CAN network) are secure. Likewise, the security processor can ensure that messages transmitted between different vehicles and devices attached or connected via a wire to the vehicle's computer are also secured.

For example, the authorization module may store passwords, usernames, PIN codes, biometric scans, and the like for different vehicle users. The authorization module may determine whether a user (or technician) has permission to access certain settings such as a vehicle's computer. In some embodiments, the authorization module may communicate with a network interface to download any necessary authorization information from an external server. When a user desires to make changes to the vehicle settings or modify technical details of the vehicle via a console or GUI within the vehicle or via an attached/connected device, the authorization module may require the user to verify themselves in some way before such settings are changed. For example, the authorization module may require a username, a password, a PIN code, a biometric scan, a predefined line drawing or gesture, and the like. In response, the authorization module may determine whether the user has the necessary permissions (access, etc.) being requested.

The authentication module may be used to authenticate internal communications between ECUs on the CAN network of the vehicle. As an example, the authentication module 308J may provide information for authenticating communications between the ECUs. As an example, the authentication module may transmit a bit signature algorithm to the ECUs of the CAN network. The ECUs may use the bit signature algorithm to insert authentication bits into the CAN fields of the CAN frame. All ECUs on the CAN network typically receive each CAN frame. The bit signature algorithm may dynamically change the position, amount, etc., of authentication bits each time a new CAN frame is generated by one of the ECUs. The authentication module may also provide a list of ECUs that are exempt (safe list) and that do not need to use the authentication bits. The authentication module may communicate with a remote server to retrieve updates to the bit signature algorithm and the like.

The encryption module may store asymmetric key pairs to be used by the vehicle to communicate with other external user devices and vehicles. For example, the encryption module may provide a private key to be used by the vehicle to encrypt/decrypt communications, while the corresponding public key may be provided to other user devices and vehicles to enable the other devices to decrypt/encrypt the communications. The encryption module may communicate with a remote server to receive new keys, updates to keys, keys of new vehicles, users, etc., and the like. The encryption module may also transmit any updates to a local private/public key pair to the remote server.

FIG. 5A illustrates an example vehicle configuration 500A for managing database transactions associated with a vehicle, according to example embodiments. Referring to FIG. 5A, as a particular vehicle 525 is engaged in transactions (e.g., vehicle service, dealer transactions, delivery/pickup, transportation services, etc.), the vehicle may receive assets 510 and/or expel/transfer assets 512 according to a transaction(s). A vehicle processor 526 resides in the vehicle 525 and communication exists between the vehicle processor 526, a database 530, and the transaction module 520. The transaction module 520 may record information, such as assets, parties, credits, service descriptions, date, time, location, results, notifications, unexpected events, etc. Those transactions in the transaction module 520 may be replicated into a database 530. The database 530 can be one of a structured query language (SQL) database, a relational database management system (RDBMS), a relational database, a non-relational database, a blockchain, a distributed ledger, and may be on board the vehicle, may be off-board the vehicle, may be accessed directly and/or through a network, or be accessible to the vehicle.

In one embodiment, a vehicle may engage with another vehicle to perform various actions such as to share, transfer, acquire service calls, etc. when the vehicle has reached a status where the services need to be shared with another vehicle. For example, the vehicle may be due for a battery charge and/or may have an issue with a tire and may be in route to pick up a package for delivery. A vehicle processor resides in the vehicle and communication exists between the vehicle processor, a first database, and a transaction module. The vehicle may notify another vehicle, which is in its network and which operates on its blockchain member service. A vehicle processor resides in the other vehicle and communication exists between the vehicle processor, a second database, the vehicle processor, and a transaction module. The other vehicle may then receive the information via a wireless communication request to perform the package pickup from the vehicle and/or from a server (not shown). The transactions are logged in the transaction modules and of both vehicles. The credits are transferred from the vehicle to the other vehicle and the record of the transferred service is logged in the first and databases, assuming that the blockchains are different from one another, or are logged in the same blockchain used by all members. The first database can be one of a SQL database, an RDBMS, a relational database, a non-relational database, a blockchain, a distributed ledger, and may be on board the vehicle, may be off-board the vehicle, may be accessible directly and/or through a network.

FIG. 5B illustrates a blockchain architecture configuration 500B, according to example embodiments. Referring to FIG. 5B, the blockchain architecture 500B may include certain blockchain elements, for example, a group of blockchain member nodes 502-505 as part of a blockchain group 510. In one example embodiment, a permissioned blockchain is not accessible to all parties but only to those members with permissioned access to the blockchain data. The blockchain nodes participate in a number of activities, such as blockchain entry addition and validation process (consensus). One or more of the blockchain nodes may endorse entries based on an endorsement policy and may provide an ordering service for all blockchain nodes. A blockchain node may initiate a blockchain action (such as an authentication) and seek to write to a blockchain immutable ledger stored in the blockchain, a copy of which may also be stored on the underpinning physical infrastructure.

The blockchain transactions 520 are stored in memory of computers as the transactions are received and approved by the consensus model dictated by the members' nodes. Approved transactions 526 are stored in current blocks of the blockchain and committed to the blockchain via a committal procedure, which includes performing a hash of the data contents of the transactions in a current block and referencing a previous hash of a previous block. Within the blockchain, one or more smart contracts 530 may exist that define the terms of transaction agreements and actions included in smart contract executable application code 532, such as registered recipients, vehicle features, requirements, permissions, sensor thresholds, etc. The code may be configured to identify whether requesting entities are registered to receive vehicle services, what service features they are entitled/required to receive given their profile statuses and whether to monitor their actions in subsequent events. For example, when a service event occurs and a user is riding in the vehicle, the sensor data monitoring may be triggered, and a certain parameter, such as a vehicle charge level, may be identified as being above/below a particular threshold for a particular period of time, then the result may be a change to a current status, which requires an alert to be sent to the managing party (i.e., vehicle owner, vehicle operator, server, etc.) so the service can be identified and stored for reference. The vehicle sensor data collected may be based on types of sensor data used to collect information about vehicle's status. The sensor data may also be the basis for the vehicle event data 534, such as a location(s) to be traveled, an average speed, a top speed, acceleration rates, whether there were any collisions, was the expected route taken, what is the next destination, whether safety measures are in place, whether the vehicle has enough charge/fuel, etc. All such information may be the basis of smart contract terms 530, which are then stored in a blockchain. For example, sensor thresholds stored in the smart contract can be used as the basis for whether a detected service is necessary and when and where the service should be performed.

In one embodiment, a blockchain logic example includes a blockchain application interface as an API or plug-in application that links to the computing device and execution platform for a particular transaction. The blockchain configuration may include one or more applications, which are linked to application programming interfaces (APIs) to access and execute stored program/application code (e.g., smart contract executable code, smart contracts, etc.), which can be created according to a customized configuration sought by participants and can maintain their own state, control their own assets, and receive external information. This can be deployed as an entry and installed, via appending to the distributed ledger, on all blockchain nodes.

The smart contract application code provides a basis for the blockchain transactions by establishing application code, which when executed causes the transaction terms and conditions to become active. The smart contract, when executed, causes certain approved transactions to be generated, which are then forwarded to the blockchain platform. The platform includes a security/authorization, computing devices, which execute the transaction management and a storage portion as a memory that stores transactions and smart contracts in the blockchain.

The blockchain platform may include various layers of blockchain data, services (e.g., cryptographic trust services, virtual execution environment, etc.), and underpinning physical computer infrastructure that may be used to receive and store new entries and provide access to auditors, which are seeking to access data entries. The blockchain may expose an interface that provides access to the virtual execution environment necessary to process the program code and engage the physical infrastructure. Cryptographic trust services may be used to verify entries such as asset exchange entries and keep information private.

The blockchain architecture configuration of FIGS. 5A and 5B may process and execute program/application code via one or more interfaces exposed, and services provided, by the blockchain platform. As a non-limiting example, smart contracts may be created to execute reminders, updates, and/or other notifications subject to the changes, updates, etc. The smart contracts can themselves be used to identify rules associated with authorization and access requirements and usage of the ledger. For example, the information may include a new entry, which may be processed by one or more processing entities (e.g., processors, virtual machines, etc.) included in the blockchain layer. The result may include a decision to reject or approve the new entry based on the criteria defined in the smart contract and/or a consensus of the peers. The physical infrastructure may be utilized to retrieve any of the data or information described herein.

Within smart contract executable code, a smart contract may be created via a high-level application and programming language, and then written to a block in the blockchain. The smart contract may include executable code that is registered, stored, and/or replicated with a blockchain (e.g., distributed network of blockchain peers). An entry is an execution of the smart contract code, which can be performed in response to conditions associated with the smart contract being satisfied. The executing of the smart contract may trigger a trusted modification(s) to a state of a digital blockchain ledger. The modification(s) to the blockchain ledger caused by the smart contract execution may be automatically replicated throughout the distributed network of blockchain peers through one or more consensus protocols.

The smart contract may write data to the blockchain in the format of key-value pairs. Furthermore, the smart contract code can read the values stored in a blockchain and use them in application operations. The smart contract code can write the output of various logic operations into the blockchain. The code may be used to create a temporary data structure in a virtual machine or other computing platform. Data written to the blockchain can be public and/or can be encrypted and maintained as private. The temporary data that is used/generated by the smart contract is held in memory by the supplied execution environment, then deleted once the data needed for the blockchain is identified.

A smart contract executable code may include the code interpretation of a smart contract, with additional features. As described herein, the smart contract executable code may be program code deployed on a computing network, where it is executed and validated by chain validators together during a consensus process. The smart contract executable code receives a hash and retrieves from the blockchain a hash associated with the data template created by use of a previously stored feature extractor. If the hashes of the hash identifier and the hash created from the stored identifier template data match, then the smart contract executable code sends an authorization key to the requested service. The smart contract executable code may write to the blockchain data associated with the cryptographic details.

FIG. 5C illustrates a blockchain configuration for storing blockchain transaction data, according to example embodiments. Referring to FIG. 5C, the example configuration 500C provides for the vehicle 562, the user device 564 and a server 566 sharing information with a distributed ledger (i.e., blockchain) 568. The server may represent a service provider entity inquiring with a vehicle service provider to share user profile rating information in the event that a known and established user profile is attempting to rent a vehicle with an established rated profile. The server 566 may be receiving and processing data related to a vehicle's service requirements. As the service events occur, such as the vehicle sensor data indicates a need for fuel/charge, a maintenance service, etc., a smart contract may be used to invoke rules, thresholds, sensor information gathering, etc., which may be used to invoke the vehicle service event. The blockchain transaction data 570 is saved for each transaction, such as the access event, the subsequent updates to a vehicle's service status, event updates, etc. The transactions may include the parties, the requirements (e.g., 18 years of age, service eligible candidate, valid driver's license, etc.), compensation levels, the distance traveled during the event, the registered recipients permitted to access the event and host a vehicle service, rights/permissions, sensor data retrieved during the vehicle event operation to log details of the next service event and identify a vehicle's condition status, and thresholds used to make determinations about whether the service event was completed and whether the vehicle's condition status has changed.

FIG. 5D illustrates blockchain blocks that can be added to a distributed ledger, according to example embodiments, and contents of block structures 582A to 582n. Referring to FIG. 5D, clients (not shown) may submit entries to blockchain nodes to enact activity on the blockchain. As an example, clients may be applications that act on behalf of a requester, such as a device, person, or entity to propose entries for the blockchain. The plurality of blockchain peers (e.g., blockchain nodes) may maintain a state of the blockchain network and a copy of the distributed ledger. Different types of blockchain nodes/peers may be present in the blockchain network including endorsing peers, which simulate and endorse entries proposed by clients and committing peers which verify endorsements, validate entries, and commit entries to the distributed ledger. In this example, the blockchain nodes may perform the role of endorser node, committer node, or both.

The instant system includes a blockchain that stores immutable, sequenced records in blocks, and a state database (current world state) maintaining a current state of the blockchain. One distributed ledger may exist per channel and each peer maintains its own copy of the distributed ledger for each channel of which they are a member. The instant blockchain is an entry log, structured as hash-linked blocks where each block contains a sequence of N entries. Blocks may include various components such as those shown in FIG. 5D. The linking of the blocks may be generated by adding a hash of a prior block's header within a block header of a current block. In this way, all entries on the blockchain are sequenced and cryptographically linked together preventing tampering with blockchain data without breaking the hash links. Furthermore, because of the links, the latest block in the blockchain represents every entry that has come before it. The instant blockchain may be stored on a peer file system (local or attached storage), which supports an append-only blockchain workload.

The current state of the blockchain and the distributed ledger may be stored in the state database. Here, the current state data represents the latest values for all keys ever included in the chain entry log of the blockchain. Smart contract executable code invocations execute entries against the current state in the state database. To make these smart contract executable code interactions extremely efficient, the latest values of all keys are stored in the state database. The state database may include an indexed view into the entry log of the blockchain and can therefore be regenerated from the chain at any time. The state database may automatically get recovered (or generated if needed) upon peer startup and before entries are accepted.

Endorsing nodes receive entries from clients and endorse the entry based on simulated results. Endorsing nodes hold smart contracts, which simulate the entry proposals. When an endorsing node endorses an entry, the endorsing nodes creates an entry endorsement, which is a signed response from the endorsing node to the client application indicating the endorsement of the simulated entry. The method of endorsing an entry depends on an endorsement policy that may be specified within smart contract executable code. An example of an endorsement policy is “the majority of endorsing peers must endorse the entry.” Different channels may have different endorsement policies. Endorsed entries are forwarded by the client application to an ordering service.

The ordering service accepts endorsed entries, orders them into a block, and delivers the blocks to the committing peers. For example, the ordering service may initiate a new block when a threshold of entries has been reached, a timer times out, or another condition. In this example, blockchain node is a committing peer that has received a data block 582A for storage on the blockchain. The ordering service may be made up of a cluster of orderers. The ordering service does not process entries, smart contracts, or maintain the shared ledger. Rather, the ordering service may accept the endorsed entries and specifies the order in which those entries are committed to the distributed ledger. The architecture of the blockchain network may be designed such that the specific implementation of ‘ordering’ becomes a pluggable component.

Entries are written to the distributed ledger in a consistent order. The order of entries is established to ensure that the updates to the state database are valid when they are committed to the network. Unlike a cryptocurrency blockchain system where ordering occurs through the solving of a cryptographic puzzle, or mining, in this example the parties of the distributed ledger may choose the ordering mechanism that best suits that network.

Referring to FIG. 5D, a block 582A (also referred to as a data block) that is stored on the blockchain and/or the distributed ledger may include multiple data segments such as a block header 584A to 584n, transaction-specific data 586A to 586n, and block metadata 588A to 588n. It should be appreciated that the various depicted blocks and their contents, such as block 582A and its contents are merely for purposes of an example and are not meant to limit the scope of the example embodiments. In some cases, both the block header 584A and the block metadata 588A may be smaller than the transaction-specific data 586A, which stores entry data; however, this is not a requirement. The block 582A may store transactional information of N entries (e.g., 100, 500, 1000, 2000, 3000, etc.) within the block data 590A to 590n. The block 582A may also include a link to a previous block (e.g., on the blockchain) within the block header 584A. In particular, the block header 584A may include a hash of a previous block's header. The block header 584A may also include a unique block number, a hash of the block data 590A of the current block 582A, and the like. The block number of the block 582A may be unique and assigned in an incremental/sequential order starting from zero. The first block in the blockchain may be referred to as a genesis block, which includes information about the blockchain, its members, the data stored therein, etc.

The block data 590A may store entry information of each entry that is recorded within the block. For example, the entry data may include one or more of a type of the entry, a version, a timestamp, a channel ID of the distributed ledger, an entry ID, an epoch, a payload visibility, a smart contract executable code path (deploy tx), a smart contract executable code name, a smart contract executable code version, input (smart contract executable code and functions), a client (creator) identify such as a public key and certificate, a signature of the client, identities of endorsers, endorser signatures, a proposal hash, smart contract executable code events, response status, namespace, a read set (list of key and version read by the entry, etc.), a write set (list of key and value, etc.), a start key, an end key, a list of keys, a Merkel tree query summary, and the like. The entry data may be stored for each of the N entries.

In some embodiments, the block data 590A may also store transaction-specific data 586A, which adds additional information to the hash-linked chain of blocks in the blockchain. Accordingly, the data 586A can be stored in an immutable log of blocks on the distributed ledger. Some of the benefits of storing such data 586A are reflected in the various embodiments disclosed and depicted herein. The block metadata 588A may store multiple fields of metadata (e.g., as a byte array, etc.). Metadata fields may include signature on block creation, a reference to a last configuration block, an entry filter identifying valid and invalid entries within the block, last offset persisted of an ordering service that ordered the block, and the like. The signature, the last configuration block, and the orderer metadata may be added by the ordering service. Meanwhile, a committer of the block (such as a blockchain node) may add validity/invalidity information based on an endorsement policy, verification of read/write sets, and the like. The entry filter may include a byte array of a size equal to the number of entries in the block data and a validation code identifying whether an entry was valid/invalid.

The other blocks 582B to 582n in the blockchain also have headers, files, and values. However, unlike the first block 582A, each of the headers 584A to 584n in the other blocks includes the hash value of an immediately preceding block. The hash value of the immediately preceding block may be just the hash of the header of the previous block or may be the hash value of the entire previous block. By including the hash value of a preceding block in each of the remaining blocks, a trace can be performed from the Nth block back to the genesis block (and the associated original file) on a block-by-block basis, as indicated by arrows 592, to establish an auditable and immutable chain-of-custody.

The above embodiments may be implemented in hardware, in a computer program executed by a processor, in firmware, or in a combination of the above. A computer program may be embodied on a computer readable media, such as a storage medium. For example, a computer program may reside in random access memory (“RAM”), flash memory, read-only memory (“ROM”), erasable programmable read-only memory (“EPROM”), electrically erasable programmable read-only memory (“EEPROM”), registers, hard disk, a removable disk, a compact disk read-only memory (“CD-ROM”), or any other form of storage medium known in the art.

An exemplary storage medium may be coupled to the processor such that the processor may read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an application-specific integrated circuit (“ASIC”). In the alternative, the processor and the storage medium may reside as discrete components. For example, FIG. 6 illustrates an example computer system architecture 600, which may represent or be integrated in any of the above-described components, etc.

FIG. 5E illustrates a process 500E of a new block being added to a distributed ledger 520E, according to example embodiments, and FIG. 5D illustrates the contents of FIG. 5E's new data block structure 530E for blockchain, according to example embodiments. Referring to FIG. 5E, clients (not shown) may submit transactions to blockchain nodes 511E, 512E, and/or 513E. Clients may be instructions received from any source to enact activity on the blockchain 522E. As an example, clients may be applications that act on behalf of a requester, such as a device, person, or entity to propose transactions for the blockchain. The plurality of blockchain peers (e.g., blockchain nodes 511E, 512E, and 513E) may maintain a state of the blockchain network and a copy of the distributed ledger 520E. Different types of blockchain nodes/peers may be present in the blockchain network including endorsing peers which simulate and endorse transactions proposed by clients and committing peers which verify endorsements, validate transactions, and commit transactions to the distributed ledger 520E. In this example, the blockchain nodes 511E, 512E, and 513E may perform the role of endorser node, committer node, or both.

The distributed ledger 520E includes a blockchain which stores immutable, sequenced records in blocks, and a state database 524E (current world state) maintaining a current state of the blockchain 522E. One distributed ledger 520E may exist per channel and each peer maintains its own copy of the distributed ledger 520E for each channel of which they are a member. The blockchain 522E is a transaction log, structured as hash-linked blocks where each block contains a sequence of N transactions. The linking of the blocks (shown by arrows in FIG. 5E) may be generated by adding a hash of a prior block's header within a block header of a current block. In this way, all transactions on the blockchain 522E are sequenced and cryptographically linked together preventing tampering with blockchain data without breaking the hash links. Furthermore, because of the links, the latest block in the blockchain 522E represents every transaction that has come before it. The blockchain 522E may be stored on a peer file system (local or attached storage), which supports an append-only blockchain workload.

The current state of the blockchain 522E and the distributed ledger 520E may be stored in the state database 524E. Here, the current state data represents the latest values for all keys ever included in the chain transaction log of the blockchain 522E. Chaincode invocations execute transactions against the current state in the state database 524E. To make these chaincode interactions extremely efficient, the latest values of all keys are stored in the state database 524E. The state database 524E may include an indexed view into the transaction log of the blockchain 522E and can therefore be regenerated from the chain at any time. The state database 524E may automatically get recovered (or generated if needed) upon peer startup and before transactions are accepted.

Endorsing nodes receive transactions from clients and endorse the transaction based on simulated results. Endorsing nodes hold smart contracts which simulate the transaction proposals. When an endorsing node endorses a transaction, the endorsing nodes creates a transaction endorsement which is a signed response from the endorsing node to the client application indicating the endorsement of the simulated transaction. The method of endorsing a transaction depends on an endorsement policy which may be specified within chaincode. An example of an endorsement policy is “the majority of endorsing peers must endorse the transaction.” Different channels may have different endorsement policies. Endorsed transactions are forwarded by the client application to the ordering service 510E.

The ordering service 510E accepts endorsed transactions, orders them into a block, and delivers the blocks to the committing peers. For example, the ordering service 510E may initiate a new block when a threshold of transactions has been reached, a timer times out, or another condition. In the example of FIG. 5E, blockchain node 512E is a committing peer that has received a new data block 530E for storage on blockchain 522E. The first block in the blockchain may be referred to as a genesis block which includes information about the blockchain, its members, the data stored therein, etc.

The ordering service 510E may be made up of a cluster of orderers. The ordering service 510E does not process transactions, smart contracts, or maintain the shared ledger. Rather, the ordering service 510E may accept the endorsed transactions and specifies the order in which those transactions are committed to the distributed ledger 520E. The architecture of the blockchain network may be designed such that the specific implementation of ‘ordering’ becomes a pluggable component.

Transactions are written to the distributed ledger 520E in a consistent order. The order of transactions is established to ensure that the updates to the state database 524E are valid when they are committed to the network. Unlike a cryptocurrency blockchain system where ordering occurs through the solving of a cryptographic puzzle, or mining, in this example the parties of the distributed ledger 520E may choose the ordering mechanism that best suits the network.

When the ordering service 510E initializes a new data block 530E, the new data block 530E may be broadcast to committing peers (e.g., blockchain nodes 511E, 512E, and 513E). In response, each committing peer validates the transaction within the new data block 530E by checking to make sure that the read set and the write set still match the current world state in the state database 524E. Specifically, the committing peer can determine whether the read data that existed when the endorsers simulated the transaction is identical to the current world state in the state database 524E. When the committing peer validates the transaction, the transaction is written to the blockchain 522E on the distributed ledger 520E, and the state database 524E is updated with the write data from the read-write set. If a transaction fails, that is, if the committing peer finds that the read-write set does not match the current world state in the state database 524E, the transaction ordered into a block will still be included in that block, but it will be marked as invalid, and the state database 524E will not be updated.

Referring to FIG. 5F500F, a new data block 530 (also referred to as a data block) that is stored on the blockchain 522E of the distributed ledger 520E, shown in FIG. 5E, may include multiple data segments such as a block header 540, block data 550, and block metadata 560. It should be appreciated that the various depicted blocks and their contents, such as new data block 530 and its contents shown in FIG. 5F, are merely examples and are not meant to limit the scope of the example embodiments. The new data block 530 may store transactional information of N transaction(s) (e.g., 1, 10, 100, 500, 1000, 2000, 3000, etc.) within the block data 550. The new data block 530 may also include a link to a previous block (e.g., on the blockchain 522E in FIG. 5E) within the block header 540. In particular, the block header 540 may include a hash of a previous block's header. The block header 540 may also include a unique block number, a hash of the block data 550 of the new data block 530, and the like. The block number of the new data block 530 may be unique and assigned in various orders, such as an incremental/sequential order starting from zero.

The block data 550 may store transactional information of each transaction that is recorded within the new data block 530. For example, the transaction data may include one or more of a type of the transaction, a version, a timestamp, a channel ID of the distributed ledger 520E (shown in FIG. 5E), a transaction ID, an epoch, a payload visibility, a chaincode path (deploy tx), a chaincode name, a chaincode version, input (chaincode and functions), a client (creator) identify such as a public key and certificate, a signature of the client, identities of endorsers, endorser signatures, a proposal hash, chaincode events, response status, namespace, a read set (list of key and version read by the transaction, etc.), a write set (list of key and value, etc.), a start key, an end key, a list of keys, a Merkel tree query summary, and the like. The transaction data may be stored for each of the N transactions.

In some embodiments, blockchain data 563 contains telematics data for the vehicle 102 (FIG. 1A) gathered, for example, by the telematics unit 118. Although in FIG. 5F the blockchain data 563 is depicted in the block data 550, the blockchain data 563 may also be located in the block header 540 or the block metadata 560.

The block metadata 560 may store multiple fields of metadata (e.g., as a byte array, etc.). Metadata fields may include signature on block creation, a reference to a last configuration block, a transaction filter identifying valid and invalid transactions within the block, last offset persisted of an ordering service that ordered the block, and the like. The signature, the last configuration block, and the orderer metadata may be added by the ordering service 510E in FIG. 5E. Meanwhile, a committer of the block (such as blockchain node 512E in FIG. 5E) may add validity/invalidity information based on an endorsement policy, verification of read/write sets, and the like. The transaction filter may include a byte array of a size equal to the number of transactions in the block data 500D and a validation code identifying whether a transaction was valid/invalid.

FIG. 6 is not intended to suggest any limitation as to the scope of use or functionality of embodiments of the application described herein. Regardless, the computing node 600 is capable of being implemented and/or performing any of the functionality set forth hereinabove.

In computing node 600 there is a computer system/server 602, which is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 602 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like.

Computer system/server 602 may be described in the general context of computer system-executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 602 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.

As shown in FIG. 6, computer system/server 602 in cloud computing node 600 is shown in the form of a general-purpose computing device. The components of computer system/server 602 may include, but are not limited to, one or more processors or processing units 604, a system memory 606, and a bus that couples various system components including system memory 606 to processor 604.

The bus represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.

Computer system/server 602 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 602, and it includes both volatile and non-volatile media, removable and non-removable media. System memory 606, in one example, implements the flow diagrams of the other figures. The system memory 606 can include computer system readable media in the form of volatile memory, such as random-access memory (RAM) 608 and/or cache memory 610. Computer system/server 602 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, memory 606 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to the bus by one or more data media interfaces. As will be further depicted and described below, memory 606 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of various embodiments of the application.

Program/utility, having a set (at least one) of program modules, may be stored in memory 606 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules generally carry out the functions and/or methodologies of various embodiments of the application as described herein.

As will be appreciated by one skilled in the art, aspects of the present application may be embodied as a system, method, or computer program product. Accordingly, aspects of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present application may take the form of a computer program product embodied in one or more computer readable media(s) having computer readable program code embodied thereon.

Computer system/server 602 may also communicate with one or more external devices via an I/O device 612 (such as an I/O adapter), which may include a keyboard, a pointing device, a display, a voice recognition module, etc., one or more devices that enable a user to interact with computer system/server 602, and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 602 to communicate with one or more other computing devices. Such communication can occur via I/O interfaces of the device 612. Still yet, computer system/server 602 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via a network adapter. As depicted, device 612 communicates with the other components of computer system/server 602 via a bus. It should be understood that, although not shown, other hardware and/or software components may be used in conjunction with computer system/server 602. Examples include, but are not limited to, microcode, device drivers, redundant processing units, external disk drive arrays, redundant array of independent disks (RAID) systems, tape drives, and data archival storage systems, etc.

Although an exemplary embodiment of at least one of a system, method, and non-transitory computer readable media has been illustrated in the accompanied drawings and described in the foregoing detailed description, it will be understood that the application is not limited to the embodiments disclosed, but is capable of numerous rearrangements, modifications, and substitutions as set forth and defined by the following claims. For example, the capabilities of the system of the various figures can be performed by one or more of the modules or components described herein or in a distributed architecture and may include a transmitter, receiver, or pair of both. For example, all or part of the functionality performed by the individual modules, may be performed by one or more of these modules. Further, the functionality described herein may be performed at various times and in relation to various events, internal or external to the modules or components. Also, the information sent between various modules can be sent between the modules via at least one of: a data network, the Internet, a voice network, an Internet Protocol network, a wireless device, a wired device and/or via plurality of protocols. Also, the messages sent or received by any of the modules may be sent or received directly and/or via one or more of the other modules.

One skilled in the art will appreciate that a “system” may be embodied as a personal computer, a server, a console, a personal digital assistant (PDA), a cell phone, a tablet computing device, a smartphone or any other suitable computing device, or combination of devices. Presenting the above-described functions as being performed by a “system” is not intended to limit the scope of the present application in any way but is intended to provide one example of many embodiments. Indeed, methods, systems and apparatuses disclosed herein may be implemented in localized and distributed forms consistent with computing technology.

It should be noted that some of the system features described in this specification have been presented as modules to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, graphics processing units, or the like.

A module may also be at least partially implemented in software for execution by various types of processors. An identified unit of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions that may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together but may comprise disparate instructions stored in different locations that, when joined logically together, comprise the module and achieve the stated purpose for the module. Further, modules may be stored on a computer-readable medium, which may be, for instance, a hard disk drive, flash device, random access memory (RAM), tape, or any other such medium used to store data.

Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set or may be distributed over different locations, including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.

It will be readily understood that the components of the application, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the detailed description of the embodiments is not intended to limit the scope of the application as claimed but is merely representative of selected embodiments of the application.

One having ordinary skill in the art will readily understand that the above may be practiced with steps in a different order and/or with hardware elements in configurations that are different from those which are disclosed. Therefore, although the application has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent.

While preferred embodiments of the present application have been described, it is to be understood that the embodiments described are illustrative only and the scope of the application is to be defined solely by the appended claims when considered with a full range of equivalents and modifications (e.g., protocols, hardware devices, software platforms etc.) thereto.

Claims

1. A method, comprising: determining, by a vehicle that has been damaged, a health of a battery in the vehicle, wherein the health is related to a capacity and a physical condition of the battery;determining, by the vehicle, an accessibility of the battery; anddetermining, by the vehicle, a future use of the battery, based on the determined health and the determined accessibility.

2. The method of claim 1, comprising: in response to the vehicle being damaged, gathering, by the vehicle, location data of the vehicle; andtransmitting, by the vehicle, a notification to a server remote from the vehicle, the notification including a current location of the vehicle.

3. The method of claim 1, comprising: determining whether or not the capacity of the battery is above a threshold;in response to the capacity being above the threshold, determining that the future use of the battery is to be deployed on another vehicle;in response to the capacity being below the threshold by a first amount, determining that the battery is to be used for at least one of a backup battery for the another vehicle, or in an on-premises energy storage device; andin response to the capacity being below the threshold by a second amount, determining that one or more materials are to be harvested from the battery, wherein the second amount is greater than the first amount.

4. The method of claim 1, comprising: in response to at least one of the physical condition or the capacity of the battery being above a threshold, determining a first recommended amount of time for recovering the battery based at least in part on the determined accessibility, and transmitting a notification indicative of the first recommended amount of time for recovering the battery; andin response to at least one of the physical condition or the capacity of the battery being below the threshold, determining a second recommended amount of time for recovering the battery based at least in part on the determined accessibility, and transmitting a notification indicative of the second recommended amount of time for recovering the battery;wherein the first recommended amount of time is greater than the second recommended amount of time.

5. The method of claim 1, comprising: in response to the vehicle being damaged, gathering by the vehicle, data from the battery, the data comprising one or more of the capacity of the battery, an age of the battery, the accessibility of the battery or a charging history of the battery; andtransmitting, by the vehicle, a notification to a server remote from the vehicle, the notification including at least a portion of the data gathered from the battery.

6. The method of claim 1, comprising: in response to the vehicle being damaged, the vehicle gathering data from a condition of an occupant in the vehicle; anddetermining the physical condition of the battery based at least in part on a location in the vehicle of the occupant and a threshold of the condition of the occupant.

7. The method of claim 1, comprising: receiving data from a telematics unit of the vehicle;determining a probability of an accident for the vehicle by analyzing the received data, wherein the received data comprises one or more of: a speed of the vehicle, a change of speed of the vehicle before the vehicle was damaged, a change of speed of the vehicle after the vehicle was damaged, or a number of days for which the vehicle has not been driven; anddetermining the physical condition of the battery based upon the determined probability of the accident.

8. A system, comprising: a processor; anda memory, wherein the processor and the memory are communicably coupled, wherein the processor:determines, by a vehicle that has been damaged, a health of a battery in the vehicle, wherein the health is related to a capacity and a physical condition of the battery;determines, by the vehicle, an accessibility of the battery; anddetermines, by the vehicle, a future use of the battery, based on the determined health and the determined accessibility.

9. The system of claim 8 wherein, in response to the vehicle being damaged, gathers, by the vehicle, location data of the vehicle; and transmits, by the vehicle, a notification to a server remote from the vehicle, the notification including a current location of the vehicle.

10. The system of claim 8, wherein the processor: determines whether or not the capacity of the battery is above a threshold;in response to the capacity being above the threshold, determines that the future use of the battery is to be deployed on another vehicle;in response to the capacity being below the threshold by a first amount, determines that the battery is to be used for at least one of a backup battery for the another vehicle, or in an on-premises energy storage device; andin response to the capacity being below the threshold by a second amount, determines that one or more materials are to be harvested from the battery, wherein the second amount is greater than the first amount.

11. The system of claim 8, wherein: in response to at least one of the physical condition or the capacity of the battery being above a threshold, determines a first recommended amount of time to recover the battery based at least in part on the determined accessibility, and transmits a notification indicative of the first recommended amount of time to recover the battery; andin response to at least one of the physical condition or the capacity of the battery being below the threshold, determines a second recommended amount of time to recover the battery based at least in part on the determined accessibility, and transmits a notification indicative of the second recommended amount of time to recover the battery;wherein the first recommended amount of time is greater than the second recommended amount of time.

12. The system of claim 8, wherein: in response to the vehicle being damaged, gathers data, by the vehicle, from the battery, wherein the data comprises one or more of the capacity of the battery, an age of the battery, the accessibility of the battery, or a charge history of the battery; andtransmits, by the vehicle, a notification to a server remote from the vehicle, the notification including at least a portion of the data gathered from the battery.

13. The system of claim 8, wherein: in response to the vehicle being damaged, the vehicle gathers data from a condition of an occupant in the vehicle; and determines the physical condition of the battery based at least in part on a location in the vehicle of the occupant and a threshold of the condition of the occupant.

14. The system of claim 8, wherein the processor: receives data from a telematics unit of the vehicle;analyzes the received data to determine a probability of an accident for the vehicle, wherein the received data comprises one or more of: a speed of the vehicle, a change of speed of the vehicle before the vehicle was damaged, a change of speed of the vehicle after the vehicle was damaged, or a number of days for which the vehicle has not been driven; anddetermines the physical condition of the battery based upon the determined probability of the accident.

15. A computer-readable storage medium comprising instructions that, when read by a processor, cause the processor to perform: determining, by a vehicle that has been damaged, a health of a battery in the vehicle, wherein the health is related to a capacity and a physical condition of the battery;determining, by the vehicle, an accessibility of the battery; anddetermining, by the vehicle, a future use of the battery, based on the determined health and the determined accessibility.

16. The computer-readable storage medium of claim 15, further comprising instructions for: gathering, by the vehicle, location data of the vehicle in response to the vehicle being damaged; andtransmitting, by the vehicle, a notification to a server remote from the vehicle, the notification including a current location of the vehicle.

17. The computer-readable storage medium of claim 15, further comprising instructions for: determining whether or not the capacity of the battery is above a threshold;in response to the capacity being above the threshold, determining that the future use of the battery is to be deployed on another vehicle;in response to the capacity being below the threshold by a first amount, determining that the battery is to be used for at least one of a backup battery for the another vehicle, or in an on-premises energy storage device; andin response to the capacity being below the threshold by a second amount, determining that one or more materials are to be harvested from the battery, wherein the second amount is greater than the first amount.

18. The computer-readable storage medium of claim 15, further comprising instructions for: in response to at least one of the physical condition or the capacity of the battery being above a threshold, determining a first recommended amount of time for recovering the battery based at least in part on the determined accessibility, and transmitting a notification indicative of the first recommended amount of time for recovering the battery; andin response to at least one of the physical condition or the capacity of the battery being below the threshold, determining a second recommended amount of time for recovering the battery based at least in part on the determined accessibility, and transmitting a notification indicative of the second recommended amount of time for recovering the battery;wherein the first recommended amount of time is greater than the second recommended amount of time.

19. The computer-readable storage medium of claim 15, further comprising instructions for: in response to the vehicle being damaged, gathering by the vehicle, data from the battery, the data comprising one or more of the capacity of the battery, an age of the battery, the accessibility of the battery or a charging history of the battery; andtransmitting, by the vehicle, a notification to a server remote from the vehicle, the notification including at least a portion of the data gathered from the battery.

20. The computer-readable storage medium of claim 15, further comprising instructions for: receiving data from a telematics unit of the vehicle;determining a probability of an accident for the vehicle by analyzing the received data, wherein the received data comprises one or more of: a speed of the vehicle, a change of speed of the vehicle before the vehicle was damaged, a change of speed of the vehicle after the vehicle was damaged, or a number of days for which the vehicle has not been driven; anddetermining the physical condition of the battery based upon the determined probability of the accident.