DESC:TECHNICAL FIELD
[0001] Various embodiments of the disclosure relate generally to rechargeable batteries, and more specifically the management of energy ecosystems including rechargeable batteries coupled to electric systems.
BACKGROUND OF THE INVENTION
[0002] Upcoming energy-consuming systems such as power backup systems, transportation systems are mainly focused on electric systems equipped with rechargeable batteries (or batteries) as sustainable options compared to traditional internal combustion engines (ICE). Accordingly, demand for such electric systems such as electric power backup systems and electric vehicles (EVs) is continuously increasing as the world moves towards sustainable energy.
[0003] Many business decisions taken in an energy ecosystem such as financing of the electric systems, reselling of the electric systems, identifying components of the electric systems to be recycled/replaced, providing loans, insurance etc. are based, in part, on various parameters such as performance, residual life etc. of the batteries coupled with the electric systems. These parameters usually depend on the usage and handling of the batteries as well as the electric systems. For instance, a residual value of a battery depends on its operation, charging and discharging cycles and associated parameters such as charging frequency, duration of charging, charging and discharging rates etc., and the operation of an electric system equipped or coupled with the battery. However, availability and validation of any information regarding the operation and performance of the batteries and the electric system equipped with the battery may be challenging as information related to charging of the battery, information related to the operation of the electric system and the battery are recorded on different centralized databases. Accordingly, financing options for such electric systems are limited due to lack of availability and validation of data and limited knowledge related to the electric systems and the batteries coupled to them.
SUMMARY OF THE INVENTION
[0004] According to an embodiment of the present disclosure, a method of managing an energy ecosystem including a battery is provided. The method includes retrieving data related to an asset that includes a rechargeable battery coupled with an electric system from a distributed ledger of a blockchain system having a plurality of nodes. The plurality of nodes include the asset, an asset manufacturer, a power source and one or more financial service providers. The method includes determining performance parameters corresponding to the asset based on the retrieved data and generating a performance value corresponding to the asset based on the retrieved data and the performance parameters. The method further includes updating the performance value in the distributed ledger. In some embodiments, the method further includes assigning a reward or a penalty to the asset based on the performance value in the distributed ledger.
[0005] These and other features and advantages of the present disclosure may be appreciated from a review of the following detailed description of the present disclosure, along with the accompanying figures in which like reference numerals refer to like parts throughout.
BRIEF DESCRIPTION OF THE DRAWINGS
[0006] The accompanying drawings illustrate the various embodiments of systems, methods, and other aspects of the disclosure. It will be apparent to a person skilled in the art that the illustrated element boundaries (e.g., boxes, groups of boxes, or other shapes) in the figures represent one example of the boundaries. In some examples, one element may be designed as multiple elements, or multiple elements may be designed as one element. In some examples, an element shown as an internal component of one element may be implemented as an external component in another, and vice versa.
[0007] Various embodiments of the present disclosure are illustrated by way of example, and not limited by the appended figures, in which like references indicate similar elements.
[0008] FIG. 1 illustrates a block diagram of a computing environment for the management of an energy ecosystem including a rechargeable battery, in accordance with an embodiment of the present disclosure.
[0009] FIG. 2 is a flow chart providing a method of managing an energy ecosystem including a rechargeable battery, in accordance with an embodiment of the present disclosure.
[0010] FIG. 3 is a table 300 that shows examples of the operation of an EV coupled to a rechargeable battery on three different days.
[0011] Further areas of applicability of the present disclosure will become apparent from the detailed description provided hereinafter. It should be understood that the detailed description of embodiments is intended for illustration purposes only and is, therefore, not intended to necessarily limit the scope of the disclosure.
DETAILED DESCRIPTION OF THE INVENTION
[0012] The following description illustrates some embodiments of the disclosed disclosure in detail. Those of skill in the art will recognize that there are numerous variations and modifications of this disclosure that are encompassed by its scope. Accordingly, the description of a certain embodiment should not be deemed to limit the scope of the present disclosure.
[0013] The term “comprising” as used herein is synonymous with “including” or “containing” and is inclusive or open-ended and does not exclude additional, unrecited elements, or method steps.
[0014] All numbers expressing quantities of ingredients, property measurements, and so forth used in the specification are to be understood as being modified in all instances by the term “about.” Accordingly, unless indicated to the contrary, the numerical parameters set forth herein are approximations that may vary depending upon the desired properties sought to be obtained.
[0015] An energy ecosystem refers to a network of entities, technologies and infrastructure that support energy production, distribution, management and use. In an embodiment, the energy ecosystem refers to an ecosystem that includes rechargeable batteries and supports the production, distribution, management and use of energy generated/provided by rechargeable batteries.
[0016] An asset, as used herein, refers to an electric system and a rechargeable battery (or battery), individually and in combination. In an embodiment, the asset includes an electric system coupled with a battery. An asset manufacturer may be a manufacturer of a battery, a manufacturer of an electric system or a manufacturer of both. The manufacturer may be an original equipment manufacturer (OEM), original design manufacturer (ODM) or original brand manufacturer (OBM). In an example, the manufacturer may be an entity that assembles an electric system and a battery such that the battery provides power to the electric system.
[0017] Embodiments of the present disclosure provide methods of managing an energy ecosystem including a rechargeable battery. In particular, the disclosed embodiments provide methods of managing an energy ecosystem including a rechargeable battery coupled to an electric system The disclosed methods use a blockchain system for sharing, interpreting and validating information related to the operation and use of an asset including a battery coupled with an electric system in the ecosystem. This way, the disclosed methods provide a single and secure decentralized platform to store and share the information. This simplifies the validation processes and improves the financing options such as loans, insurance, resale of the asset etc. in the energy ecosystems and thereby improves the adoption of the assets.
[0018] A “blockchain” may include a distributed ledger for maintaining records of a sequence of executed transactions in blocks, which are linked cryptographically. In such examples, a “block” of a blockchain may be a unit of data recordation for the blockchain. In such examples, a given block of a blockchain may contain information to record a given transaction, and a block signature (for example, a hash or cryptographic hash) of a prior block to link the given block and the prior block. This way, blocks may be chained together in the blockchain by including in a given block the signature of a prior block of the blockchain. Such chaining of blocks may enable confirmation of the integrity of block in a blockchain and make it difficult to alter a block in the blockchain without such alteration being readily detectable. In some examples, a blockchain may be implemented by a blockchain system, which may comprise a plurality of computing devices to implement the blockchain system. In such examples, the blockchain system may implement a blockchain as a distributed ledger, which is a form of a decentralized database that may be stored at one or more entities participating in the blockchain system (e.g., blockchain nodes, such as respective computing devices). In such examples, each entity participating in a blockchain system may get a copy of the blockchain (i.e. the distributed ledger), which may be downloaded automatically upon enrolling (e.g., registering as per a registration model to access the blockchain system) for the blockchain system. At least some blockchain nodes may maintain the blockchain and cryptographically validate each new block added to the blockchain, and the transaction(s) represented in the corresponding block. The blockchain system may record information identifying the blockchain nodes and information identifying an owner of each block. An owner of a block may be a blockchain node that provides data to create that block in the distributed ledger. Whenever a transaction (including information related to the transaction) is recorded or updated in the distributed ledger, each participant entity or node of the blockchain system may get its copy of the distributed ledger updated with the information.
[0019] FIG. 1 is a block diagram of a computing environment 100 of at least a portion of an energy ecosystem, in an embodiment. The computing environment 100 includes a blockchain system 110 having a plurality of nodes 120 (120a, 120b, 120c, 120d, collectively referred to as 120). The blockchain system 110 includes a distributed ledger 112 that contains information in a blockchain and a management device 114 that performs several functions to update and retrieve information from the distributed ledger 112. In such examples, the management device 114 may perform these functions according to various blockchain protocols and specifications. In the example as described herein, the distributed ledger 112 may be implemented as a private distributed ledger. In some examples, the blockchain system 110 may further include an authorization system (not shown in FIG. 1) to permit or restrict a node, for example a service provider or a third-party agency to access the distributed ledger 112. In an example, the blockchain system 110 may further include a smart contract that is a deterministic module executed within a sandbox, ensuring that a transaction for example, the information to be recorded in the distributed ledger 112 is valid and unique.
[0020] A blockchain system generally records a plurality of transactions between at least two nodes of a plurality of nodes. The term “transaction” may refer to data transmission across the blockchain system’s network of computers. In the embodiments disclosed herein, the blockchain system may record any information related to the operation of a battery and an electric system coupled to the battery, and any details about financial transactions, loan agreement, identity records, maintenance, sale or resale etc. related to the battery and the energy system.
[0021] In an example, the blockchain system 110 may be communicatively associated with various components of the computing environment 100 for example, the plurality of nodes 120 via a wired or wireless network. In examples described herein, the network may include, for example, a local area network (LAN), a virtual LAN (ULAN), a wireless local area network (WLAN), a virtual private network (VPN), the Internet, or the like.
[0022] Most of the functionalities such as formation of blocks of the blockchain, updating any data or information in the distributed ledger 112, permitting or restricting a node accessing the distributed ledger 112, etc. performed by the blockchain system 110 (e.g., performed by any of management device 114, smart contract, and authorization system) may be performed by at least one processing resource of at least one computing device executing instructions perform those functionalities described herein.
[0023] The management device 114 may be a computing device that may be any suitable type of computing device as described herein. For the sake of simplicity, the functions performed by at least one processing resource in the management device 114 may be considered to be performed by the blockchain system 110. In other words, most of the functionalities performed by blockchain system may be performed by instructions stored on at least one machine readable storage medium of the management device 114, executed by the at least one processing resource of the management device 114. The at least one machine readable storage medium may be non-transitory and alternatively referred to as a non-transitory machine readable medium. The at least one machine readable storage medium may be implemented by volatile memory (e.g., one or more volatile memory devices, such as DRAM device(s), DIMM(s), or the like).
[0024] As used herein, a “computing device” may be a server, storage system, storage array, desktop or laptop computer, switch, router, or any other processing device or equipment including a processing resource. In examples described herein, a processing resource may include, for example, one processor or multiple processors included in a single computing device or distributed across multiple computing devices. As used herein, a “processor” may be at least one of a central processing unit (CPU), a semiconductor-based microprocessor, a graphics processing unit (GPU), a field-programmable gate array (FPGA) configured to retrieve and execute instructions, other electronic circuitry suitable for the retrieval and execution instructions stored on a machine-readable storage medium, or a combination thereof. In examples described herein, a processing resource may fetch, decode, and execute instructions stored on a storage medium to perform the functionalities described in relation to the instructions stored on the storage medium. The storage medium may be located either in the computing device executing the machine-readable instructions or remote to the computing device but accessible to the computing device (e.g., via a computer network) for execution.
[0025] As illustrated in FIG. 1, the blockchain system 110 is associated with an asset 120a that belongs to the plurality of nodes 120. The blockchain system 110 is configured to receive data from the asset 120a and update the data to the distributed ledger 112. The data from the asset 120a may be received periodically or randomly. In an embodiment, the data from the asset 120a may be received periodically in a predefined time interval. The time interval may be in hours, days or weeks. In an example, the time interval may be 1 hour, 5 hours, 10 hours,1 day, 1 week, or the like. In some embodiments, more than one asset may be associated with the blockchain system 110.
[0026] The asset 120a includes a battery 124 coupled with an electric system 122. The term “coupled” means that the energy storage system 124 is electrically connected to the electric system 122. In an embodiment, the electric system 122 is an electric vehicle (EV) coupled with the battery 124. An EV is a vehicle that is powered by an electric motor that draws electricity from a battery and is capable of being charged from an external source of electricity. In another embodiment, the electric system 122 may be a power backup system coupled with the battery 124 e.g., an emergency backup system, a grid stabilization system, or the like. The power backup system may be defined as any device that provides instantaneous, uninterruptible power when the main power sources are not available or unable to meet the power demand.
[0027] A battery or rechargeable battery may be defined as an electrochemical device which converts chemical energy into electrical energy and vice versa. Non limiting examples of the rechargeable battery 124 may include lithium-ion battery, sodium ion battery, lithium-sulfur battery or the like. The rechargeable battery 124 may include one or more electrochemical cells (hereinafter referred to as “cells”) connected in series/parallel. A typical electrochemical cell may include an anode, a cathode, a separator, an electrolyte and current collectors. The electrochemical cell may use reversible reduction of ions (for example, Li ions in a lithium-ion battery cell or Na ions in a sodium-ion battery cell, respectively) to store energy.
[0028] In an embodiment, the electrochemical cell may be a lithium-ion cell. Further, depending on the chemistry i.e., the compositions of the anode and the cathode, the lithium-ion cell may include, but is not limited to, a lithium titanium oxide (LTO) cell, lithium iron phosphate (LFP) cell, lithium nickel manganese cobalt oxide (NMC) cell, lithium cobalt oxide (LCO) cell, lithium nickel cobalt aluminum oxide (NCA) cell, lithium manganese oxide (LMO) or lithium manganese iron phosphate (LMFP). It should be noted that the cells in the rechargeable battery are of the same type or have the same chemistry. In an embodiment, the cells are the same with respect to their components and the materials used for the components.
[0029] Apart from the asset 120a, the plurality of nodes 120 includes an asset manufacturer 120b, a power source 120c and one or more financial service providers 120d. The asset manufacturer 102b may include one or more companies that has provided the asset 120a, electric system 122 or battery 124. The asset manufacturer 120b may also provide services to the asset 120a. The asset manufacturer 120b may retrieve the data related to the asset 120a from the distributed ledger 112.
[0030] The power source 120c may include a charging source for the battery 124 of the electric system 122. For example, the charging source may include a plurality of charging stations (e.g., level one charging station, level two charging station, and level three charging station). In an example, the charging source may be a charge point operator (CPO). When the asset 120a utilizes the power source 120c for charging the battery 124, the power source 120c may identify and authenticate the asset 120a and may update the ledger 112 with the charging related information of the battery 124 such as charging rate, voltage, frequency of charging of the asset 120a etc.
[0031] The term “financial service provider” refers to an entity or an organization that provides finance related services such as insurance, resale services, loan etc. to one or more other parties such as an asset manufacturer, asset owner or manager etc. Examples of the one or more financial service providers 120d may include, but are not limited to, a finance company, an insurance company, an asset resale company, or a bank. Other examples of financial service provide may also include a token partner, or a franchise operator. The one or more financial service providers 120d, for example, the insurance company may provide insurance coverage and risk management solution for the asset 120a to an asset owner or manager. The token partner may collaborate with the other nodes (e.g., the asset manufacturer 120b or power source 120c) of the blockchain system 110 for a reward program to incentivize the asset owner or the manager for improved and optimal use of the asset 120a. An asset owner or manager is an individual or an entity who owns or manages the asset. For example, the asset owner or manager may be an owner of the electric system e.g., EV or a power backup system or a fleet operator who owns commercial EVs.
[0032] An asset user is an individual who operates the asset. For example, the asset user may be a driver who drives an EV or an operator of a power backup system. The asset resale company may correspond to a reseller that specializes in buying and selling the assets including EVs and batteries.
[0033] A node of the plurality of nodes 120 may have a role-based access to the blockchain system 110 according to the blockchain protocols and specifications. For example, a node such as the asset manufacturer 120b may have read and write access while another node such as the asset 120a or a financial service provider 120d may have read only access. Further, as alluded previously, in some examples, the nodes of the plurality of nodes may access the distributed ledger 112 in the blockchain system 110 through the authorization system that may permit or restrict respective node to access the distributed ledger 112 according to the blockchain protocols and specifications
[0034] In an embodiment, one or more nodes (except the asset 120a) of the plurality of the nodes 120 may retrieve data related to the asset 120a from the distributed ledger 112 to monitor and analyze the performance, health, and safety of the asset 120a. In an example, the asset manufacturer 120b retrieves the data related to the asset 120a.
[0035] The data related to the asset 120a may be obtained from a management system coupled with the asset 120a. The management system of the asset 120a may provide the data to the blockchain system 110, which is then updated and stored in the distributed ledger 112. The management system of the asset 120a may include a battery management system (BMS), telematics and CAN (Controller Area Network) bus. The BMS may be associated with the battery 124 to manage and monitor its performance, health, and safety. For example, the BMS performs several operations related to charging and discharging, thermal management, cell balancing of the battery, and the like. The BMS provides data related to the battery 124 to the blockchain system 110.
[0036] In an embodiment, the data related to the asset 120a may include a first data related to the battery 124 and a second data related to the operation of the electric system 122. In an embodiment, the first data is received, by the blockchain system 110, from the BMS of the battery 124. The first data may include data related to charging and discharging of the battery 124. In an example, the first data includes voltage values, current values, a maximum temperature, a minimum temperature, state of charge (SOC) values, a charging rate, a discharging rate etc. during charging and discharging of the battery 124. In addition, the first data includes voltage values, current values, a maximum temperature, a minimum temperature, SOC values, a rate of charge, a rate of discharge of individual cells, a string (a string refers to two or more cells connected in series) during each charging and discharging of the battery 124, in some instances
[0037] The term “SOC” represents the percentage of energy stored in a battery or a cell or a string relative to its full capacity. The term “charging rate” and “discharging rate” may correspond to a measure of the rate at which a cell or a battery is charged or discharged, respectively, relative to a maximum capacity of the cell. For example, as a charging or discharging rate of a type of cell (e.g., LFP cell) may be 1 Coulomb (C), time required to charge the cell may be one hour, while when a charging rate of another type of cell (e.g., LTO cell) may be around 10C, the time required to charge this other type of cell is significantly faster as compared to the previous type of cell. Furthermore, the cycle life of LTO cells may be impacted by several factors such as a charging or discharging rate, an operating temperature, cell chemistry, or the like. The “cycle life” of a battery represents the number of times a battery can be charged and discharged over its lifetime. For example, the LTO cells have the capability to handle over 40,000 cycles at the charging and discharging rate of 1C and can last up to 20 years. The lifecycle of the LTO cell may reduce if the charging rate or discharging rate is higher than 1C rate or charging or discharging at a higher temperature than 25 °C (77 °F). Thus, the performance of the battery 124 is greatly dependent on its usage i.e., the way of handling during its use or operation.
[0038] The second data related to the operation of the electric system 122 is received, by the blockchain system 110, from the telematics coupled with the electric system 122. The second data may include operating status (Running or Idle or Charging) of the electric system, load on the electric system, operating hours and the like. In embodiments when the electric system is an electric vehicle, the second data may further include odometer readings, longitude and latitude of the telemetry, speed reported by GPS, vehicle mode (economy or power) or the like. The idle status of a vehicle may be defined as a period of time (idle time) when a vehicle's engine is running, but not moving. For example, a vehicle may be idle for short periods in congested traffic or for extended stretches when deliveries are being made. In this scenario, as an engine of the vehicle is running, energy is unnecessarily consumed. The idle time of a vehicle may be predetermined based on parameters such as SOC, voltage, distance travelled by vehicle, and zero discharge of the battery. The second data may further include information about other factors such as load on electric systems, number of deliveries, idle time etc. This information may be provided by an asset user or manager to the electric system 122, and the telematics of the electric system 122 may provide it to the blockchain system 110. Accordingly, the second data partly depends on the behavior of asset user while operating the asset 102a e.g., the way a driver drives an EV.
[0039] In an embodiment the one or more nodes (except the asset 120a) of the plurality of nodes 120 may determine a set of performance parameters corresponding to the asset 120a based on the retrieved data (that includes the first data, the second data or both). The performance parameters may correspond to the factors which impact the energy consumption, performance or both of the asset 120a. In an embodiment, the performance parameters corresponding to the asset 120a may include a first set of performance parameters related to the battery 124 and a second set of performance parameters related to the operation of the electric system 122.
[0040] In an example, the first set of performance parameters may be determined based on the first data related to the battery 124. In an embodiment, the asset manufacturer 120b may determine the first set of performance parameters related to the battery 124 based on the first data retrieved from the distributed ledger 112. The asset manufacturer 120a may use the first data from historical data or the most recent data at an instant of time from the distributed ledger 112 to determine one or more performance parameters of the first set of performance parameters. The first set of performance parameters may include state-of health (SOH) degradation, remaining useful life or residual life of the battery 124. ’SOH’ of a battery is a measure of the overall health and performance of the battery over time and is defined as the total available charged capacity of the battery as a percentage compared to the nominal capacity (capacity of a newly assembled battery). Remaining useful life (RUL) of a battery may be defined as the number of remaining charge/discharge cycles before the end of life (EOL). Generally, a battery's lifespan ends when its remaining capacity reaches 70–80% of its initial value.
[0041] The second set of performance parameters may be obtained from the second data related to the operation of the electric system 122. In an embodiment, the asset manufacturer 120b may determine the second set of performance parameters related to the operation of the electric system 122 based on the second data retrieved from the distributed ledger 112. The asset manufacturer 120a may use the second data from historical data or the most recent data at an instant of time from the distributed ledger 112 to determine one or more performance parameters of the second set of performance parameters. The second set of performance parameters may include operational performance parameters of the electric system 122. In an example, the second set of performance parameters may include mileage, actuation etc.
[0042] The behavior of an asset user may impact the energy consumption and performance of the asset 120a as it may be handled or used by different asset users throughout its operation. For example, an EV in the commercial vehicle category generally faces transition across multiple drivers. Every driver has a certain style of driving, which needs to be adapted as per the condition of the EV and the battery coupled to the EV or the route of operation selected by the driver. Accordingly, the behavior of the one or more drivers may impact the energy consumption and the performance of the EV. The behavior of an asset user may include qualitative and quantitative parameters such as charging timelines including charging frequency and duration of charging, route planning of an EV, the way of operating the electric system 122, load management in case of power backup system, etc.
[0043] In an embodiment, information about each asset user e.g., driver of an EV may be added to the distributed ledger 112 for the identification of the driver. The information about each driver may include identification details such as name, Date of Birth (DOB), address, photo, Adhar card number, license number etc.
[0044] Once the performance parameters are determined, a performance value corresponding to the asset 120a may be generated by the one or more nodes 120 (except the asset 120a) based on the retrieved data and the performance parameters. In an embodiment, one or more nodes of the plurality of nodes 120 may generate the performance value by analyzing and accessing the retrieved data and/or performance parameters. For example, the asset manufacturer 120b may generate a performance value corresponding to the asset 120a. In an example, a charging station may generate a performance value corresponding to the asset 120a. The performance value may be a quantitative value (for example, a score) indicative of the overall performance of the asset 120a or the behavior of an asset user relative to BOL (beginning of life) performance of the asset 120a or the ideal behavior of the same or other asset user. The BOL performance defines specifications and performance of a newly manufactured battery. The quantitative value may be provided in arithmetic numerals, geometric numerals, roman numbers, or the like. The best performance of the asset 120a may be the performance of the asset 120a when the energy consumption of the battery is comparatively minimum and the performance of the asset 120a is comparatively maximum based on the performance parameters of the asset. The ideal behavior of the asset user may be defined as per the set of rules or guidelines provided by the one or more of the plurality of nodes 120 and accepted by the majority of nodes 120. In an embodiment, the performance value may include an asset score corresponding to the battery 124 of the asset 120a based on the first set of performance parameters and an asset user score corresponding to the asset user of the asset 120a based on the second set of performance parameters. In an example, the asset score and the asset user score, individually, may vary from 0 to 10, 0 to 50, 0 to 100, or the like. For example, Table 300 of FIG. 3 shows operation of an EV on three different days. Table 300 is described below in detail.
[0045] After generating the performance value, the one or more nodes (except the asset 120a) of the plurality of nodes 120 may update the performance value in the distributed ledger 112. In an example, the asset manufacturer 120b of the asset 120a determines the first set of performance parameters related to the battery 124 based on the first data. The asset manufacturer 120b may generate an asset score based on the first set of performance parameters and the first data, and update the asset score in the distributed ledger 112. In another embodiment, the asset manufacturer 120b of the asset 120a determines the second set of performance parameters related to the electric system 122 based on the second data. The asset manufacturer 120b may generate an asset user score based on the second set of performance parameters and the second data, and update the asset user score in the distributed ledger 112.
[0046] Based on the performance value, the one or more nodes (except the asset 120a) of the plurality of nodes 120 may assign a reward or a penalty to the asset 120a in the distributed ledger 112 based on the performance value. The reward or the penalty may be assigned to the asset 120a based on a comparison of the performance value and a threshold value. In an embodiment, the threshold value may be defined by all nodes or majority of nodes of the plurality of nodes 120. In an example, the plurality of nodes 120 may define a first threshold value corresponding to the asset 120a and a second threshold value corresponding to an asset user of the asset 120a. In these examples, the first and second threshold values may be defined in the same numerals as the asset score and the asset user score, respectively. In an embodiment, a reward or a penalty may be assigned to the asset 120a based on the comparison of the asset score and the first threshold value, the comparison of the asset user score and the second threshold value or both. In such embodiment, an asset owner or a manager of the asset 120a or a fleet operator supervises the distribution of the assigned reward or penalty among the asset users (e.g., among EV owner and driver(s) or among drivers).
[0047] In an example, the asset manufacturer 120b of the asset 120a may assign a reward or a penalty to the asset 120a including the battery 124 and the electric system 122 in the distributed ledger 112 on determining the first set of performance parameters related to the battery 124 and the second set of performance parameters related to the operation of the electric system 122, respectively. Assigning a reward or penalty in the distributed ledger 112 may mean that information related to allocating the reward or the penalty to the asset 120a is updated in the distributed ledger 112. On updating the information in the distributed ledger 112, each copy of the distributed ledger 112 of each node 120 gets updated and the information is shared with each node 120 of the blockchain system 110.
[0048] In an embodiment, the reward may include a blockchain token, a service voucher or reward points based on the performance value. Examples of the blockchain tokens may include utility tokens that may be used to avail services with the blockchain system 110, wrapped tokens that may function as a medium of exchange across a plurality of blockchains (e.g., wrapped Bitcoin, wrapped Ether, and wrapped Litecoin), or the like. The blockchain token may be provided by a token partner that belongs to the plurality of nodes 120. In an embodiment, the penalty includes devaluation of a blockchain token, deduction of reward points or deactivating service vouchers. Based on the assigned reward to the asset 120a, the asset owner or manager may redeem and then distribute the reward among the asset and asset user(s) according to the asset score and asset user score(s). In case of rewarding the asset, the asset owner or manager may redeem one or more services offered by the CPO 120c, the asset manufacturer 120b or one or more financial service providers 120d of the blockchain system 110 at discounted rates or for free. In case of a penalty assigned to the asset 120a, the asset owner or manager may penalize the asset and the asset user(s) according to the asset score and asset user score.
[0049] In an example, a financial service provider e.g., an insurance partner may determine from a distributed ledger that an asset score to an EV is more than a predefined threshold value (i.e., a second threshold value). The asset score to the EV corresponds to a residual value of the EV. The “residual value” of an EV may be determined by determining the remaining useful life of a battery after a number of charge/discharge cycles. On determining that the asset score to EV is more than the predefined second threshold value, the insurance partner may assign reward to the EV. For example, the insurance partner may provide a discount voucher on the next insurance premium for the EV to the owner of the EV. Similarly, when the residual value of the EV is less, an asset score to the EV is lower than the predefined second threshold value, the insurance partner may penalize the EV, i.e., the owner of the EV. In an example, based on the asset score corresponding to the residual life of a battery or an EV in the distributed ledger 112, a resale company may provide a price quotation equivalent to the residual value of the EV to the owner or manager of the EV.
[0050] In another example, a charge point operator (CPO) provides a set of rules for an asset user to adhere to. The CPO may identify instances when an asset user does not abide by the set of rules (discussed above) and may accordingly update the ledger 112 with a low asset user score (i.e., lower than the second threshold value). Alternatively, the CPO may identify instances when the asset user abides by the set of rules and may update the ledger 112 with a high asset user score (higher than the second threshold value), accordingly. Based on the updated asset user score in the distributed ledger 112, the CPO or any other node of the plurality of nodes 120 may assign a reward or a penalty to the asset 120a.
[0051] FIG. 2 is a flow chart depicting a method 200 of managing an energy ecosystem including a battery, in accordance with an embodiment of the present disclosure. For ease of illustration, the method 200 is described with reference to FIG. 1.
[0052] The method 200 at step 202, includes retrieving data related to the asset 120a from a distributed ledger 112 of a blockchain system 110 having a plurality of nodes 120. In an embodiment, an asset manufacturer 120b may retrieve the data. In an embodiment, the asset may include a battery 124 coupled with an electric system 122. In an embodiment, the retrieved data related to the asset 120a may include a first data related to a rechargeable battery and a second data related to the operation of the electric system.
[0053] The method 200, at step 204, includes determining performance parameters of the asset 120a based on the retrieved data. In an embodiment, the asset manufacturer 120b may determine the performance parameters. In an embodiment, the performance parameters may include a first set of performance parameters and a second set of performance parameters. The first set of performance parameters may be obtained from the first data related to the battery 124 and the second set of parameters may be obtained from the second data related to the operations of the electric system 122. The first set of parameters may include SOH degradation, residual life/remaining useful life or the like. The second set of performance parameters may include the behavior of an asset user and operational performance parameters of the electric system 122.
[0054] The method 200, at step 206, includes generating a performance value corresponding to the asset 120a based on the retrieved data and the performance parameters. In an embodiment, the asset manufacturer 120b may generate the performance value. In an embodiment, the performance value may include an asset score, an asset user score or both the asset score and the asset user score. The asset score corresponding to the battery 124 of the asset 120a may be generated based on the first set of performance parameters and an asset user score corresponding to the asset user of the asset 120a may be generated based on the second set of performance parameters.
[0055] The method 200, at step 208, includes updating the performance value in the distributed ledger 112. In an embodiment, the asset manufacturer 120b may update the performance value. In an embodiment, the performance value including asset score, and asset user score may be updated in the distributed ledger 112 by one or more nodes (except the asset 120a) of the plurality of nodes 120.
[0056] The method 200, at step 210, further includes assigning a reward or a penalty to the asset 120a based on the performance value in the distributed ledger 112. In an embodiment, the one or more financial service providers 120d may assign the reward or the penalty. In another embodiment, the asset manufacturer120a may assign the reward or the penalty.In an embodiment, the reward or the penalty may be assigned based on a comparison of the performance value and a threshold value defined by all or majority of the plurality of nodes 120. In an embodiment, the threshold value may include a first threshold value corresponding to the asset and a second threshold value corresponding to the asset user of the asset and the first threshold value and the second threshold value may be defined by the plurality of nodes.
[0057] The following examples are included to describe one or more particular embodiments of the present disclosure. It should be noted that the processes disclosed in the examples follow merely represent exemplary embodiments of the present disclosure. However, as will be appreciated by those of skill in the art, in light of the present disclosure, changes can be made in the specific embodiments described and still a like or similar result can be obtained without departing from the spirit and scope of the present disclosure.
[0058] A lithium-ion battery (Li-ion battery) coupled with an EV was a node (Node 1) (referred to as EV hereinafter) of a plurality of nodes of a blockchain system similar to as illustrated in FIG. 1 and described with respect to FIG. 1. Another node of the plurality of nodes was a battery manufacturer (Node 2). Node 2 retrieved data from a distributed ledger of the blockchain system for three random days (day 1, day 2, day3) when the EV was driven by three different drivers (driver 1, driver 2, driver 3). The retrieved data included operational data related to the EV i.e., data related to the battery and the vehicle. Node 2 determined performance parameters (parameters of battery, behavior of the driver and operational parameters of the EV) related to the operation of the EV based on the retrieved data for the three days. Table 300 represents the performance parameters related to the operation of the EV driven on day 1, day2, and day3 in Example 1, Example 2 and Example 3, respectively.
[0059] The performance parameters of the EV, as shown in Table 300 of FIG. 3, include number of deliveries, idle time of the EV, mileage of the EV in kilometers (Km), energy consumption of the EV in watt-hours per kilometer (Wh/Km), discharging rates of the EV in amperes (A), Mean/Median Discharge current and Mean Discharge Current X No of pulses. The “Mean Discharge Current X No of pulses” is the product of the degree of actuation of the throttle (enabling discharge of the battery) and the frequency of actuation of the throttle. A good performance value to the driver is attributed to a constant current and minimal actuation.
[0060] Example 1: EV was driven on day 1 by driver 1. The number of deliveries made by driver 1 was 11. On that particular day, the mileage of the EV was recorded as 91 km on a single charge of the battery and the energy consumption of the EV was around 123 Wh/Km. Further, discharging rate of the EV through an entire journey was divided into three categories, for example, greater than 150A (>150A), between 50A-150A (50A-150A), and less than 50A (<50A). During the entire journey, the EV was driven with a discharging rate greater than 150A, between 50A-150A, and less than 50A for 2%, 24%, and 56% of the total running time, respectively. Additionally, the idle time for the EV was 34% of total operational time of the EV. The operational time refers to the time including running time and idle time. The mean/median discharge current was 1.43A and the mean current per pulse times pulses per kilometer for the EV was -651 which was obtained by multiplying mean discharge current per pulse i.e., -32.58 and the number of pulses per kilometer i.e., 20.
[0061] Example 2: EV was driven on day 2 by driver 2. The number of deliveries made by the driver was 13. On that particular day, the mileage of the EV was recorded as 58 Km on a single charge and the energy consumption for the EV was around 193 Wh/Km. Further, during the entire journey, the EV was driven with a discharging rate greater than 150A, between 50A-150A, and less than 50A for 12%, 21%, and 46% of the total time, respectively. Additionally, the idle time for the EV was 42% of the total operational time of the EV. The mean/median discharge current was 2.09A and the mean current per pulse times pulses per kilometer for the EV was -1016.
[0062] Example 3: EV was driven on day 3 by driver 3. The number of deliveries made by the driver was 12. On that particular day, the mileage of the EV was recorded as 78 km on a single charge and the energy consumption for the EV was around 142 Wh/Km. Further, during the entire journey, the EV was driven with a discharging rate greater than 150A, between 50A-150A, and less than 50A for 5%, 25%, and 52% of the total time, respectively. Additionally, the idle time for the EV was 40% of the total operational time of the EV. The mean/median discharge current was 1.59A and the mean current per pulse times pulses per kilometer for the EV was -766.
[0063] Since the performance parameters of the EV in example 1 were the best among the three examples, example 1 was considered as the best-case. The performance parameters of the EV in example 2 were significantly inferior to that of the example 1, thus example 2 was considered the worst-case. In addition, the performance parameters of the EV in the example 3 lied in-between the respective performance parameters of example 1 and example 2, so example 3 was considered as average case.
[0064] Based on the performance parameters in example 1, example 2 and example 3, performance values i.e., asset user score assigned to the EV (corresponding to respective drivers) may be on a scale of 0 to 100. For instance, the asset user score assigned to EV on day 1 (Example 1) may be 90, on day 2 (example2) may be 30 and on day 3(example3) may be 60.
BENEFICIAL EFFECTS
[0065] Embodiments of the present disclosure provide methods for managing ecosystems of batteries. The disclosed methods help in managing ecosystems of batteries by providing a secure and decentralized platform for energy ecosystem for sharing information (e.g., data and performance parameters) related to the operation and use of assets among the participants of the blockchain system. As any shared information may be validated by different participants, parameters such as residual value of the asset, resale value of the asset, second life of the asset based on the remaining useful life of the asset etc. may be determined based on predefined logics and processes accepted by the all or majority of the participants. The “second life of a battery” refers to new non-automotive uses after the first initial use in a vehicle. Based on these determinations, the financing options such as loans, insurance may be available at a lower interest rate, resale of the asset may be improved in energy ecosystem and thereby the adoption of the assets may be improved.
[0066] Another advantage of the disclosed systems and methods is to provide a single platform on which different types of assets like charging infrastructure, electric vehicles, stationary storage systems, etc. may be defined and added.
[0067] In light of the above-mentioned advantages and the technical advancements provided by the disclosed processes, the claimed steps as discussed above are not routine, conventional, or well understood in the art, as the claimed steps enable the following solutions to the existing problems in conventional technologies. Further, the claimed steps clearly bring an improvement in the functioning of the device itself as the claimed steps provide a technical solution to a technical problem.
[0068] The specification has described the methods for managing ecosystems of batteries. The illustrated steps are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for the purposes of illustration and are not limited. Although a method has been described with respect to managing a single asset using a blockchain system, in the above embodiments, the method may be applicable to multiple assets simultaneously. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0069] It is intended that the disclosure and examples be considered exemplary only, with a true scope and spirit of disclosed embodiments being indicated by the following claims.
,CLAIMS:1. A method of managing an energy ecosystem including a rechargeable battery, the method comprising:
retrieving data related to an asset comprising the rechargeable battery coupled with an electric system from a distributed ledger of a blockchain system having a plurality of nodes, wherein the plurality of nodes comprise the asset, an asset manufacturer, a power source and one or more financial service providers;
determining performance parameters of the asset based on the retrieved data;
generating a performance value corresponding to the asset based on the retrieved data and the performance parameters; and
updating the performance value in the distributed ledger.
2. The method as claimed in claim 1, comprising assigning a reward or a penalty to the asset based on the performance value in the distributed ledger.
3. The method as claimed in claim 1, wherein the one or more financial service providers comprise a finance company, an insurance company, an asset resale company, a token partner, or a franchise operator.
4. The method as claimed in claim 1, wherein the retrieved data related to the asset comprises a first data related to the battery and a second data related to the operation of the electric system.
5. The method as claimed in claim 1, wherein the performance parameters comprise a first set of performance parameters related to the battery and a second set of performance parameters related to the operation of the electric system.
6. The method as claimed in claim 1, wherein the first set of performance parameters related to the battery comprises state-of-health (SOH) degradation, residual life/remaining useful life of the battery.
7. The method as claimed in claim 1, wherein the performance value comprises an asset score, an asset user score or both the asset score and the asset user score.
8. The method as claimed in claim 1, wherein the reward comprises a blockchain token, a service voucher or reward points based on the performance value.
9. The method as claimed in claim 1, wherein the penalty comprises devaluation of a blockchain token, deduction of reward points or deactivating service vouchers.
10. The method as claimed in claim 1, wherein assigning the reward or the penalty comprises assigning the reward or the penalty based on a comparison of the performance value and a threshold value defined by the plurality of nodes.