US 11,734,770 B2
Using a distributed ledger to determine fault in subrogation
William J. Leise, Normal, IL (US); Douglas A. Graff, Mountain View, MO (US); Anthony McCoy, Normal, IL (US); Jaime Skaggs, Chenoa, IL (US); Shawn M. Call, Bloomington, IL (US); Stacie A. McCullough, Bloomington, IL (US); Wendy H. Clayton, Franklin, TN (US); Melinda Teresa Magerkurth, Utica, IL (US); Kim E. Flesher, Normal, IL (US); and Travis Charles Runge, Heyworth, IL (US)
Assigned to STATE FARM MUTUAL AUTOMOBILE INSURANCE COMPANY, Bloomington, IL (US)
Filed by STATE FARM MUTUAL AUTOMOBILE INSURANCE COMPANY, Bloomington, IL (US)
Filed on Nov. 17, 2022, as Appl. No. 17/989,562.
Application 17/989,562 is a continuation of application No. 17/740,264, filed on May 9, 2022.
Application 17/740,264 is a continuation of application No. 15/956,578, filed on Apr. 18, 2018, granted, now 11,416,942.
Claims priority of provisional application 62/609,800, filed on Dec. 22, 2017.
Claims priority of provisional application 62/555,358, filed on Sep. 7, 2017.
Claims priority of provisional application 62/554,907, filed on Sep. 6, 2017.
Claims priority of provisional application 62/555,030, filed on Sep. 6, 2017.
Prior Publication US 2023/0080371 A1, Mar. 16, 2023
This patent is subject to a terminal disclaimer.
Int. Cl. G06Q 40/08 (2012.01); G07C 5/00 (2006.01); H04L 9/06 (2006.01); G07C 5/08 (2006.01); G06N 20/00 (2019.01); H04L 9/00 (2022.01)
CPC G06Q 40/08 (2013.01) [G06N 20/00 (2019.01); G07C 5/008 (2013.01); G07C 5/0816 (2013.01); G07C 5/0866 (2013.01); H04L 9/0637 (2013.01); H04L 9/50 (2022.05)] 20 Claims
OG exemplary drawing
 
1. A computer-implemented method of handling an electronic subrogation demand via a shared ledger, the method comprising:
specifying, in a smart contract of the electronic subrogation demand and via one or more processors, an identity of a subrogation claimant by assigning a first cryptographic public key to the subrogation claimant;
specifying, in the smart contract and via the one or more processors, an identity of a subrogation defendant by assigning a second cryptographic public key to the subrogation defendant;
signing, with the one or more processors, a message with private keys corresponding to the first and second public keys identifying the subrogation claimant and the subrogation defendant; and
sending, to the smart contract and via the one or more processors, data including the message signed by the private keys corresponding to the first and second public keys identifying the subrogation claimant and the subrogation defendant.