IP Library › Granted Patent US 12,190,389
Granted Patent B2
US 12,190,389 · App. 18/202,365 · Granted Jan 7, 2025

Distributed ledger system for managing smart data

Inventors: Ronny S. Bryant (Bloomington, IL); Stacie A. McCullough (Bloomington, IL); Mitchell J. Hill (Bloomington, IL); Jacob J. Alt (Downs, IL); Jaime Skaggs (Chenoa, IL); Shawn M. Call (Bloomington, IL); Eric Bellas (Bloomington, IL); Vicki King (Bloomington, IL); Melinda Teresa Magerkurth (Utica, IL)
Assignee: STATE FARM MUTUAL AUTOMOBILE INSURANCE COMPANY
G06Q40/08B60W50/00G06F16/182G06F16/27G06Q10/10G06Q20/389G06Q30/0283G06Q30/0623G06Q50/163G07C5/008G07C5/0808G16H10/60H04L9/0643H04L9/32H04L12/2803H04L67/1061H04L67/12H04W4/40B60W2756/10G06F16/903H04L9/50H04L2012/2847
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,190,389
App. No.
18/202,365
Filed
May 26, 2023
Granted
Jan 7, 2025
Kind
B2
Art Unit
3694
USPC
705/4
Abstract

Systems and methods are disclosed with respect to using a distributed ledger, such as a blockchain, for tracking changes for a user. Example methods may include implementing one or more servers, each of the one or more servers maintaining a copy of a distributed ledger; detecting a change in a policy or claim status for a user; responding to the detection of the change, including: (i) generating, via a server of the one or more servers, a transaction record for the distributed ledger including data corresponding to the change; (ii) generating a hash value representative of at least the transaction record using at least a generated nonce value; and (iii) storing the transaction record and the hash value to each copy of the distributed ledger at the one or more servers; and performing a function based upon the transaction record stored to the distributed ledger.

Claims (44)

1. A computer-implemented method for tracking changes for a user, the method comprising:

implementing, by one or more processors, one or more servers, each of the one or more servers maintaining a copy of a distributed ledger;

detecting, by the one or more processors, a change in an insurance claim status for a user;

responding, by the one or more processors, to the detection of the change, including:

(i) generating, via a server of the one or more servers, a transaction record for the distributed ledger including data corresponding to the change;

(ii) generating a hash value representative of at least the transaction record using at least a generated nonce value as an input to a cryptographic puzzle; and

(iii) storing, responsive to solving the cryptographic puzzle, the transaction record and the hash value to each copy of the distributed ledger at the one or more servers; and

performing, by the one or more processors, a function based upon the transaction record stored to the distributed ledger.

2. The computer-implemented method of claim 1 , wherein the change represents any one or more of: a filing of the insurance claim; an assessment of damage; an estimate of a repair or replacement cost; or a payment to settle the insurance claim.

3. The computer-implemented method of claim 1 , wherein responding to the detection further includes:

performing, via the one or more servers, a consensus analysis via a consensus mechanism to form a consensus regarding a validity of the transaction record,

wherein storing the transaction record includes storing the transaction record in response to detecting that the consensus has been formed.

4. The computer-implemented method of claim 3 , wherein the consensus mechanism is any one or more of: a proof of activity mechanism, a proof of burn mechanism, a proof of capacity mechanism, or a proof of elapsed time mechanism.

5. The computer-implemented method of claim 3 , wherein responding to the detection further includes:

generating a notification that the transaction record is invalid in response to detecting that the consensus has not been formed.

6. The computer-implemented method of claim 1 , wherein the change pertains to at least one of: a vehicle, a property, a financial transaction, or the user.

7. The computer-implemented method of claim 1 , wherein storing the transaction record at the distributed ledger comprises: storing the transaction record to a block.

8. The computer-implemented method of claim 7 , wherein the hash value is a hash value for the block, and further wherein generating the hash value for the block includes generating a transaction hash value for the transaction record and utilizing the transaction hash value for the transaction record to generate the hash value for the block.

9. A computing system for tracking changes for a user, the system comprising:

one or more servers, each including one or more processors and maintaining a copy of a distributed ledger for tracking changes in policy or claim statuses for a user;

wherein a server of the one or more servers is configured to respond to a detection of a change in an insurance claim status for the user by generating a transaction record for the distributed ledger including data corresponding to the change; and

wherein the one or more servers are configured to: (i) generate a hash value representative of at least the transaction record using at least a generated nonce value, as an input to a cryptographic puzzle; (ii) store, responsive to solving the cryptographic puzzle, the transaction record generated by the server and the hash value to each copy of the distributed ledger at the one or more servers; and (iii) perform a function based upon the transaction record stored to the distributed ledger.

10. The computing system of claim 9 , wherein the change represents any one or more of: a filing of the insurance claim; an assessment of damage; an estimate of a repair or replacement cost; or a payment to settle the insurance claim.

11. The computing system of claim 9 , wherein the server is configured to broadcast the transaction record to one or more other servers;

wherein the one or more servers are configured to: perform a consensus analysis via a consensus mechanism to form a consensus regarding a validity of the transaction record; and store the transaction record in response to detecting that the consensus has been formed.

12. The computing system of claim 11 , wherein the consensus mechanism is any one or more of: a proof of activity mechanism, a proof of burn mechanism, a proof of capacity mechanism, or a proof of elapsed time mechanism.

13. The computing system of claim 11 , wherein responding to the detection further includes:

generating a notification that the transaction record is invalid in response to detecting that the consensus has not been formed.

14. The computing system of claim 9 , wherein the change pertains to at least one of: a vehicle, a property, a financial transaction, or the user.

15. The computing system of claim 9 , wherein storing the transaction record at the distributed ledger comprises: storing the transaction record to a block.

16. The computing system of claim 15 , wherein the hash value is a hash value for the block, and further wherein generating the hash value for the block includes generating a transaction hash value for the transaction record and utilizing the transaction hash value for the transaction record to generate the hash value for the block.

17. A non-transitory computer readable medium storing instructions for tracking changes for a user that, when implemented, cause a computing system to:

implement one or more servers, each of the one or more servers maintaining a copy of a distributed ledger;

