Usage metric-based warranty for internet-of-things devices

Methods, computer program products, and systems are presented for warranty tracking and transactions based on usage metrics by use of blockchain. The methods include, for instance: obtaining a usage report of an IoT device in a predefined format. The usage report is recorded in a blockchain network, and a warranty balance, also recorded in the blockchain network, is updated in the amount corresponding to the usage report on the IoT device. A warranty claim is resolved based on records of the usage report and the warranty balance for the IoT device as recorded in the blockchain network.

TECHNICAL FIELD

The present disclosure relates to warranty for Internet of Things (IoT) devices, and more particularly to methods, computer program products, and systems for warranty tracking and transactions based on usage metrics by use of blockchain.

BACKGROUND

Conventionally, manufacturer's warranty on most products for refund, exchange, or repairs are period-based from a certain date. For example, it is common that the manufacturer's warranty covers an electrical/electronic device for a year from the date of purchase based on a registration within the first 90 days, or if the customer requests a repair with the purchase receipt and/or any other proof of purchase. Most manufacturers often inform customers on any conditions and/or events that might void the warranty on the products even within the warranty period, if such conditions and/or events during the use by the customer would cause the products to function not as originally described or intended without any defect on the product. Conventional warranty claims are often subject to dispute on what happened to the product in determining whether or not the product should be covered under the warranty.

SUMMARY

The shortcomings of the prior art are overcome, and additional advantages are provided, through the provision, in one aspect, of a method. The method includes, for instance, obtaining, by one or more processors, a usage report of an Internet of Things (IoT) device in a predefined format; recording, by the one or more processors, the usage report of the IoT device in a blockchain network; updating, by the one or more processors, a warranty balance for the IoT device by reducing an amount of the warranty balance corresponding to the usage report of the IoT device from a current value of the warranty balance, wherein the warranty balance for the IoT device is stored in the blockchain network; and resolving, by the one or more processors, a warranty claim on the IoT device based on respective blockchain records of the usage report and the warranty balance regarding the IoT device.

Additional features are realized through the techniques set forth herein. Other embodiments and aspects, including but not limited to computer program products and systems, are described in detail herein and are considered a part of the claimed invention.

DETAILED DESCRIPTION

As noted, conventional manufacturer's warranty on products are period-based from a certain date. However, certain working conditions and manners of use, even for a product with no defect within specified working conditions, can also affect how long the product would last and function well. Also, users may have vast differences in mannerism, use habits, and the level of care, so time-based manufacturer's warranty may not be fair for all users.

For certain warranty claims in conventional warranty systems, because there is no agreed account on how the product is in a certain state and the warranty claim came to be, manufacturers are often required to investigate such warranty claims, which drives up the cost of the product for all users.

The users often are asked to buy an extended warranty on products at the time of purchase, but users often do not feel the need for such extended warranty until they start using the product. Also, with the conventional warranty systems, users often forget to register the product and/or to keep the receipts or other proof of purchase, so when the users need the coverage under the warranty, it might not be successfully claimed even if the product should be covered by all means.

FIG.1depicts an enhanced warranty system100for Internet of Things (IoT) devices based on usage metrics, in accordance with one or more embodiments set forth herein.

The enhanced warranty system100provides transparently and unalterably shared record of usage of products based on communication networks and blockchain in offering a customized warranty system for respective products that can benefit both users and manufacturers. For example, if a laptop computer conventionally covered by a one-year manufacturer's warranty is actually based on an average eight (8) hours of daily use and the one-year warranty is supposed to cover a total of three thousand (3,000) hours of use for the first year from the date of purchase, a user who uses the laptop computer for two to three hours a day can have three or more years of manufacturer's warranty if the warranty is based on the usage rather than the simple one-year term, which can be beneficial to the user with less daily use and fair to all users.

The enhanced warranty system100includes one or more IoT devices subject to respective warranties and a blockchain network120that is a platform of the enhanced warranty system100. A manufacturer109is an entity that produces an IoT device110of the one or more IoT devices, and a user101purchases and/or uses the IoT device110for the purpose of a warranty corresponding to the IoT device110. The manufacturer109provides manufacturer's warranty on the IoT device110to the user101by use of the enhanced warranty system100. The blockchain network120can be established by the manufacturer109.

The user101accesses the blockchain network120by use of a user interface application (UIA)160for the enhanced warranty system100. The UIA160can be a mobile app running on a smartphone to view current usage data for the IoT device110and a current warranty balance on the IoT device110corresponding to the current usage data. The UIA160is also used to communicate and to further interact with the manufacturer109regarding the warranty of the IoT device110. For example, the UIA160can alert the user101on expiring warranty based on that the IoT device warranty balance value became less than a warranty balance threshold to alert the user101and recommend any extended warranty available to the user101.

The IoT device110includes a timer115, a sensor117, and any other mechanism embedded into the IoT device to detect conditions that affect the manufacturer's warranty on the IoT device110, as well as a process for communicating with the blockchain network120. The manufacturer109devised a set of working conditions that affect the manufacturer's warranty of the IoT device110, and configured the IoT device110to report by use of such detection mechanism including the timer115and the sensor117for the purpose of collecting data for the enhanced warranty system100. For example, the timer115can be conveniently implemented as a 555 timer Integrated Circuit (IC) on a printed circuit board (PCB) of the IoT device110along with other parts. A few examples of working conditions that affect the manufacturer's warranty of the IoT device110include, but not limited to, how often the IoT device110runs and intervals between run cycles, a length of each run cycle, a power level or other level of intensity of each run cycle, any environmental condition of the IoT device110including temperature and humidity, and any event that can void the manufacturer's warranty on the IoT device110such as submersion or a drop from a certain height, depending on a type and functionality of the IoT device110.

The IoT device110reports usage data to the blockchain network120, by use of a blockchain interface process as noted above. The IoT device110is uniquely identified with a certain identifier such as manufacturer's serial number, and the identifier is reported along with the usage data of the IoT device110. All blockchain nodes of the blockchain network120including the IoT device usage blockchain, the IoT device warranty balance blockchain, and the manufacturer blockchain would identify the IoT device110and associate respective usage data and warranty balances with the uniquely identified IoT device110. The blockchain nodes can further include other device metadata such as a model number, the date of manufacture, a material parts list, blockchain wallet addresses associated with the IoT device110, and any other information that can affect the warranty balance of the IoT device110at the moment or an availability of warranty extension in cases the user101wishes to have.

In the blockchain network120, the IoT device110is represented by an IoT device usage wallet130and an IoT device warranty balance wallet140. The IoT device usage wallet130and the IoT device warranty balance wallet140are identified by respective wallet addresses to be publicly shared amongst participants of the blockchain network120for access in viewing and verification. The IoT device usage wallet130and the IoT device warranty balance wallet140are loaded with respective credits that would be exhausted over time proportional to the usage of the IoT device110, and that would be replenished if the user101extends the warranty on the IoT device110.

The manufacturer109is represented by a manufacturer wallet150in the blockchain network120. Warranty data of the IoT device110subject to transactions by the manufacturer wallet150, which can be referred to as a manufacturer blockchain, can be optionally and/or occasionally replicated by a certification authority190. The certification authority190is a trusted third party outside of the blockchain network120for additional assurance on transparency and accuracy of the transactions as performed by the manufacturer wallet150on the warranty data of the IoT device110, for audit or for any warranty claims.

For the enhanced warranty system100, the user101, the manufacturer109, and the IoT device110can request transactions in the blockchain network120. The blockchain network120is a Peer to Peer (P2P) network in which participants of the blockchain network120that process requested transactions and store records of the requested transactions are referred to as respective blockchain nodes. The records of transactions requested by the user101, the manufacturer109, and/or the IoT device110can be stored in many blockchain nodes in the blockchain network120, such that the records of transactions as performed by the request from the user101, the manufacturer109, or the IoT device110can be transparently shared in a tamperproof manner. The blockchain network120for the enhanced warranty system100records respective blockchains for the IoT device usage data and the IoT device warranty balance. Each transaction on either the IoT device usage data or the IoT device warranty balance is added to the respective blockchain once verified amongst parties to each transaction as a new block to the corresponding blockchain, which will not be altered and can be shared transparently, as the record is distributed amongst the blockchain nodes.

In this specification, the term “wallet” indicates a software client having a private key to access, to view, and to create transactions on a particular blockchain for which the wallet is designed. Accordingly, the blockchain network120includes an IoT device usage blockchain that corresponds to the IoT device usage wallet130, an IoT device usage warranty balance blockchain that corresponds to the IoT device warranty balance wallet140, and a manufacturer blockchain that corresponds to the manufacturer wallet150.