detect a change in an insurance claim status for a user;

respond to the detection of the change by:

(i) generating, via a server of the one or more servers, a transaction record for the distributed ledger including data corresponding to the change;

(ii) generating a hash value representative of at least the transaction record using at least a generated nonce value as an input to a cryptographic puzzle; and

(iii) storing, responsive to solving the cryptographic puzzle, the transaction record and the hash value to each copy of the distributed ledger at the one or more servers; and

perform a function based upon the transaction record stored to the distributed ledger.

18. The non-transitory computer readable medium of claim 17 , wherein the change represents any one or more of: a filing of the insurance claim; an assessment of damage; an estimate of a repair or replacement cost; or a payment to settle the insurance claim.

19. The non-transitory computer readable medium of claim 17 , wherein responding to the detection further includes:

performing, via the one or more servers, a consensus analysis via a consensus mechanism to form a consensus regarding a validity of the transaction record,

wherein storing the transaction record includes storing the transaction record in response to detecting that the consensus has been formed.

20. The non-transitory computer readable medium of claim 19 , wherein the consensus mechanism is any one or more of: a proof of burn mechanism, a proof of capacity mechanism, or a proof of elapsed time mechanism.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 9, 2023
From: BRYANT, RONNY S.; MCCULLOUGH, STACIE A.; HILL, MITCHELL J.; ALT, JACOB J.; SKAGGS, JAIME; CALL, SHAWN M.; BELLAS, ERIC; KING, VICKI; MAGERKURTH, MELINDA TERESA
To: STATE FARM MUTUAL AUTOMOBILE INSURANCE COMPANY
Reel/Frame 063912/0765 →
Continuity (15)
Continuation 17177825 · Feb 17, 2021
Continuation 15870350 · Jan 12, 2018
Provisional Application 62548692 · Aug 22, 2017
Provisional Application 62548731 · Aug 22, 2017
Provisional Application 62548679 · Aug 22, 2017
Provisional Application 62548741 · Aug 22, 2017
Provisional Application 62548700 · Aug 22, 2017
Provisional Application 62548682 · Aug 22, 2017
Provisional Application 62548748 · Aug 22, 2017
Provisional Application 62548668 · Aug 22, 2017
Provisional Application 62545262 · Aug 14, 2017
Provisional Application 62508133 · May 18, 2017
Provisional Application 62500049 · May 2, 2017
Provisional Application 62500326 · May 2, 2017
Related Publication 20230298108A1 · Sep 21, 2023
References Cited (343)
US 5499182A · Ousborne · 1996 [cited by applicant]
US 8085166B2 · Tamir et al. · 2011 [cited by applicant]
US 8106769B1 · Maroney et al. · 2012 [cited by applicant]
US 8374957B1 · Garcia et al. · 2013 [cited by applicant]
US 8756085B1 · Plummer et al. · 2014 [cited by applicant]
US 9141582B1 · Brinkmann et al. · 2015 [cited by applicant]
US 9298806B1 · Vessenes · 2016 [cited by examiner]
US 9311271B2 · Wright · 2016 [cited by applicant]
US 9633487B2 · Wright · 2017 [cited by applicant]
US 9646029B1 · Baird, III · 2017 [cited by applicant]
US 9811863B1 · Marinescu et al. · 2017 [cited by applicant]
US 9830748B2 · Rosenbaum · 2017 [cited by applicant]
US 9855785B1 · Nagelberg et al. · 2018 [cited by applicant]
US 9990782B2 · Rosenbaum · 2018 [cited by applicant]
US 9998286B1 · Ramathal et al. · 2018 [cited by applicant]
US 10192369B2 · Wright · 2019 [cited by applicant]
US 10198879B2 · Wright · 2019 [cited by applicant]
US 10269009B1 · Winklevoss et al. · 2019 [cited by applicant]
US 10269190B2 · Rosenbaum · 2019 [cited by applicant]
US 10340038B2 · Witchey · 2019 [cited by applicant]
US 10341309B1 · Ramirez et al. · 2019 [cited by applicant]
US 10366204B2 · Tanner, Jr. et al. · 2019 [cited by applicant]
US 10430883B1 · Bischoff et al. · 2019 [cited by applicant]
US 10430889B1 · Ismaili et al. · 2019 [cited by applicant]
US 10454878B2 · Khan et al. · 2019 [cited by applicant]
US 10467824B2 · Rosenbaum · 2019 [cited by applicant]
US 10510120B1 · Roll · 2019 [cited by applicant]
US 10521780B1 · Hopkins, III et al. · 2019 [cited by applicant]
US 10554649B1 · Fields et al. · 2020 [cited by applicant]
US 10586062B1 · Rangan et al. · 2020 [cited by applicant]
US 10606669B2 · Jacobs et al. · 2020 [cited by applicant]
US 10679221B1 · Rutley et al. · 2020 [cited by applicant]
US 10685009B1 · Rutley et al. · 2020 [cited by applicant]
US 10713727B1 · Floyd et al. · 2020 [cited by applicant]
US 10726493B1 · Kyne et al. · 2020 [cited by applicant]
US 10733616B1 · Rutley et al. · 2020 [cited by applicant]
US 10796371B1 · Floyd et al. · 2020 [cited by applicant]
US 10796393B2 · Messerges et al. · 2020 [cited by applicant]
US 10805085B1 · Liang · 2020 [cited by applicant]
US 10832337B1 · Floyd et al. · 2020 [cited by applicant]
US 10832338B1 · Floyd et al. · 2020 [cited by applicant]
US 10833843B1 · Vijayvergia et al. · 2020 [cited by applicant]
US 10872381B1 · Leise et al. · 2020 [cited by applicant]
US 10878512B1 · Al-Zoubi et al. · 2020 [cited by applicant]
US 10891694B1 · Leise et al. · 2021 [cited by applicant]
US 10929931B1 · Bryant et al. · 2021 [cited by applicant]
US 10971251B1 · Giobbi et al. · 2021 [cited by applicant]
US 11037377B1 · Bryant et al. · 2021 [cited by applicant]
US 11217332B1 · Bryant et al. · 2022 [cited by applicant]
US 11227452B2 · Rosenbaum · 2022 [cited by applicant]
US 11407410B2 · Rosenbaum · 2022 [cited by applicant]
US 11524707B2 · Rosenbaum · 2022 [cited by applicant]
US 11594083B1 · Rosenbaum · 2023 [cited by applicant]
US 11756128B2 · Bryant et al. · 2023 [cited by applicant]
US 20020022976A1 · Hartigan · 2002 [cited by applicant]
US 20050276401A1 · Madill et al. · 2005 [cited by applicant]
US 20060212195A1 · Veith et al. · 2006 [cited by applicant]
US 20060253351A1 · Keaney · 2006 [cited by applicant]
US 20060282342A1 · Chapman · 2006 [cited by applicant]
US 20070185743A1 · Jinks · 2007 [cited by applicant]
US 20080255722A1 · McClellan et al. · 2008 [cited by applicant]
US 20090024419A1 · McClellan et al. · 2009 [cited by applicant]
US 20090327006A1 · Hansan et al. · 2009 [cited by applicant]
US 20100223078A1 · Willis et al. · 2010 [cited by applicant]
US 20110090075A1 · Armitage et al. · 2011 [cited by applicant]
US 20110106370A1 · Duddle et al. · 2011 [cited by applicant]
US 20110161116A1 · Peak et al. · 2011 [cited by applicant]
US 20110213628A1 · Peak et al. · 2011 [cited by applicant]
US 20110320492A1 · Inghelbrecht · 2011 [cited by applicant]
US 20120029945A1 · Altieri et al. · 2012 [cited by applicant]
US 20120053965A1 · Hellman et al. · 2012 [cited by applicant]
US 20120066007A1 · Ferrick et al. · 2012 [cited by applicant]
US 20120259722A1 · Mikurak · 2012 [cited by examiner]
US 20140063232A1 · Fairfield et al. · 2014 [cited by applicant]
US 20140129261A1 · Bothwell et al. · 2014 [cited by applicant]
US 20140278582A1 · Shambach · 2014 [cited by examiner]
US 20140278585A1 · Zerbib · 2014 [cited by applicant]
US 20140368601A1 · deCharms · 2014 [cited by applicant]
US 20150006205A1 · Chase et al. · 2015 [cited by applicant]
US 20150170112A1 · DeCastro · 2015 [cited by applicant]
US 20150310476A1 · Gadwa · 2015 [cited by applicant]
US 20150332283A1 · Witchey · 2015 [cited by applicant]
US 20150356686A1 · Cook et al. · 2015 [cited by applicant]
US 20160027121A1 · Lucia et al. · 2016 [cited by applicant]
US 20160048923A1 · Maher et al. · 2016 [cited by applicant]
US 20160171619A1 · Besman et al. · 2016 [cited by applicant]
US 20160217532A1 · Slavin · 2016 [cited by applicant]
US 20160224949A1 · Thomas et al. · 2016 [cited by applicant]
US 20160260169A1 · Arnold et al. · 2016 [cited by applicant]
US 20160358135A1 · Liao et al. · 2016 [cited by applicant]
US 20160378943A1 · Vallée · 2016 [cited by applicant]
US 20170034197A1 · Daniel et al. · 2017 [cited by applicant]
US 20170046526A1 · Chan et al. · 2017 [cited by applicant]
US 20170046651A1 · Lin et al. · 2017 [cited by applicant]
US 20170046792A1 · Haldenby et al. · 2017 [cited by applicant]
US 20170053461A1 · Pal et al. · 2017 [cited by applicant]
US 20170069034A1 · Luciani · 2017 [cited by applicant]
US 20170075941A1 · Finlow-Bates · 2017 [cited by applicant]
US 20170091397A1 · Shah · 2017 [cited by applicant]
US 20170124556A1 · Seger, II · 2017 [cited by applicant]
US 20170147957A1 · Deane · 2017 [cited by examiner]
US 20170161439A1 · Raduchel et al. · 2017 [cited by applicant]
US 20170177898A1 · Dillenberger · 2017 [cited by applicant]
US 20170220998A1 · Horn et al. · 2017 [cited by applicant]
US 20170300627A1 · Giordano et al. · 2017 [cited by applicant]
US 20170300912A1 · Narasimhan · 2017 [cited by examiner]
US 20170372431A1 · Perl et al. · 2017 [cited by applicant]
US 20180018723A1 · Nagla et al. · 2018 [cited by applicant]
US 20180039667A1 · Pierce et al. · 2018 [cited by applicant]
US 20180040007A1 · Lane et al. · 2018 [cited by applicant]
US 20180046992A1 · Hanrahan et al. · 2018 [cited by applicant]
US 20180101848A1 · Castagna et al. · 2018 [cited by applicant]
US 20180157688A1 · Zessin · 2018 [cited by examiner]
US 20180165416A1 · Saxena et al. · 2018 [cited by applicant]
US 20180183600A1 · Davis · 2018 [cited by applicant]
US 20180205546A1 · Haque et al. · 2018 [cited by applicant]
US 20180218455A1 · Kolb et al. · 2018 [cited by applicant]
US 20180225660A1 · Chapman et al. · 2018 [cited by applicant]
US 20180247376A1 · Sharma et al. · 2018 [cited by applicant]
US 20180267539A1 · Shih · 2018 [cited by applicant]
US 20180276054A1 · Furuichi et al. · 2018 [cited by applicant]
US 20180308072A1 · Smith et al. · 2018 [cited by applicant]
US 20190019186A1 · Falah et al. · 2019 [cited by applicant]
US 20190057454A1 · Komenda et al. · 2019 [cited by applicant]
US 20190080392A1 · Youb et al. · 2019 [cited by applicant]
US 20190123889A1 · Schmidt-Karaca · 2019 [cited by applicant]
US 20190197620A1 · Jayaram et al. · 2019 [cited by applicant]
US 20190279227A1 · Chantz · 2019 [cited by applicant]
US 20190287140A1 · Arora et al. · 2019 [cited by applicant]
US 20190303931A1 · Valencia · 2019 [cited by applicant]
US 20190318816A1 · Witchey · 2019 [cited by applicant]
US 20190354966A1 · Himura et al. · 2019 [cited by applicant]
US 20190392437A1 · Castagna et al. · 2019 [cited by applicant]
US 20190392438A1 · Rice · 2019 [cited by applicant]
US 20200020037A1 · Idrobo · 2020 [cited by applicant]
US 20200058071A1 · Yang · 2020 [cited by applicant]
US 20200065763A1 · Rosinzonsky et al. · 2020 [cited by applicant]
US 20200177373A1 · Komandur et al. · 2020 [cited by applicant]
US 20200226677A1 · Dhawan et al. · 2020 [cited by applicant]
US 20200250753A1 · Blount · 2020 [cited by applicant]
US 20200272966A1 · Kirkegaard · 2020 [cited by applicant]
US 20200279328A1 · Zhiri et al. · 2020 [cited by applicant]
US 20200341971A1 · Krishnaswamy et al. · 2020 [cited by applicant]
US 20200394321A1 · Ramos et al. · 2020 [cited by applicant]
US 20200394322A1 · Ramos et al. · 2020 [cited by applicant]
US 20200409937A1 · Wang et al. · 2020 [cited by applicant]
US 20210065293A1 · Sigler et al. · 2021 [cited by applicant]
US 20210090037A1 · Dowding · 2021 [cited by applicant]
US 20210174442A1 · Trudeau et al. · 2021 [cited by applicant]
US 20210264362A1 · Bryant et al. · 2021 [cited by applicant]
US 20210264526A1 · Bryant et al. · 2021 [cited by applicant]
US 20210264527A1 · Bryant et al. · 2021 [cited by applicant]
US 20210279808A1 · Bryant et al. · 2021 [cited by applicant]
US 20210350469A1 · Bryant et al. · 2021 [cited by applicant]
US 20220092893A1 · Rosenbaum · 2022 [cited by applicant]
US 20220340148A1 · Rosenbaum · 2022 [cited by applicant]
US 20230060300A1 · Rosenbaum · 2023 [cited by applicant]
US 20240273638A1 · Bryant et al. · 2024 [cited by applicant]
EP 3239686A1 · 2017 [cited by applicant]
EP 3578433B1 · 2020 [cited by applicant]
EP 3730375B1 · 2021 [cited by applicant]
EP 3960576A1 · 2022 [cited by applicant]
EP 4190659A1 · 2023 [cited by applicant]
EP 4190660A1 · 2023 [cited by applicant]
WO WO2009044226A1 · 2009 [cited by applicant]
WO WO2017098519A1 · 2017 [cited by applicant]
WO WO2017136879A1 · 2017 [cited by applicant]
WO WO2017145009A1 · 2017 [cited by applicant]
WO WO2020169129A2 · 2020 [cited by applicant]
WO WO2021046494A1 · 2021 [cited by applicant]
Blockchain in the insurance sector. Retrieved from the internet at: <URL: https://www.pwc.co.uk (2016). [cited by applicant]
HashCoin Uses Emercoin Blockchain for Vehicle Registration and Tracking. Retrieved from the internet at: <URL: https://cointelegraph.com/news/hashcoin-uses-emercoin-blockchain-for-vehicle-registration-and-tracking (2018… [cited by applicant]
U.S. Appl. No. 14/871,401, filed Sep. 30, 2015, “System and Method for Obtaining and/or Maintaining Insurance Coverage”. [cited by applicant]
U.S. Appl. No. 15/457,705, filed Mar. 13, 2017, “System and Method for Obtaining and/or Maintaining Insurance Coverage”. [cited by applicant]
U.S. Appl. No. 15/600,968, filed May 22, 2017, “Systems and Methods for Blockchain Validation of Consumer Identity and Authority”. [cited by applicant]
U.S. Appl. No. 15/604,178, filed May 24, 2017, “Systems and Methods for Generating a Blockchain-based Consumer Profile”. [cited by applicant]
U.S. Appl. No. 15/624,278, filed Jun. 15, 2017, “Systems and Methods for Building and Utilizing an Autonomous Vehicle-Related Event Blockchain”. [cited by applicant]
U.S. Appl. No. 15/624,287, filed Jun. 15, 2017, “Systems and Methods For Maintaining a Distributed Ledger Pertaining to Smart Contracts”. [cited by applicant]
U.S. Appl. No. 15/624,292, filed Jun. 15, 2017, “Systems and Methods for Building, Utilizing, and/or Maintaining an Autonomous Vehicle-Related Event Distributed Ledger or Blockchain”. [cited by applicant]
U.S. Appl. No. 15/624,307, filed Jun. 15, 2017, “Systems and Methods for Maintaining a Distributed Ledger of Transactions Pertaining to an Autonomous Vehicle”. [cited by applicant]
U.S. Appl. No. 15/624,334, filed Jun. 15, 2017, “Systems and Methods for Maintaining a Distributed Ledger of Transactions Pertaining to One or More Smart Contracts”. [cited by applicant]
U.S. Appl. No. 15/624,341, filed Jun. 15, 2017, “Systems and Methods for Maintaining a Distributed Ledger Pertaining to Autonomous Vehicles”. [cited by applicant]
U.S. Appl. No. 15/704,339, filed Sep. 14, 2017, “Systems and Methods for Obtaining and/or Maintaining Usage-Based Insurance”. [cited by applicant]
U.S. Appl. No. 15/704,350, filed Sep. 14, 2017, “Systems and Methods for Obtaining and/or Maintaining Insurance for Autonomous Vehicles”. [cited by applicant]
U.S. Appl. No. 15/704,363, filed Sep. 14, 2017, “Systems and Methods for Determining and Providing Insurance to Affinitiy Groups”. [cited by applicant]
U.S. Appl. No. 15/704,632, filed Sep. 14, 2017, Systems and Methods for Obtaining and/or Securing Insurance for Affinity Groups. [cited by applicant]
U.S. Appl. No. 15/863,208, filed Jan. 5, 2018, “Providing Temporary Insurance Coverage Using Temorary Risk Data”. [cited by applicant]
U.S. Appl. No. 15/863,243, filed Jan. 5, 2018, “Providing Temporary Insurance Coverage Using Temorary Risk Data”. [cited by applicant]
U.S. Appl. No. 15/863,284, filed Jan. 5, 2018, “Providing Temporary Insurance Coverage Using Temorary Risk Data”. [cited by applicant]
U.S. Appl. No. 15/863,327, filed Jan. 5, 2018, Providing Temporary Insurance Coverage Using Temorary Risk Data. [cited by applicant]
U.S. Appl. No. 15/869,685, filed Jan. 12, 2018, “Risk Mitigation for Affinity Groupings”. [cited by applicant]
U.S. Appl. No. 15/869,752, filed Jan. 12, 2018, “Blockchain Systems and Methods for Providing Insurance Coverage to Affinity Groups”. [cited by applicant]
U.S. Appl. No. 15/870,271, filed Jan. 12, 2018, “Distributed Ledger System for Managing Loss Histories for Properties”. [cited by applicant]
U.S. Appl. No. 15/870,282, filed Jan. 12, 2018, “Distributed Ledger System for Managing Vehicle Sensor Data Utilized to Develop Collision Profiles”. [cited by applicant]
U.S. Appl. No. 15/870,292, filed Jan. 12, 2018, “Distributed Ledger System for Use With Vehicle Sensor Data and Usage Based Systems”. [cited by applicant]
U.S. Appl. No. 15/870,298, filed Jan. 12, 2018, “Distributed Ledger System for Managing Medical Records”. [cited by applicant]
U.S. Appl. No. 15/870,332, filed Jan. 12, 2018, “Distributed Ledger System for Insurance Record Management Systems”. [cited by applicant]
U.S. Appl. No. 15/870,343, filed Jan. 12, 2018, “Distributed Ledger System for Managing Smart Home Data”. [cited by applicant]
U.S. Appl. No. 15/870,350, filed Jan. 12, 2018, “Distributed Ledger System for Managing Smart Vehicle Data”. [cited by applicant]
U.S. Appl. No. 15/870,357, filed Jan. 12, 2018, “Distributed Ledger System for Claim Payouts”. [cited by applicant]
U.S. Appl. No. 15/870,364, filed Jan. 12, 2018, “Distributed Ledger System for Carrier Discovery”. [cited by applicant]
U.S. Appl. No. 15/870,371, filed Jan. 12, 2018, “Distributed Ledger System for Managing Loss Histories for Individuals”. [cited by applicant]
U.S. Appl. No. 15/877,982, filed Jan. 23, 2018, “Blockchain Banking Identity Authentication”. [cited by applicant]
U.S. Appl. No. 15/878,007, filed Jan. 23, 2018, “Blockchain Based Account Funding and Distribution”. [cited by applicant]
U.S. Appl. No. 15/878,028, filed Jan. 23, 2018, “Blockchain Based Card Activation”. [cited by applicant]
U.S. Appl. No. 15/878,046, filed Jan. 23, 2018, “Blockchain Based Passing Registry Actions”. [cited by applicant]
U.S. Appl. No. 15/878,067, filed Jan. 23, 2018, “Blockchain Based Asset Access”. [cited by applicant]
U.S. Appl. No. 15/878,082, filed Jan. 23, 2018, “Blockchain Based Lien Perfection”. [cited by applicant]
U.S. Appl. No. 15/878,106, filed Jan. 23, 2018, “Blockchain Based Settlement Processes”. [cited by applicant]
U.S. Appl. No. 15/878,125, filed Jan. 23, 2018, “Blockchain Based Contractor Ratings”. [cited by applicant]
U.S. Appl. No. 15/878,140, filed Jan. 23, 2018, “Blockchain Based Customer Records”. [cited by applicant]
U.S. Appl. No. 15/878,154, Jan. 23, 2018, “Blockchain Based Associate Information and Licensing”. [cited by applicant]
U.S. Appl. No. 62,508,133, filed May 18, 2017, “Distributed Ledger System for Managing Smart Home Data, Vehicle Data, Insurance Claim Payouts, and/or Insurance Carrier Discovery”. [cited by applicant]
U.S. Appl. No. 62/425,684, filed Nov. 23, 2016, “Systems and Methods for Maintaining a Distributed Ledger Governing Autonomous Vehicle Transactions”. [cited by applicant]
U.S. Appl. No. 62/428,223, filed Nov. 30, 2016, “Systems and Methods for Maintaining a Distributed Ledger Governing Autonomous Vehicle Transactions”. [cited by applicant]
U.S. Appl. No. 62/434,215, filed Dec. 14, 2016, “Systems and Methods for Maintaining a Distributed Ledger Governing Autonomous Vehicle Transactions”. [cited by applicant]
U.S. Appl. No. 62/447,240, filed Jan. 17, 2017, “Providing Temporary Insurance Coverage Using Temorary Risk Data”. [cited by applicant]
U.S. Appl. No. 62/449,405, filed Jan. 23, 2017, Providing Temporary Insurance Coverage Using Temorary Risk Data. [cited by applicant]
U.S. Appl. No. 62/450,349, filed Jan. 25, 2017, “Systems and Methods for Securely Incorporating Blockchain Technology”. [cited by applicant]
U.S. Appl. No. 62/450,441, filed Jan. 25, 2017, “Using Blockchain for Banking, Asset, and Identify Services”. [cited by applicant]
U.S. Appl. No. 62/457,430, filed Feb. 10, 2017, “Systems and Methods for Maintaining a Distributed Ledger Governing Autonomous Vehicle Transactions”. [cited by applicant]
U.S. Appl. No. 62/466,917, filed Mar. 3, 2017, “Blockchain Vin Registry”. [cited by applicant]
U.S. Appl. No. 62/468,092, filed Mar. 7, 2017, “Blockchain Vin Registry”. [cited by applicant]
U.S. Appl. No. 62/469,070, filed Mar. 9, 2017, “Using Blockchain for Banking, Asset, and Identify Services”. [cited by applicant]
U.S. Appl. No. 62/471,224, filed Mar. 17, 2017, “System and Method for Obtaining and/or Maintaining Insurance Coverage”. [cited by applicant]
U.S. Appl. No. 62/474,900, filed Mar. 22, 2017, “Providing Temporary Insurance Coverage Using Temorary Risk Data”. [cited by applicant]
U.S. Appl. No. 62/481,888, filed Apr. 5, 2017, “Using a Blockchain for Vehicle Lifecycle Processes”. [cited by applicant]
U.S. Appl. No. 62/482,792, filed Apr. 7, 2017, “Using a Blockchain for Vehicle Lifecycle Processes”. [cited by applicant]
U.S. Appl. No. 62/485,725, filed Apr. 14, 2017, “System and Method for Obtaining and/or Maintaining Insurance Coverage”. [cited by applicant]
U.S. Appl. No. 62/500,049, filed May 2, 2017, “Distributed Ledger System”. [cited by applicant]
U.S. Appl. No. 62/500,326, filed May 2, 2017, “Distributed Ledger System”. [cited by applicant]
U.S. Appl. No. 62/501,621, filed May 4, 2017, “Using a Blockchain for Vehicle Lifecycle Processes”. [cited by applicant]
U.S. Appl. No. 62/503,184, filed May 8, 2017, “System and Method for Obtaining and/or Maintaining Insurance Coverage”. [cited by applicant]
U.S. Appl. No. 62/504,328, filed May 10, 2017, “Method of Approving Dynamic Mortgage Application”. [cited by applicant]
U.S. Appl. No. 62/509,479, filed May 22, 2017, “Using a Blockchain for Vehicle Lifecycle Processes”. [cited by applicant]
U.S. Appl. No. 62/509,557, filed May 22, 2017, “Providing Temporary Insurance Coverage Using Temorary Risk Data”. [cited by applicant]
U.S. Appl. No. 62/510,664, filed May 24, 2017, “Blockchain Subrogation Payments”. [cited by applicant]
U.S. Appl. No. 62/514,470, filed Jun. 2, 2017, “System and Method of Utilizing Blockchain Technology to Approve and Update Dynamic Mortgage Applications”. [cited by applicant]
U.S. Appl. No. 62/515,923, filed Jun. 6, 2017, “Providing Temporary Insurance Coverage Using Temorary Risk Data”. [cited by applicant]
U.S. Appl. No. 62/520,376, filed Jun. 15, 2017, “Blockchain Based Banking Identity Authentication”. [cited by applicant]
U.S. Appl. No. 62/520,401, filed Jun. 15, 2017, “Blockchain Based Account Funing and Distribution”. [cited by applicant]
U.S. Appl. No. 62/520,648, filed Jun. 16, 2017, “Blockchain Based Card Activation”. [cited by applicant]
U.S. Appl. No. 62/520,708, filed Jun. 16, 2017, “Blockchain Based Passing Registry Actions”. [cited by applicant]
U.S. Appl. No. 62/521,784, filed Jan. 25, 2018, “Technology for Building and Managing Data Models”. [cited by applicant]
U.S. Appl. No. 62/523,523, filed Jun. 22, 2017, “Blockchain Based Asset Access”. [cited by applicant]
U.S. Appl. No. 62/528,791, filed Jul. 5, 2017, “Blockchain Based Lien Perfection”. [cited by applicant]
U.S. Appl. No. 62/528,806, filed Jul. 5, 2017, “Blockchain Based Settlement Processes”. [cited by applicant]
U.S. Appl. No. 62/532,072, filed Jul. 13, 2017, “Blockchain Based Contractor Ratings”. [cited by applicant]
U.S. Appl. No. 62/532,089, filed Jul. 13, 2017, “Blockchain Based Customer Records”. [cited by applicant]
U.S. Appl. No. 62/532, 102, filed Jul. 13, 2017, “Blockchain Based Associate Information and Licensing”. [cited by applicant]
U.S. Appl. No. 62/535,018, filed Jul. 20, 2017, “System and Method of Approving and Updating Dynamic Mortgage Applications”. [cited by applicant]
U.S. Appl. No. 62/536,600, filed Jul. 25, 2017, “Systems and Methods for Controlled Access to Blockchain Data”. [cited by applicant]
U.S. Appl. No. 62/536,672, filed Jul. 25, 2017, “Systems and Methods for Controlled Access to Policy Data on Blockchain”. [cited by applicant]
U.S. Appl. No. 62/536,683, filed Jul. 25, 2017, “Systems and Methods for Controlled Access to Audit Data on Blockchain”. [cited by applicant]
U.S. Appl. No. 62/536,698, filed Jul. 25, 2017, “Systems and Methods for Securely Filing Documents via Blockchain”. [cited by applicant]
U.S. Appl. No. 62/536,704, filed Jul. 25, 2017, “Systems and Methods for Verifying Agent Sales Data via Blockchain”. [cited by applicant]
U.S. Appl. No. 62/536,709, filed Jul. 25, 2017, “Systems and Methods for Fund Transfers via Blockchain”. [cited by applicant]
U.S. Appl. No. 62/536,715, filed Jul. 25, 2017, “Systems and Methods for Anti-Money Laundering Compliance via Blockchain”. [cited by applicant]
U.S. Appl. No. 62/536,716, filed Jul. 25, 2017, “Systems and Methods for Industry Reporting via Blockchain”. [cited by applicant]
U.S. Appl. No. 62/536,735, filed Jul. 25, 2017, “Sytems and Methods for Insurable Interest Validation via Blockchain”. [cited by applicant]
U.S. Appl. No. 62/536,754, filed Jul. 25, 2017, “Sytems and Methods for Blockchain-Based Payments”. [cited by applicant]
U.S. Appl. No. 62/537,084, filed Jul. 26, 2017, “System and Methods for Maintaining Transferability of Title via Blockchain”. [cited by applicant]
U.S. Appl. No. 62/540,299, filed Aug. 2, 2017, “Systems and Methods for Recall Compliance via Blockchain”. [cited by applicant]
U.S. Appl. No. 62/541,363, filed Aug. 4, 2017, “Systems and Methods for Sensor Recalibration via Blockchain”. [cited by applicant]
U.S. Appl. No. 62/541,386, filed Aug. 4, 2017, “Systems and Methods for Feature-Based via Blockchain”. [cited by applicant]
U.S. Appl. No. 62/542,066, filed Aug. 7, 2017, “Systems and Methods for Total Loss Handling via Blockchain”. [cited by applicant]
U.S. Appl. No. 62/542,081, filed Aug. 7, 2017, “Systems and Methods for Analyzing Vehicle Financing via Blockchain”. [cited by applicant]
U.S. Appl. No. 62/542,456, filed Aug. 8, 2017, “Systems and Methods for Usage Based Insurance via Blockchain”. [cited by applicant]
U.S. Appl. No. 62/542,477, filed Aug. 8, 2017, “Systems and Methods for Estimating Vehicle Value via Blockchain”. [cited by applicant]
U.S. Appl. No. 62/542,496, filed Aug. 8, 2017, “Systems and Methods for Post-Collision Vehicle Routing via Blockchain”. [cited by applicant]
U.S. Appl. No. 62/545,262, filed Aug. 14, 2017, “Distributed Ledger System for Managing Loss Histories”. [cited by applicant]
U.S. Appl. No. 62/548,668, filed Aug. 22, 2017, “Distributed Ledger System for Managing Vehicle Sensor Data Utilized to Develop Collision Profiles”. [cited by applicant]
U.S. Appl. No. 62/548,679, filed Aug. 22, 2017, “Distributed Ledger System for Use with Vehicle Sensor Data and Usage Based Systems”. [cited by applicant]
U.S. Appl. No. 62/548,682, filed Aug. 22, 2017, “Distributed Ledger System for Manging Medical Records”. [cited by applicant]
U.S. Appl. No. 62/548,692, filed Aug. 22, 2017, “Distributed Ledger System for Insurance Record Management Systems”. [cited by applicant]
U.S. Appl. No. 62/548,700, filed Aug. 22, 2017, “Distributed Ledger System for Managing Smart Vehicle Data”. [cited by applicant]
U.S. Appl. No. 62/548,731, filed Aug. 22, 2017, “Distributed Ledger System for Claim Payouts”. [cited by applicant]
U.S. Appl. No. 62/548,741, filed Aug. 22, 2017, “Distributed Ledger System for Smart Home Data”. [cited by applicant]
U.S. Appl. No. 62/548,748, filed Aug. 22, 2017, Distributed Ledger System for Carrier Discovery. [cited by applicant]
U.S. Appl. No. 62/550, 131, filed Aug. 25, 2017, “Maintaining a Distributed Ledger for VIN Recordkeeping”. [cited by applicant]
U.S. Appl. No. 62/550,140, filed Aug. 25, 2017, “Using a Distributed Ledger for Total Loss Management”. [cited by applicant]
U.S. Appl. No. 62/550,172, filed Aug. 25, 2017, “Using a Distributed Ledger for Tracking VIN Recordkeeping”. [cited by applicant]
U.S. Appl. No. 62/550,186, filed Aug. 25, 2017, “Smart Contracts for Vehicle Events”. [cited by applicant]
U.S. Appl. No. 62/550,197, filed Aug. 25, 2017, “Using a Distributed Ledger for Tracking Vehicle Financial Events”. [cited by applicant]
U.S. Appl. No. 62/550,224, filed Aug. 25, 2017, “Using a Distributed Ledger for the Auto Claims Process”. [cited by applicant]
U.S. Appl. No. 62/550,245, filed Aug. 25, 2017, “Using a Distributed Ledger to Track a VIN Lifecycle”. [cited by applicant]
U.S. Appl. No. 62/550,261, filed Aug. 25, 2017, “Using a Distributed Ledger for Proof of Insurance”. [cited by applicant]
U.S. Appl. No. 62/551,618, filed Aug. 29, 2017, “Risk Mitigation for Affinity Groupings”. [cited by applicant]
U.S. Appl. No. 62/554,907, filed Sep. 6, 2017, “Blockchain Based Claim Handling”. [cited by applicant]
U.S. Appl. No. 62/555,014, filed Sep. 6, 2017, “Fault Determination of Blockchain Subrogation Claims”. [cited by applicant]
U.S. Appl. No. 62/555,030, filed Sep. 6, 2017, “Using a Blockchain for the Subrogation Claim Process”. [cited by applicant]
U.S. Appl. No. 62/555,177, filed Sep. 7, 2017, “Fault Determination of Blockchain Subrogation Claims”. [cited by applicant]
U.S. Appl. No. 62/555,358, filed Sep. 7, 2017, “Using a Blockchain for the Subrogation Claim Process”. [cited by applicant]
U.S. Appl. No. 62/563,818, filed Sep. 27, 2017, “Automated Section of a Vehicle”. [cited by applicant]
U.S. Appl. No. 62/581,292, filed Nov. 3, 2017, “Approving and Updating Dynamic Mortgage Applications”. [cited by applicant]
U.S. Appl. No. 62/581,323, filed Nov. 3, 2017, “Continuously Monitoring and Updating Mortgage Ready Data”. [cited by applicant]
U.S. Appl. No. 62/581,356, filed Nov. 3, 2017, “Identifying Multiple Mortgage Ready Properties”. [cited by applicant]
U.S. Appl. No. 62/581,373, filed Nov. 3, 2017, “Incentivizing an Agent Based Upon Mortgage Ready Data Updated”. [cited by applicant]
U.S. Appl. No. 62/581,391, filed Nov. 3, 2017, “Approving and Updating Dynamic Mortgage Applications”. [cited by applicant]
U.S. Appl. No. 62/581,423, filed Nov. 3, 2017, “Continuously Monitoring and Updating Mortgage Ready Data”. [cited by applicant]
U.S. Appl. No. 62/581,442, filed Nov. 3, 2017, “Identifying Multiple Mortgage Ready Properties”. [cited by applicant]
U.S. Appl. No. 62/581,470, filed Nov. 3, 2017, “Incentivizing an Agent Based Upon Mortgage Ready Data Updated”. [cited by applicant]
U.S. Appl. No. 62/581,480, filed Nov. 3, 2017, “Approving and Updating Dynamic Mortgage Applications”. [cited by applicant]
U.S. Appl. No. 62/581,494, filed Nov. 3, 2017, “Continuously Monitoring and Updating Mortgage Ready Data”. [cited by applicant]
U.S. Appl. No. 62/581,521, filed Nov. 3, 2017, “Identifying Multiple Mortgage Ready Properties”. [cited by applicant]
U.S. Appl. No. 62/581,524, filed Nov. 3, 2017, “Incentivizing an Agent Based Upon Mortgage Ready Data Updated”. [cited by applicant]
U.S. Appl. No. 62/584,364, filed Nov. 10, 2017, “Blockchain Subrogation Payments”. [cited by applicant]
U.S. Appl. No. 62/584,435, filed Nov. 10, 2017, “Fault Determination of Blockchain Subrogation Claims”. [cited by applicant]
U.S. Appl. No. 62/589,444, filed Nov. 21, 2017, “Technology for Building and Managing Data Models”. [cited by applicant]
U.S. Appl. No. 62/592,975, filed Nov. 30, 2017, “Technology for Building and Managing Data Models”. [cited by applicant]
U.S. Appl. No. 62/593,727, filed Dec. 1, 2017, “Risk Mitigation for Affinity Groupings”. [cited by applicant]
U.S. Appl. No. 62/595,803, filed Dec. 7, 2017, “Evidence Oracles”. [cited by applicant]
U.S. Appl. No. 62/595,823, filed Dec. 7, 2017, “Using a Distributed Ledger for Subrogation Recommendations”. [cited by applicant]
U.S. Appl. No. 62/598,246, filed Dec. 13, 2017, “Using a Distributed Ledger for Line Item Determination”. [cited by applicant]
U.S. Appl. No. 62/599,103, filed Dec. 15, 2017, “Residence Provisioning Platform”. [cited by applicant]
U.S. Appl. No. 62/609,611, filed Dec. 22, 2017, “Using a Vehicle Mode for Subrogation on a Distributed Ledger”. [cited by applicant]
U.S. Appl. No. 62/609,644, filed Dec. 22, 2017, “Using a Historical Data for Subrogation on a Distributed Ledger”. [cited by applicant]
U.S. Appl. No. 62/609,786, filed Dec. 22, 2017, “Vehicle Creation of a Subrogation Distributed Ledger”. [cited by applicant]
U.S. Appl. No. 62/609,800, filed Dec. 22, 2017, “Using a Distributed Ledger to Detemine Fault in Subrogation”. [cited by applicant]
U.S. Appl. No. 62/615,286, filed Jan. 9, 2018, “Technology for Building and Managing Data Models”. [cited by applicant]
U.S. Appl. No. 62/617,824, filed Jan. 16, 2018, “Residence Provisioning Platform”. [cited by applicant]
U.S. Appl. No. 62/618,955, filed Jan. 18, 2018, “Residence Provisioning Platform”. [cited by applicant]
U.S. Appl. No. 15/870,292, Nonfinal Office Action, dated Dec. 31, 2019. [cited by applicant]
U.S. Appl. No. 15/87,350, Nonfinal Office Action, dated Oct. 10, 2019. [cited by applicant]
U.S. Appl. No. 15/870,364, Nonfinal Office Action, dated Oct. 9, 2019. [cited by applicant]
U.S. Appl. No. 15/870,371, Nonfinal Office Action, dated Aug. 28, 2019. [cited by applicant]
Van Oerle et al., “Distributed ledger technology for the financial industry, Blockchain Administration 3.0”, White Paper, Robeco (May 2016). [cited by applicant]
Haber & Stornetta, “How to Time-Stamp a Digital Document”, Bellcore, NJ (1991). [cited by applicant]
Mazieres and Shasha, “Building secure file systems out of Byzantine storage”, NYU (2002). [cited by applicant]
BlockstreetHQ Team, “Before Blockchain, There was Distributed Ledger Technology BlockstreetHQ,” Medium.com (2018). [cited by applicant]
Sneakernet, definition, Wikipedia. Retrieved from the Internet at: <https://en.wikipedia.org/wiki/Sneakernet> (2020). [cited by applicant]
File Transfer Protocol, definition/history/overview, Wikipedia. Retrieved from the Internet at: <https://en.wikipedia.org/wiki/File Transfer Protocol> (2020). [cited by applicant]
Distribution File system overview. Retrieved from the Internet at: <http://www.cse.chalmers.se/˜tsigas/Courses/DCDSeminar/Files/afs_report.pdf> (2020). [cited by applicant]
Authors et al.: Disclosed Anonymously, “Mechanism to Preserve Audit History Record for Insurance Claim Using Blockchain Smart Contract”, An IP.com Prior Art Database Technical Disclosure (2016). [cited by applicant]
C.L.U.E. ® Personal Property, “How to Read Your Rreport”, ChoicePoint (1999). [cited by applicant]
Goodman et al., “CLUE Reports Comprehensive Loss Underwriting Reports”, CLUE, Apr. 1, 2003. [cited by applicant]
Mainelli et al: “Sharing ledgers for sharing economies: an exploration of mutual distributed ledgers (aka blockchain technology)”, The Journal of Financial Perspectives: FinTech, EY Global Financial Services Institute, … [cited by applicant]
“Blockchain in the insurance sector,” Web page <https://www.pwc.co.uk/financialservices/fintech/assets/blockchain-in-insurance.pdf>, 2 pages, dated Aug. 7, 2016 by the Internet Archive Wayback Machine; retrieved from th… [cited by applicant]
Cointelegraph, “HashCoin Uses Emercoin Blockchain For Vehicle Registration and Tracking,” Retrieved from the Internet at: <https://cointelegraph.com/news/hashcoin-uses-emercoin-blockchain-forvehicle-registration-and-tra… [cited by applicant]
Azaria et al., MedRec: Using blockchain for medical data access and permission management, 2016 2nd International Conference on Open and Big Data, pp. 25-30 (2016). [cited by applicant]
Gatteschi et al., Blockchain and smart contracts for insurance: is the technology mature enough?, Future Internet, 10,20 (2018). [cited by applicant]
Antonopoulos, Mastering Bitcoin: Unlocking Digital Crypto-Currencies, Sebastopol, California: O'Reilly Media, Inc., 282 pp. (2010). [cited by applicant]
Lorenz et al., Blockchain in Insurance—Oportunity or Threat, Jul. 2016, pp. 1-9 (Year: 2016). [cited by applicant]
Cited By (1)
US 12,586,139