The IoT device110accesses and creates a record of IoT device usage on the IoT device usage blockchain via the IoT device usage wallet130. The IoT device warranty balance wallet140accesses the IoT device usage blockchain as updated by the IoT device usage wallet130and creates a record of IoT device warranty balance onto the IoT device usage warranty balance blockchain. Similarly, the manufacturer wallet150accesses the IoT device usage blockchain as updated by the IoT device usage wallet130and creates a record of IoT device warranty balance onto the manufacturer blockchain. Accordingly, the IoT device warranty balance values accessed by the IoT device warranty balance wallet140and the manufacturer wallet150would be synchronized. Each blockchain can be copied to a plurality of participants, which is referred to as a blockchain node, of the blockchain network120. The manufacturer109and the user101can access blockchain nodes storing the IoT device usage data and/or the IoT device warranty balance in the blockchain network120, such that the IoT device usage data and/or the IoT device warranty balance would be shared in a manner transparent and unalterable for the purpose of the enhanced warranty system100.

In this specification, functionalities of the blockchain network120are described in terms of wallet transactions, which are recorded in respectively corresponding blockchains to be shared amongst certain blockchain nodes of the blockchain network120, in order to achieve a transparent, verifiable, and unalterable record of the wallet transactions. Further details on the blockchain nodes and blockchain wallets are not within the scope of the present specification.

By use of the IoT device usage wallet130, the IoT device warranty balance wallet140, and the manufacturer wallet150in the blockchain network120, the user101and the vendor109can transparently share a record of usage on the IoT device110.

As noted, the IoT device warranty balance wallet140corresponds to the IoT device usage wallet130and the IoT device warranty balance is adjusted according to the IoT device usage as reported by the IoT device110. The manufacturer109can quantify an effect of a certain usage on the IoT device110in terms of a certain depreciation on the lifespan of the IoT device and reduce the warranty hours accordingly.

In certain embodiments of the present invention, the IoT device usage wallet130and the IoT device warranty balance wallet140can be integrated in the IoT device110, and/or the IoT device110can also be one of a blockchain node that holds copies of the IoT device usage data and the IoT device warranty balance data represented in respective blockchains. Similarly, in certain embodiments of the present invention, the manufacturer109, or a blockchain node representing the manufacturer109in the blockchain network120, which is a combination of a process to perform transactions and a record of the transactions referred to as a blockchain, can include the manufacturer wallet150.

Detailed operations of the IoT device110, along with the IoT device usage wallet130and the IoT device warranty balance wallet140, are described inFIG.2and corresponding description.

Detailed interactions amongst the IoT device110, the IoT device usage wallet130, the IoT device warranty balance wallet140, the manufacturer wallet150, and the UIA160are described inFIG.3and corresponding description.

FIG.2depicts a flowchart of operations performed by the IoT device110in the enhanced warranty system100ofFIG.1, in accordance with one or more embodiments set forth herein.

InFIG.2, the operations of the IoT device110for the purpose of the enhanced warranty system100throughout its lifetime are described. The operations of the IoT device110include the operations by the IoT device110itself communicating with the blockchain network120, as well as transactions on corresponding blockchain nodes that are performed by the IoT device usage wallet130and the IoT device warranty balance wallet140.

In block210, the IoT device110automatically registers the IoT device110with the manufacturer wallet150in the blockchain network120, upon being used for the first time. When the user101first starts using the IoT device110in an environment where access to Internet is available for the IoT device110, the IoT device110automatically reports, via the Internet, all device metadata of the IoT device110that can identify the IoT device110within the blockchain network120such that the manufacturer109would initiate and/or activate the IoT device usage wallet130and the IoT device warranty balance wallet140by transferring respective credits from the manufacturer wallet150to the IoT device usage wallet130and the IoT device warranty balance wallet140. Then, in an embodiment, the IoT device110proceeds with block220.

In certain embodiments of the present invention, the IoT device usage wallet130and the IoT device warranty balance wallet140are initialized with a certain value of usage reporting credits and an instance of initial warranty hours, respectively, as the manufacturer wallet150transfers the initial values of the usage reporting credits and warranty hours to the respective wallets130,140, once the IoT device110registers itself upon the first use. In other embodiments of the present invention, the IoT device usage wallet130and the IoT device warranty balance wallet140are previously initialized with a certain value of usage reporting credits and an instance of initial warranty hours, respectively, and when the IoT device110registers itself upon the first use, the manufacturer wallet150can activate the respective wallets130,140to keep track of the usage and warranty balance from then on.

Blocks220through260describes operations of the IoT device110that are relevant to the enhanced warranty system100while the warranty on the IoT device110is effective. When the warranty on the IoT device110expires, the IoT device110operations regarding the enhanced warranty system100terminates.

In block220, the IoT device110reports, in real time, instances of encoded IoT device usage data to the IoT device usage wallet130in the blockchain network120when the IoT device110runs. The IoT device110uploads the encoded IoT device usage data to the blockchain network120as the IoT device110runs. Accordingly, the user101can also view the usage data of the IoT device110in real time on the UIA160, or in certain frequencies configured for synchronization with the UIA160viewing. The IoT device usage wallet130records the IoT device usage data to the IoT device usage blockchain in the blockchain network120. If the IoT device110is kept running for a certain period of time, the IoT device110can report at an interval even within a same run. The IoT device110can report a certain triggering event configured for reporting such as a certain high temperature, a certain extended run cycle, a submersion under water, a drop from a certain height, etc. The IoT device110reports in an encoded data format specific for the IoT device110. Then, in an embodiment, the IoT device110proceeds with block230.

In block230, the IoT device110decreases credits in the respective IoT device wallets130,140, according to the IoT usage data report from block220. As noted in block220, the IoT device usage wallet130recorded the IoT device usage data to the IoT device usage blockchain in the blockchain network120. The IoT device usage wallet130translates the intensity and the amount of time corresponding to the IoT device usage data from block220to an instance of warranty hours, and requests the IoT device warranty balance wallet140for a transaction to decrease the instance of warranty hours from a current value stored in the IoT device warranty balance blockchain for the IoT device110. The IoT device warranty balance wallet140can also request the manufacturer wallet150for the same transaction to decrease the instance of warranty hours from a current value stored in the manufacturer blockchain as a warranty balance for the IoT device110. Then, in an embodiment, the IoT device110proceeds with block240.

In block240, the IoT device determines whether or not the warranty balance for the IoT device110resulting from block230is large enough not to alert the user101on the expiring warranty. If the IoT device determines that the warranty balance for the IoT device110resulting from block230is greater than or equal to the warranty balance threshold to alert the user101, then the IoT device110loops back to block220for a next report of the IoT usage data. If the IoT device determines that the warranty balance for the IoT device110resulting from block230is less than the warranty balance threshold to alert the user101, then, in an embodiment, the IoT device110proceeds with block250.

In block250, the IoT device notifies the user101that the warranty balance for the IoT device110is expiring and recommends the user101to extend the warranty for the IoT device110. In certain embodiments of the present invention, the IoT device warranty balance wallet140can send a push notification of the expiring warranty to the UIA160running on the mobile phone of the user101. The UIA160facilitates blockchain transactions for the user101to transfer a certain number of additional warranty hours from the manufacturer wallet150to the IoT device warranty balance wallet140and to transfer a certain amount of additional reporting credits from the manufacturer wallet150to the IoT device usage wallet130, by use of various conventional payment methods available on-line. Then, in an embodiment, the IoT device110proceeds with block260.

In block260, the IoT device110updates the IoT device usage reporting credits and the IoT device warranty balance from respective blockchains by use of the IoT device usage wallet130and the IoT device warranty balance wallet140, respectively, if the user101had extended the warranty with the manufacturer109via the UIA160. If the user101had not taken any action but the IoT device warranty balance had not expired yet, then, the IoT device110loops back to block220for a next report on the IoT device usage. If the user101had not taken any action and the IoT device warranty balance had expired, then, the IoT device110terminates processing for the purpose of the enhanced warranty system100.

In certain embodiments of the present invention, the user101can renew the warranty on the IoT device110by selecting an option from a certain group of warranties offered by the manufacturer109from the UIA160, within a certain time period as set by the manufacturer109after the expiration. In the same embodiment of the present invention, the manufacturer wallet150can facilitate to perform a transfer of certain number of reporting credits and a specified amount of the warranty balance for the IoT device110to the IoT device usage wallet130and the IoT device warranty balance wallet140, respectively. Further in the same embodiment of the present invention, for the warranty gap between the period of the date of the expiration and the date of the renewal, a certain amount of warranty balance can be deducted, proportional to the number of days corresponding to the warranty gap. In the same embodiment of the present invention, the amount of deduction for the warranty gap can be estimated based on maximum intensity of usage, average usage by the user101during the period while the warranty was effective, or any other method specified by the manufacturer109, depending on the value and type of usage relevant to the IoT device110. Also, any damages or operating conditions of the IoT device110should be inspected and reported for a renewal.

In certain embodiments of the present invention, the user101can report a warranty claim on malfunctions of the IoT device110via the UIA160for a repair or an exchange. Upon receiving the warranty claim, the manufacturer109reviews the IoT device usage data and the IoT device warranty balance and processes the warrant claim accordingly. As the blockchain records of IoT device usage and the IoT device warranty balance are transparent, verifiable, and unalterable as shared via the blockchain network120, both the user101and the manufacturer109can trust the records and accordingly the warranty claim could be processed based on the blockchain records of IoT device usage and the IoT device warranty balance. The outcome of the warranty claim can be more satisfactory than in conventional warranty systems where there is no record on how the IoT device110has been used up to the time of warranty claim as each use on the IoT device110has been recorded, the IoT device110had been automatically registered, and the question on whether or not the IoT device110is covered by a warranty is clearly answered by the value of the warranty balance on the IoT device110.

FIG.3depicts exemplary transactions performed amongst blockchain wallets in the components of the enhanced warranty system100ofFIG.1, in accordance with one or more embodiments set forth herein.

The components of the enhanced warranty system100fromFIG.1are shown inFIG.3, including the IoT device110, the IoT device usage wallet130, the IoT device warranty balance wallet140, the manufacturer wallet150, and the user interface app160.

InFIG.2above, the IoT device110, the IoT device usage wallet130, and the IoT device warranty balance wallet140had been collectively referred to as the IoT device110. InFIG.3, the operations of the IoT device110described inFIG.2are further detailed as distinguished between the blockchain transactions and other types of operations. InFIG.3, blockchain transactions are marked as solid arrows from a wallet which initiates a transaction to change a credit to another wallet which reflects the requested transaction in credits.

When the IoT device110registers itself by sending device metadata that identifies the IoT device110upon being turned on for the first time, the manufacturer wallet150performs transaction301-302to transfer an initial warranty hours corresponding to the IoT device110from the manufacturer wallet150to the IoT device warranty balance wallet140. The manufacturer wallet150also performs transaction303-304to transfer an initial usage reporting credits for the IoT device110from the manufacturer wallet150to the IoT device usage wallet130.

For example, if the IoT device110is a blender coded “1blender395” as identified by the manufacturer109named A which made the blender, when the IoT device110“1blender395” is turned on for the first time in Internet-accessible environment, the IoT device110“1blender395” sends in a time-attribute stamp that is preconfigured for reporting usage on the IoT device110“1blender395”. For example, the time-attribute stamp for the IoT device110“1blender395” and for the same models can be “DEVSN_YYMMDDMMSSAABBCCDDEEFF”, in which DEVSN is a device serial number to identify each blender made by the manufacturer109A, YYMMDD indicates the date by year in two digits (YY), month in two digits (MM), and day in two digits (DD), MMSS indicates the duration of a run cycle that is being reported by minutes in two digits (MM) and seconds in two digits (SS), AABBCCCDDEEFF indicates specifics of the run cycle and working environment, as in AA for a two-digit power level in percentage, BB is for a two-digit humidity, CCC is for a three-digit temperature representing degrees in Fahrenheit (° F.), and so on. Respective parameters in the time-attribute stamp can be instantiated by the readings from respective detectors embedded in the IoT device110“1blender395” or parts of the IoT device110“1blender395” that generate data such as power level adjustment units.

In the same example, the manufacture wallet150can activate the IoT device usage data wallet130“1blender395a” by the transaction303-304, and can activate the IoT device warranty balance wallet140“1blender395b” by the transaction301-302.

When the user101runs the IoT device110, the IoT device110reports the usage data to the blockchain network120. The IoT device usage data wallet130receives the usage data and calculates certain warranty hours corresponding to the usage data, then performs transaction305-306to reduce the certain warranty hours corresponding to the usage data from the IoT device warranty balance wallet140. The IoT device usage data wallet130performs transaction307-308to transfer the reporting credit corresponding to the usage report from the IoT device usage data wallet130to the manufacturer wallet150. The manufacturer wallet308can trace the usage data upon which the reporting credit has been used in the blockchain network120when the usage data is needed for verification. As the reporting of the IoT device usage can be periodical or upon being triggered by a certain working conditions that affect the warranty on the IoT device110, the manufacturer109can set the reporting credits to a certain number such that exhausting the reporting credit can be translated as the IoT device110had been over with an expected life span or an expected number of run cycles with no defect.

Transaction309-310indicates that the UIA160receives a notification by the IoT device warranty balance wallet140as the warranty balance for the IoT device110is less than a threshold set to alert the user101. Alternatively, the IoT device usage wallet130can also send a notification to the UIA160based on that a value of the reporting credits is less than another threshold set to alert the user101. In certain embodiments of the present invention, because the UIA160can access and view respective data in the IoT device usage wallet130and the IoT device warranty balance wallet140, the UIA160can generate an alert such as a push notification on the mobile phone for the user101upon checking the values of respective data in the IoT device usage wallet130and the IoT device warranty balance wallet140.

Transaction311-312indicates that the user101extended the warranty hours for the IoT device110via the UIA160or any other online transaction method to have the amount of extended warranty hours from the manufacturer wallet150. Transaction312-301indicates that the manufacturer wallet150loads the amount of extended warranty hours as extended by the user to the IoT device warranty balance wallet140. Another transaction303-304would follow the re-load of the IoT device warranty balance wallet140with the extended warranty hours.

FIG.4depicts an exemplary display of the UIA160on a mobile device400, in accordance with one or more embodiments set forth herein

When the user101uses the IoT device110“1blender395” for the first time, the IoT device110“1blender395” reports the usage with a time-attribute stamp “1blender39520012305005025080”, indicating that the IoT device110“1blender395” ran on Jan. 23, 2020 (200123), for five minutes (0500), at a fifty percent power level (50), in a twenty-five percent humidity (25) and eighty-degree temperature in Fahrenheit (° F.) (080).

In the example ofFIG.3, when the blockchain network120receives the usage report of the time-attribute stamp instantiated as above from the IoT device110“1blender395”, the manufacture wallet150activates the IoT device usage data wallet130“1blender395a” by the transaction303-304, and activates the IoT device warranty balance wallet140“1blender395b” by the transaction301-302. “1blender395a” and “1blender395b” are public information that can be used to access the respective wallets, which often referred to as wallet addresses. In certain embodiments of the present invention, the manufacturer wallet150activates the IoT device usage data wallet130“1blender395a” by loading an initial value of the usage reporting credits of one hundred (100), which is configured to decrease 0.001 for every reporting of a run cycle. In the same embodiments of the present invention, the manufacturer wallet150activates the IoT device warranty balance wallet140“1blender395b” by loading an initial value of the warranty balance of five thousand (5000) for the IoT device110“1blender395”. The manufacturer109sets respective values of the usage reporting credits and the warranty balance for the IoT devices110according to the characteristics of each IoT device110in types and pattern of the use for the IoT devices110. For example, a laptop computer and a blender would be set with respective values of the usage reporting credits and the warranty balance, based on the characteristics of each IoT device and use pattern typical for each IoT device.

For example, a battery would be covered by a warranty to maintain eighty percent (80%) of capacity for five hundred (500) cycles of charge and discharge at a range of ambient temperature below one hundred degrees in Fahrenheit (100° F.), but two hundred and fifty (250) cycles of charge and discharge at a range of ambient temperature equal or higher than one hundred degrees in Fahrenheit (100° F.). Accordingly, in certain embodiments of the present invention, if each cycle of charge and discharge cycle is configured to subtract one (1) unit from the warranty balance for the battery, then another cycle of charge and discharge cycle would be configured to subtract two (2) units from the warranty balance for the same battery. The warranty balance becomes zero (0) the warranty for the battery expires, and the user101can view the warranty balance and purchase an extended warranty.

When balance reaches 0, warranty coverage expires. The manufacturer and user of product can transparently check how much balance is left in the warranty wallet.

For another example, a warranty on a video camera will be presented with a recommended operating conditions such as “warranty based operating temperature range −20 to 110 degrees Fahrenheit, humidity range 20% to 95%”, such that the manufacturer109can reduce or avoid any warranty coverage if the recommended operating conditions are not satisfied consistently, as functionalities of the video camera would deteriorate significantly under the circumstances even without any defect on the product.

An exemplary screen410titled “DASHBOARD” shows a dashboard of information relevant to the warranty of the IoT device110“1blender395” after the usage report of the time-attribute stamp instantiated as above. The icon on the left of “DASHBOARD” indicates a main menu of the UIA160.

Section411in the dashboard410stating “BALANCES; 1blender395b” indicates the IoT device warranty balance wallet140is named as “1blender395b” and the current warranty balance is shown by a pie chart415for the IoT device110“1blender395” as depicted in an image413.

Section417“Warranty hours; 5000.00” indicates that the initial warranty balance loaded to the IoT device warranty balance wallet140“1blender395b” is five thousand (5000.00).

Section419“1blender395a; Usage data” indicates that the IoT device usage data wallet130named “1blender395a” stores usage data for the IoT device110“1blender395”. The Usage data can be further navigable upon being selected by the user101, for example, as the user101tap the area on and around the tab “Usage data” on a touch screen of the mobile device400, or as the user101clicks the tab “Usage data” on a web browser.

Table420depicts items recorded in the usage data blockchain by the IoT device usage data wallet130“1blender395a”. The usage data blockchain recorded by the IoT device usage data wallet130“1blender395a” includes information reported in the usage report of the time-attribute stamp instantiated as above. The first use of running the blender IoT device “1blender395” for five minutes at fifty percent power level in eighty-degree temperature would account as depreciating 0.04 warranty hours in table420. The current warranty balance after the first use as recorded in the IoT device warranty balance wallet140“1blender395b” is also shown on the pie chart415.

Certain embodiments of the present invention provide the enhanced warranty system for IoT devices on a blockchain network in providing a usage-based warranty that improves conventional period-based warranty systems. Certain embodiments of the present invention implement two types of wallets for the IoT device in the blockchain network, an IoT device usage wallet to keep track of the usage records of the IoT device and an IoT device warranty balance wallet to keep track of a warranty balance. Certain embodiments of the present invention implement that the manufacturer of the IoT device loads a certain number of reporting credits to the IoT device usage wallet to be reduced per each usage report. Certain embodiments of the present invention implement that the manufacturer of the IoT device loads a certain amount of warranty balance the IoT device warranty balance wallet to be reduced by a specific warranty balance value corresponding to each usage report. Certain embodiments of the present invention implement that the IoT device would be automatically registered with the blockchain network to start the warranty coverage when the IoT device first communicates with the blockchain network by sending a usage report. Certain embodiments of the present invention translate each usage record as reported in real time by the IoT device to a corresponding amount of warranty balance and subtract the amount of warranty balance corresponding to the usage record automatically from the IoT device warranty balance as a series of blockchain wallet transactions. Certain embodiments of the present invention provide a user interface application that facilitates for the user to view up-to-date usage records on the IoT device and the current value of the warranty balance of the IoT device as being updated by the aforementioned blockchain transactions upon each use of the IoT device. Certain embodiments of the present invention facilitate, by use of the user interface application, the user to be notified with an upcoming expiration of the warranty as well as to extend the warranty.

Certain embodiments of the present invention provide a computer implemented method including, but not limited to: obtaining, by one or more processors, a usage report of an Internet of Things (IoT) device in a predefined format; recording, by the one or more processors, the usage report of the IoT device in a blockchain network; updating, by the one or more processors, a warranty balance for the IoT device by reducing an amount of the warranty balance corresponding to the usage report of the IoT device from a current value of the warranty balance, wherein the warranty balance for the IoT device is stored in the blockchain network; and resolving, by the one or more processors, a warranty claim on the IoT device based on respective blockchain records of the usage report and the warranty balance regarding the IoT device.

Certain embodiments of the present invention provide the computer implemented method as above further including, but not limited to: ascertaining that the usage report is sent from the IoT device for the first time; and registering the IoT device with the blockchain network by use of device metadata that uniquely identifies the IoT device.

Certain embodiments of the present invention provide the computer implemented method as above further including, but not limited to: receiving a request for access to usage data of the IoT device resulting from the recording for all run cycles on the IoT device from a user of the IoT device via a user interface application running on a mobile device; retrieving the usage data of the IoT device from the blockchain network; and displaying the usage data of the IoT device from the retrieving on the user interface application running on the mobile device.

Certain embodiments of the present invention provide the computer implemented method as above further including, but not limited to: receiving a request for access to the warranty balance of the IoT device resulting from the updating for all run cycles on the IoT device from a user of the IoT device via a user interface application running on a mobile device; retrieving the warranty balance of the IoT device from the blockchain network; and displaying the warranty balance of the IoT device from the retrieving on the user interface application running on the mobile device.

Certain embodiments of the present invention provide the computer implemented method as above, the recording including, but not limited to: performing, by an IoT device usage wallet for the IoT device, a blockchain transaction to record the usage report of the IoT device from the obtaining in the blockchain network; and performing another blockchain transaction to reduce a preconfigured amount of reporting credits corresponding to the usage report from the IoT device usage wallet, wherein the IoT device usage wallet is loaded with an initial amount of reporting credits by a manufacturer of the IoT device.

Certain embodiments of the present invention provide the computer implemented method as above, the updating including, but not limited to: ascertaining the amount of the warranty balance corresponding to the usage report of the IoT device from the obtaining; and performing, by an IoT device warranty balance wallet for the IoT device, a blockchain transaction to reduce, from the current value of the warranty balance, the amount of warranty balance corresponding to the usage report of the IoT device from the ascertaining, wherein the IoT device warranty balance wallet is loaded with an initial amount of warranty balance for the IoT device by a manufacturer of the IoT device.

Certain embodiments of the present invention provide the computer implemented method as above, in which the predefined format of the usage report of the IoT device includes a time stamp and one or more data values on preselected attributes of run cycles that affect functionalities of the IoT device for the purpose of warranty and environmental conditions that affect the warranty of the IoT device.

FIGS.5-7depict various aspects of computing, including a cloud computing system, in accordance with one or more aspects set forth herein.

Characteristics are as follows:

Service Models are as follows:

Deployment Models are as follows:

Computer system12may be described in the general context of computer system-executable instructions, such as program processes, being executed by a computer system. Generally, program processes may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system12may 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 processes may be located in both local and remote computer system storage media including memory storage devices.

As shown inFIG.5, computer system12in cloud computing node10is shown in the form of a general-purpose computing device. The components of computer system12may include, but are not limited to, one or more processors16, a system memory28, and a bus18that couples various system components including system memory28to processor16.

System memory28can include computer system readable media in the form of volatile memory, such as random access memory (RAM)30and/or cache memory32. Computer system12may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system34can 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 memory device (e.g., a “thumb drive”, “external hard drive”), 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 bus18by one or more data media interfaces. As will be further depicted and described below, memory28may include at least one program product having a set (e.g., at least one) of program processes that are configured to carry out the functions of embodiments of the invention.

One or more program40, having a set (at least one) of program processes42, may be stored in memory28by way of example, and not limitation, as well as an operating system, one or more application programs, other program processes, and program data. Each of the operating system, one or more application programs, other program processes, and program data or some combination thereof, may include an implementation of the user interface application160, the IoT device110, the IoT device usage wallet130, the IoT device warranty balance wallet140, and the manufacturer wallet150. Program processes42, as in the components of the enhanced warranty system100generally carry out the functions and/or methodologies of embodiments of the invention as described herein.

Computer system12may also communicate with one or more external devices14such as a keyboard, a pointing device, a display24, etc.; one or more devices that enable a user to interact with computer system12; and/or any devices (e.g., network card, modem, etc.) that enable computer system12to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces22. Still yet, computer system12can 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 network adapter20. As depicted, network adapter20communicates with the other components of computer system12via bus18.

In addition to or in place of having external devices14and the display24, which can be configured to provide user interface functionality, computing node10in one embodiment can include another display25connected to bus18. In one embodiment, the display25can be configured as a touch screen render and can be configured to provide user interface functionality, e.g. can facilitate virtual keyboard functionality and input of total data. Computer system12in one embodiment can also include one or more sensor device27connected to bus18. One or more sensor device27can alternatively or in addition be connected through I/O interface(s)22. The one or more sensor device27can include a Global Positioning Sensor (GPS) device in one embodiment and can be configured to provide a location of computing node10. In one embodiment, the one or more sensor device27can alternatively or in addition include, e.g., one or more of a camera, a gyroscope, a temperature sensor, a humidity sensor, a pulse sensor, a blood pressure (BP) sensor or an audio input device.

It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system12. Examples, include, but are not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

Workloads layer90provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation91; software development and lifecycle management92; virtual classroom education delivery93; data analytics processing94; transaction processing95; and processing components for the enhanced warranty system96, as described herein.