Source: https://patents.com/us-9786154.html
Timestamp: 2019-10-20 04:00:19
Document Index: 629950417

Matched Legal Cases: ['art\n2005', 'art 6', 'Application No. 13167206', 'Application No. 62', 'Application No. 62', 'Application No. 62', 'Application No. 62', 'Application No. 62', 'Application No. 62', 'Application No. 62', 'Application No. 62', 'Application No. 62', 'Application No. 62', 'Application No. 62', 'Application No. 62', 'Application No. 62']

US Patent # 9,786,154. Methods of facilitating emergency assistance - Patents.com
United States Patent 9,786,154
Potter , et al. October 10, 2017
In system and methods for loss mitigation, accident data associated with a vehicle accident involving a driver may be collected. The accident data may be analyzed, and a likely severity of the vehicle accident may be determined based upon the analysis of the accident data. A communication related to emergency assistance or an emergency assistance recommendation may be generated based upon the determined likely severity of the vehicle accident, and transmitted, via wireless communication, from one or more remote servers to a mobile device associated with the driver. A wireless communication from the driver indicating approval or modification of the emergency assistance or emergency assistance recommendation may be received. A third party may be notified, via a communication sent from the remote server(s), of requested emergency assistance as approved or modified by the driver. An estimated insurance claim may also be generated based upon vehicle accident likely severity.
Potter; Thomas Michael (Normal, IL), Clauss; Mark E. (Bloomington, IL), Carter; Dustin Ryan (Normal, IL), Graff; Douglas Albert (Mountain View, MO), Baumann; Megan Michal (Bloomington, IL), Bonnom; Atlanta (Bloomington, IL), Cope; Craig (Bloomington, IL), Lawyer; Jennifer Luella (Bloomington, IL), Simpson; Curtis (Bloomington, IL), Baumann; Nathan W. (Bloomington, IL)
Family ID: 1000001273528
14/798,757
62145022 Apr 9, 2015
62145234 Apr 9, 2015
62145027 Apr 9, 2015
62145228 Apr 9, 2015
62145029 Apr 9, 2015
62145232 Apr 9, 2015
62145032 Apr 9, 2015
62145033 Apr 9, 2015
62145024 Apr 9, 2015
62145028 Apr 9, 2015
62145145 Apr 9, 2015
62040735 Aug 22, 2014
62027021 Jul 21, 2014
Current CPC Class: G08B 25/00 (20130101); G08B 21/02 (20130101); G06Q 40/08 (20130101); B60W 2030/082 (20130101)
Current International Class: B60Q 1/00 (20060101); G08B 25/00 (20060101); G06Q 40/08 (20120101); G08B 21/02 (20060101); B60W 30/08 (20120101)
Field of Search: ;340/426.12,539.12,439,436,435,438 ;705/4,400,325,26.7 ;455/557,404.1,456.2
4218763 August 1980 Kelley et al.
4565997 January 1986 Seko et al.
5363298 November 1994 Survanshi et al.
5367456 November 1994 Summerville et al.
5368484 November 1994 Copperman et al.
5436839 July 1995 Dausch et al.
5515026 May 1996 Ewert
5626362 May 1997 Mottola
5835008 November 1998 Colemere, Jr.
5978720 November 1999 Hieronymus
6215200 April 2001 Genzel
6285931 September 2001 Hattori et al.
6313749 November 2001 Horne et al.
6553354 April 2003 Hausner et al.
6570609 May 2003 Heien
6704434 March 2004 Sakoh et al.
6909407 June 2005 Schradi
6909947 June 2005 Douros et al.
6934365 August 2005 Suganuma et al.
6956470 October 2005 Heise
6989737 January 2006 Yasui
7054723 May 2006 Seto et al.
7138922 November 2006 Strumolo et al.
7149533 December 2006 Laird et al.
7200207 April 2007 Meer
7253724 August 2007 Prakah-Asante et al.
7254482 August 2007 Kawasaki et al.
7302344 November 2007 Olney et al.
7315233 January 2008 Yuhara
7330124 February 2008 Ota
7356392 April 2008 Hubbard et al.
7386376 June 2008 Basir et al.
7391784 June 2008 Renkel
7424414 September 2008 Craft
7609150 October 2009 Wheatley et al.
7692552 April 2010 Harrington et al.
7783505 August 2010 Roschelle et al.
7812712 October 2010 White et al.
7835834 November 2010 Smith et al.
7865378 January 2011 Gay
7870010 January 2011 Joao
7881951 February 2011 Roschelle et al.
7890355 February 2011 Gay et al.
7904219 March 2011 Lowrey et al.
7987103 July 2011 Gay et al.
8005467 August 2011 Gerlach
8009051 August 2011 Omi
8010283 August 2011 Yoshida et al.
8016595 September 2011 Aoki et al.
8027853 September 2011 Kazenas
8040247 October 2011 Gunaratne
8095394 January 2012 Nowak et al.
8117049 February 2012 Berkobin et al.
8140359 March 2012 Daniel
8180522 May 2012 Tuff
8185380 May 2012 Kameyama
8188887 May 2012 Catten et al.
8190323 May 2012 Maeda et al.
8255243 August 2012 Raines et al.
8255244 August 2012 Raines et al.
8260639 September 2012 Medina, III
8265861 September 2012 Ikeda et al.
8340893 December 2012 Yamaguchi et al.
8344849 January 2013 Larsson et al.
8352118 January 2013 Mittelsteadt et al.
8355837 January 2013 Avery et al.
8364391 January 2013 Nagase et al.
8384534 February 2013 James et al.
8386168 February 2013 Hao
8423239 April 2013 Blumer et al.
8447231 May 2013 Bai et al.
8473143 June 2013 Stark et al.
8554468 October 2013 Bullock
8554587 October 2013 Nowak et al.
8595034 November 2013 Bauer et al.
8645014 February 2014 Kozlowski
8645029 February 2014 Kim et al.
8700251 April 2014 Zhu et al.
8742936 June 2014 Galley et al.
8788299 July 2014 Medina, III
8816836 August 2014 Lee et al.
8849558 September 2014 Morotomi et al.
8876535 November 2014 Fields
8880291 November 2014 Hampiholi
8965677 February 2015 Breed et al.
9049584 June 2015 Hatton
9053588 June 2015 Briggs
9056395 June 2015 Ferguson et al.
9056616 June 2015 Fields
9070243 June 2015 Kozlowski
9135803 September 2015 Fields
9147353 September 2015 Slusar
9164507 October 2015 Cheatham, III et al.
9180888 November 2015 Fields
9205842 December 2015 Fields
9274525 March 2016 Ferguson et al.
9275417 March 2016 Binion et al.
9275552 March 2016 Fields
9279697 March 2016 Fields
9282430 March 2016 Brandmaier
9282447 March 2016 Gianakis
9283847 March 2016 Riley, Sr.
9299108 March 2016 Diana et al.
9317983 April 2016 Ricci
9342993 May 2016 Fields
9352709 May 2016 Brenneis et al.
9355423 May 2016 Slusar
9361650 June 2016 Binion et al.
9373203 June 2016 Fields
9376090 June 2016 Gennermann
9384674 July 2016 Nepomuceno
9390451 July 2016 Slusar
9430944 August 2016 Grimm et al.
9440657 September 2016 Fields
9443152 September 2016 Atsmon et al.
9454786 September 2016 Srey et al.
9457754 October 2016 Christensen
9466214 October 2016 Fuehrer
9477990 October 2016 Binion
9478150 October 2016 Fields
9530333 December 2016 Fields
9583017 February 2017 Nepomuceno
9601027 March 2017 Nepomuceno
9646428 May 2017 Konrardy
9646433 May 2017 Sanchez
2001/0005217 June 2001 Hamilton et al.
2002/0146667 October 2002 Dowdell et al.
2003/0028298 February 2003 Macky et al.
2003/0061160 March 2003 Asahina
2004/0017106 January 2004 Aizawa et al.
2004/0085198 May 2004 Saito et al.
2004/0090334 May 2004 Zhang et al.
2004/0111301 June 2004 Wahlbin et al.
2004/0122639 June 2004 Qiu
2004/0158476 August 2004 Blessinger et al.
2004/0198441 October 2004 Cooper
2004/0226043 November 2004 Mettu et al.
2005/0108910 May 2005 Esparza et al.
2005/0134443 June 2005 Hottebart
2005/0228763 October 2005 Lewis et al.
2005/0259151 November 2005 Hamilton et al.
2005/0267784 December 2005 Slen et al.
2006/0031103 February 2006 Henry
2006/0079280 April 2006 LaPerch
2006/0136291 June 2006 Morita et al.
2006/0212195 September 2006 Veith et al.
2006/0220905 October 2006 Hovestadt
2006/0232430 October 2006 Takaoka et al.
2007/0001831 January 2007 Raz et al.
2007/0055422 March 2007 Anzai et al.
2007/0080816 April 2007 Haque et al.
2007/0088469 April 2007 Schmiedel et al.
2007/0122771 May 2007 Maeda et al.
2007/0219720 September 2007 Trepagnier et al.
2007/0249372 October 2007 Gao
2007/0291130 December 2007 Broggi et al.
2007/0299700 December 2007 Gay et al.
2008/0027761 January 2008 Bracha
2008/0052134 February 2008 Nowak et al.
2008/0061953 March 2008 Bhogal et al.
2008/0064014 March 2008 Wojtczak et al.
2008/0082372 April 2008 Burch
2008/0106390 May 2008 White
2008/0114502 May 2008 Breed et al.
2008/0126137 May 2008 Kidd et al.
2008/0143497 June 2008 Wasson et al.
2008/0180237 July 2008 Fayyad et al.
2008/0195457 August 2008 Sherman et al.
2008/0291008 November 2008 Jeon
2008/0297488 December 2008 Operowsky et al.
2009/0015684 January 2009 Ooga et al.
2009/0040060 February 2009 Anbuhl
2009/0063030 March 2009 Howarter et al.
2009/0069953 March 2009 Hale et al.
2009/0207005 August 2009 Habetha et al.
2009/0210257 August 2009 Chalfant et al.
2009/0247113 October 2009 Sennett
2009/0267801 October 2009 Kawai et al.
2009/0303026 December 2009 Broggi et al.
2010/0004995 January 2010 Hickman
2010/0030540 February 2010 Choi et al.
2010/0076646 March 2010 Basir et al.
2010/0106356 April 2010 Trepagnier et al.
2010/0128127 May 2010 Ciolli
2010/0131302 May 2010 Collopy et al.
2010/0131307 May 2010 Collopy et al.
2010/0142477 June 2010 Yokota
2010/0214087 August 2010 Nakagoshi et al.
2010/0219944 September 2010 McCormick et al.
2010/0293033 November 2010 Hall et al.
2010/0299021 November 2010 Jalili
2011/0054767 March 2011 Schafer et al.
2011/0066310 March 2011 Sakai et al.
2011/0087505 April 2011 Terlep
2011/0090075 April 2011 Armitage et al.
2011/0093350 April 2011 Laumeyer et al.
2011/0133954 June 2011 Ooshima et al.
2011/0137684 June 2011 Peak et al.
2011/0140968 June 2011 Bai et al.
2011/0169625 July 2011 James et al.
2011/0295446 December 2011 Basir et al.
2011/0301839 December 2011 Pudar et al.
2011/0307188 December 2011 Peng
2012/0066007 March 2012 Ferrick et al.
2012/0081221 April 2012 Doerr
2012/0083668 April 2012 Pradeep et al.
2012/0083974 April 2012 Sandblom
2012/0108909 May 2012 Slobounov et al.
2012/0109407 May 2012 Yousefi et al.
2012/0135382 May 2012 Winston et al.
2012/0143630 June 2012 Hertenstein
2012/0172055 July 2012 Edge
2012/0185204 July 2012 Jallon et al.
2012/0190001 July 2012 Knight et al.
2012/0191343 July 2012 Haleem
2012/0209634 August 2012 Ling
2012/0215375 August 2012 Chang
2012/0235865 September 2012 Nath et al.
2012/0239471 September 2012 Grimm et al.
2012/0239822 September 2012 Poulson
2012/0246733 September 2012 Schafer et al.
2012/0258702 October 2012 Matsuyama
2012/0277950 November 2012 Plante et al.
2012/0284747 November 2012 Joao
2012/0316406 December 2012 Rahman et al.
2013/0006675 January 2013 Bowne
2013/0017846 January 2013 Schoppe
2013/0018677 January 2013 Chevrette
2013/0038437 February 2013 Talati et al.
2013/0044008 February 2013 Gafford et al.
2013/0046562 February 2013 Taylor et al.
2013/0073115 March 2013 Levin et al.
2013/0144459 June 2013 Ricci
2013/0151202 June 2013 Denny et al.
2013/0164715 June 2013 Hunt et al.
2013/0179198 July 2013 Bowne
2013/0189649 July 2013 Mannino
2013/0209968 August 2013 Miller et al.
2013/0227409 August 2013 Das et al.
2013/0245881 September 2013 Scarbrough
2013/0289819 October 2013 Hassib et al.
2013/0307786 November 2013 Heubel
2013/0317865 November 2013 Tofte
2013/0332402 December 2013 Rakshit
2013/0339062 December 2013 Brewer
2014/0002651 January 2014 Plante
2014/0009307 January 2014 Bowers et al.
2014/0012492 January 2014 Bowers et al.
2014/0039934 February 2014 Rivera
2014/0047347 February 2014 Mohn et al.
2014/0047371 February 2014 Palmer et al.
2014/0052323 February 2014 Reichel et al.
2014/0058761 February 2014 Freiberger et al.
2014/0070980 March 2014 Park
2014/0095214 April 2014 Mathe et al.
2014/0099607 April 2014 Armitage et al.
2014/0100892 April 2014 Collopy et al.
2014/0106782 April 2014 Chitre
2014/0108198 April 2014 Jariyasunant et al.
2014/0111647 April 2014 Atsmon et al.
2014/0167967 June 2014 He
2014/0168399 June 2014 Plummer et al.
2014/0191858 July 2014 Morgan
2014/0218187 August 2014 Chun et al.
2014/0236638 August 2014 Pallesen et al.
2014/0253376 September 2014 Large et al.
2014/0257866 September 2014 Gay et al.
2014/0277916 September 2014 Mullen
2014/0278569 September 2014 Sanchez
2014/0278840 September 2014 Scofield et al.
2014/0301218 October 2014 Luo et al.
2014/0358324 December 2014 Sagar et al.
2014/0376410 December 2014 Ros
2014/0378082 December 2014 Ros
2015/0024705 January 2015 Rashidi
2015/0039350 February 2015 Martin et al.
2015/0051752 February 2015 Paszkowicz
2015/0088373 March 2015 Wilkins
2015/0112504 April 2015 Binion et al.
2015/0120331 April 2015 Russo et al.
2015/0127570 May 2015 Doughty
2015/0142262 May 2015 Lee
2015/0158469 June 2015 Cheatham, III et al.
2015/0158495 June 2015 Duncan et al.
2015/0160653 June 2015 Cheatham, III et al.
2015/0161893 June 2015 Duncan et al.
2015/0161894 June 2015 Duncan et al.
2015/0178998 June 2015 Attard et al.
2015/0193219 July 2015 Pandya et al.
2015/0235557 August 2015 Engelman et al.
2015/0254955 September 2015 Fields et al.
2015/0294422 October 2015 Carver et al.
2015/0348337 December 2015 Choi
2016/0027276 January 2016 Freeck et al.
2016/0036899 February 2016 Moody
2016/0092962 March 2016 Wasserman
2016/0093212 March 2016 Barfield, Jr.
2016/0105365 April 2016 Droste et al.
2016/0277911 September 2016 Kang et al.
700009 Mar 1996 EP
2494727 Mar 2013 GB
2002-259708 Sep 2002 JP
WO-2005/083605 Sep 2005 WO
WO-2010/034909 Apr 2010 WO
WO-2014/139821 Sep 2014 WO
WO-2014/148976 Sep 2014 WO
WO-2016/156236 Oct 2016 WO
"Driverless Cars . . . The Future is Already Here", AutoInsurance Center, downloaded from the Internet at: <http://www.autoinsurancecenter.com/driverless-cars . . . the-future-is-already-here.htm> (2010; downloaded on Mar. 27, 2014). cited by applicant .
"Integrated Vehicle-Based Safety Systems (IVBSS)", Research and Innovative Technology Administration (RITA), http://www.its.dot.gov/ivbss/, retrieved from the internet on Nov. 4, 2013, 3 pages. cited by applicant .
Advisory Action dated Apr. 1, 2015 for U.S. Appl. No. 14/269,490, 4 pgs. cited by applicant .
Carroll et al. "Where Innovation is Sorely Needed", http://www.technologyreview.com/news/422568/where-innovation-is-sorely-ne- eded/?nlid, retrieved from the internet on Nov. 4, 2013, 3 pages. cited by applicant .
Davies, Avoiding Squirrels and Other Things Google's Robot Car Can't Do, downloaded from the Internet at: <http://www.wired.com/2014/05/google-self-driving-car-can-cant/ (downloaded on May 28, 2014). cited by applicant .
Fields et al., U.S. Appl. No. 14/511,712, filed Oct. 10, 2014. cited by applicant .
Fields et al., U.S. Appl. No. 14/511,750, filed Oct. 10, 2014. cited by applicant .
Final Office Action, U.S. Appl. No. 14/255,934, dated Sep. 23, 2014. cited by applicant .
Final Office Action, U.S. Appl. No. 14/269,490, dated Jan. 23, 2015. cited by applicant .
Hancock, G.M., P.A. Hancock, and C.M. Janelle, "The Impact of Emotions and Predominant Emotion Regulation Technique on Driving Performance," pp. 5882-5885, 2012. cited by applicant .
Levendusky, Advancements in automotive technology and their effect on personal auto insurance, downloaded from the Internet at: <http://www.verisk.com/visualize/advancements-in-automotive-technology- -and-their-effect> (2013). cited by applicant .
McCraty, R., B. Barrios-Choplin, M. Atkinson, and D. Tomasino. "The Effects of Different Types of Music on Mood, Tension, and Mental Clarity." Alternative Therapies in Health and Medicine 4.1 (1998): 75-84. NCBI PubMed. Web. Jul. 11, 2013. cited by applicant .
Mui, Will auto insurers survive their collision with driverless cars? (Part 6), downloaded from the Internet at: <http://www.forbes.com/sites/chunkamui/2013/03/28/will-auto-insurers-s- urvive-their-collision> (Mar. 28, 2013). cited by applicant .
Nonfinal Office Action, U.S. Appl. No. 14/255,934, dated Jan. 15, 2015. cited by applicant .
Nonfinal Office Action, U.S. Appl. No. 14/255,934, dated Jun. 18, 2014. cited by applicant .
Nonfinal Office Action, U.S. Appl. No. 14/269,490, dated Sep. 12, 2014. cited by applicant .
Notice of Allowance in U.S. Appl. No. 14/057,408 dated Sep. 25, 2014. cited by applicant .
Notice of Allowance in U.S. Appl. No. 14/057,419 dated Oct. 5, 2015. cited by applicant .
Notice of Allowance in U.S. Appl. No. 14/208,626 dated May 11, 2015. cited by applicant .
Notice of Allowance in U.S. Appl. No. 14/208,626 dated Sep. 1, 2015. cited by applicant .
Notice of Allowance in U.S. Appl. No. 14/255,934 dated May 27, 2015. cited by applicant .
Notice of Allowance in U.S. Appl. No. 14/729,290 dated Aug. 5, 2015. cited by applicant .
Office Action dated Dec. 26, 2014 for U.S. Appl. No. 14/511,712, 21 pgs. cited by applicant .
Office Action in U.S. Appl. No. 13/844,090 dated Dec. 4, 2013. cited by applicant .
Office Action in U.S. Appl. No. 14/057,419 dated Mar. 31, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/057,419 dated Oct. 9, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/057,456 dated Mar. 17, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/201,491 dated Apr. 29, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/201,491 dated Jan. 16, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/201,491 dated Sep. 11, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/201,491 dated Sep. 26, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/215,789 dated Sep. 17, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/255,934 dated Jan. 15, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/255,934 dated Jun. 18, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/255,934 dated Sep. 23, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/269,490 dated Jan. 23, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/269,490 dated Jun. 11, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/269,490 dated Sep. 12, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/511,712 dated Jun. 25, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/511,712 dated Oct. 10, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/511,750 dated Dec. 19, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/511,750 dated Jun. 30, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/057,408 dated Jan. 28, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/057,408 dated May 22, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/057,419 dated Jan. 28, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/057,419 dated Jun. 18, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/057,435 dated Jul. 23, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/057,435 dated Mar. 20, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/057,435 dated May 29, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/057,435 dated Nov. 18, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/057,447 dated Aug. 28, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/057,447 dated Dec. 18, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/057,447 dated Feb. 24, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/057,447 dated Jul. 6, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/057,456 dated Mar. 14, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/057,456 dated Oct. 28, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/057,467 dated Feb. 23, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/057,467 dated Jan. 27, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/057,467 dated Jun. 11, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/057,467 dated Oct. 17, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/208,626 dated Apr. 29, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/208,626 dated Aug. 13, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/208,626 dated Dec. 23, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/339,652 dated May 15, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/339,652 dated Oct. 23, 2014. cited by applicant .
Office Action in U.S. Appl. No. 14/339,652 dated Sep. 24, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/528,424 dated Feb. 27, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/528,424 dated Jul. 30, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/528,642 dated Jan. 13, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/713,230 dated Oct. 9, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/713,254 dated Oct. 9, 2015. cited by applicant .
Office Action in U.S. Appl. No. 14/718,338 dated Jul. 7, 2015. cited by applicant .
Office Action, U.S. Appl. No. 14/713,261, dated Oct. 21, 2015. cited by applicant .
Read, Autonomous cars & the death of auto insurance, downloaded from the Internet at: <http://www.thecarconnection.com/news/1083266.sub.--autonomous-cars-th- e-death-of-auto-insurance> (Apr. 1, 2013). cited by applicant .
Riley et al., U.S. Appl. No. 14/269,490, filed May 5, 2014. cited by applicant .
Ryan, Can having safety features reduce your insurance premiums? (Dec. 15, 2010). cited by applicant .
Search Report in EP Application No. 13167206.5 dated Aug. 13, 2013, 6 pages. cited by applicant .
Sharma, Driving the future: the legal implications of autonomous vehicles conference recap, downloaded from the Internet at: <http://law.scu.edu/hightech/autonomousvehicleconfrecap2012> (2012). cited by applicant .
Stienstra, Autonomous Vehicles & the Insurance Industry, 2013 CAS Annual Meeting--Minneapolis, MN (2013). cited by applicant .
U.S. Appl. No. 14/215,789, filed Mar. 17, 2014, Baker et al., "Split Sensing Method". cited by applicant .
U.S. Appl. No. 14/339,652, filed Jul. 24, 2014, Freeck et al., "System and Methods for Monitoring a Vehicle Operator and Monitoring an Operating Environment Within the Vehicle". cited by applicant .
U.S. Appl. No. 14/528,424, filed Oct. 30, 2014, Christensen et al., "Systems and Methods for Processing Trip-Based Insurance Policies". cited by applicant .
U.S. Appl. No. 14/528,642, filed Oct. 30, 2014, Christensen et al., "Systems and Methods for Managing Units Associated with Time-Based Insurance Policies". cited by applicant .
U.S. Appl. No. 14/713,184, filed May 15, 2015, Konrardy et al., "Autonomous Vehicle Insurance Pricing". cited by applicant .
U.S. Appl. No. 14/713,188, filed May 15, 2015, Konrardy et al., "Autonomous Feature Use Monitoring and Insurance Pricing". cited by applicant .
U.S. Appl. No. 14/713,194, filed May 15, 2015, Konrardy et al., "Autonomous Communication Feature Use and Insurance Pricing". cited by applicant .
U.S. Appl. No. 14/713,201, filed May 15, 2015, Konrardy et al., "Autonomous Vehicle Insurance Pricing and Offering Based Upon Accident Risk Factors". cited by applicant .
U.S. Appl. No. 14/713,206, filed May 15, 2015, Konrardy et al., "Determining Autonomous Vehicle Technology Performance for Insurance Pricing and Offering". cited by applicant .
U.S. Appl. No. 14/713,214, filed May 15, 2015, Konrardy et al., "Accident Risk Model Determination Using Autonomous Vehicle Operating Data". cited by applicant .
U.S. Appl. No. 14/713,217, filed May 15, 2015, Konrardy et al., "Autonomous Vehicle Operation Feature Usage Recommendations". cited by applicant .
U.S. Appl. No. 14/713,223, filed May 15, 2015, Konrardy et al., "Driver Feedback Alerts Based Upon Monitoring Use of Autonomous Vehicle Operation Features". cited by applicant .
U.S. Appl. No. 14/713,226, filed May 15, 2015, Konrardy et al., "Accident Response Using Autonomous Vehicle Monitoring". cited by applicant .
U.S. Appl. No. 14/713,230, filed May 15, 2015, Konrardy et al., "Accident Fault Determination for Autonomous Vehicles". cited by applicant .
U.S. Appl. No. 14/713,237, filed May 15, 2015, Konrardy et al., "Autonomous Vehicle Technology Effectiveness Determination for Insurance Pricing". cited by applicant .
U.S. Appl. No. 14/713,240, filed May 15, 2015, Konrardy et al., "Fault Determination with Autonomous Feature Use Monitoring". cited by applicant .
U.S. Appl. No. 14/713,244, filed May 15, 2015, Konrardy et al., "Autonomous Vehicle Operation Feature Evaulation". cited by applicant .
U.S. Appl. No. 14/713,249, filed May 15, 2015, Konrardy et al., "Autonomous Vehicle Operation Feature Monitoring and Evaluation of Effectiveness". cited by applicant .
U.S. Appl. No. 14/713,254, filed May 15, 2015, Konrardy et al., "Accident Fault Determination for Autonomous Vehicles". cited by applicant .
U.S. Appl. No. 14/713,261, filed May 15, 2015, Konrardy et al., "Accident Fault Determination for Autonomous Vehicles". cited by applicant .
U.S. Appl. No. 14/713,266, filed May 15, 2015, Konrardy et al., "Autonomous Vehicle Operation Feature Monitoring and Evaluation of Effectiveness". cited by applicant .
U.S. Appl. No. 14/713,271, filed May 15, 2015, Konrardy et al. "Fully Autonomous Vehicle Insurance Pricing". cited by applicant .
U.S. Appl. No. 14/729,290, filed Jun. 3, 2015, Fields et al., "Advanced Vehicle Operator Intelligence System". cited by applicant .
U.S. Appl. No. 14/857,242, filed Sep. 17, 2015, Fields et al., "Advanced Vehicle Operator Intelligence System". cited by applicant .
Wiesenthal, David L., Dwight A. Hennessy, and Brad Totten, "The Influence of Music on Driver Stress," Journal of Applied Social Psychology 30, 8, pp. 1709-1719, 2000. cited by applicant .
Young et al., "Cooperative Collision Warning Based Highway Vehicle Accident Reconstruction", Eighth International Conference on Intelligent Systems Design and Applications, Nov. 26-28, 2008, pp. 561-565. cited by applicant .
"Linking Driving Behavior to Automobile Accidents and Insurance Rates: An Analysis of Five Billion Miles Driven", Progressive Insurance brochure (Jul. 2012). cited by applicant .
"Self-Driving Cars: The Next Revolution", KPMG, Center for Automotive Research (2012). cited by applicant .
The Influence of Telematics on Customer Experience: Case Study of Progressive's Snapshot Program, J.D. Power Insights, McGraw Hill Financial (2013). cited by applicant .
Alberi et al., A proposed standardized testing procedure for autonomous ground vehicles, Virginia Polytechnic Institute and State University, 63 pages (Apr. 29, 2008). cited by applicant .
Broggi et al., Extensive Tests of Autonomous Driving Technologies, IEEE Trans on Intelligent Transportation Systems, 14(3):1403-15 (May 30, 2013). cited by applicant .
Campbell et al., Autonomous Driving in Urban Environments: Approaches, Lessons, and Challenges, Phil. Trans. R. Soc. A, 368:4649-72 (2010). cited by applicant .
Figueiredo et al., An Approach to Simulate Autonomous Vehicles in Urban Traffic Scenarios, University of Porto, 7 pages (Nov. 2009). cited by applicant .
Gechter et al., Towards a Hybrid Real/Virtual Simulation of Autonomous Vehicles for Critical Scenarios, International Academy Research and Industry Association (IARIA), 4 pages (2014). cited by applicant .
Hars, Autonomous Cars: The Next Revolution Looms, Inventivio GmbH, 4 pages (Jan. 2010). cited by applicant .
Lee et al., Autonomous Vehicle Simulation Project, Int. J. Software Eng. and Its Applications, 7(5):393-402 (2013). cited by applicant .
Miller, A simulation and regression testing framework for autonomous workers, Case Western Reserve University, 12 pages (Aug. 2007). cited by applicant .
Pereira, An Integrated Architecture for Autonomous Vehicle Simulation, University of Porto., 114 pages (Jun. 2011). cited by applicant .
Quinlan et al., Bringing Simulation to Life: A Mixed Reality Autonomous Intersection, Proc. IROS 2010--IEEE/RSJ International Conference on Intelligent Robots and Systems, Taipei Taiwan, 6 pages (Oct. 2010). cited by applicant .
Reddy, The New Auto Insurance Ecosystem: Telematics, Mobility and the Connected Car, Cognizant (Aug. 2012). cited by applicant .
Reifel et al., "Telematics: The Game Changer--Reinventing Auto Insurance", A.T. Kearney (2010). cited by applicant .
Roberts, "What is Telematics Insurance?", MoneySupermarket (Jun. 20, 2012). cited by applicant .
Stavens, Learning to Drive: Perception for Autonomous Cars, Stanford University, 104 pages (May 2011). cited by applicant .
U.S. Appl. No. 13/844,090, Notice of Allowance, dated Jul. 8, 2014. cited by applicant .
U.S. Appl. No. 13/844,090, Office Action, dated Dec. 4, 2013. cited by applicant .
U.S. Appl. No. 14/057,408, Notice of Allowance, dated Sep. 25, 2014. cited by applicant .
U.S. Appl. No. 14/057,419, Notice of Allowance, dated Oct. 5, 2015. cited by applicant .
U.S. Appl. No. 14/057,435, Notice of Allowance, dated Apr. 1, 2016. cited by applicant .
U.S. Appl. No. 14/057,447, Final Office Action, dated Jun. 20, 2016. cited by applicant .
U.S. Appl. No. 14/057,447, Nonfinal Office Action, dated Dec. 11, 2015. cited by applicant .
U.S. Appl. No. 14/057,447, Nonfinal Office Action, dated Sep. 28, 2016. cited by applicant .
U.S. Appl. No. 14/057,456, Final Office Action, dated Jun. 16, 2016. cited by applicant .
U.S. Appl. No. 14/057,456, Final Office Action, dated Mar. 17, 2015. cited by applicant .
U.S. Appl. No. 14/057,456, Nonfinal Office Action, dated Dec. 3, 2015. cited by applicant .
U.S. Appl. No. 14/057,456, Nonfinal Office Action, dated Mar. 9, 2017. cited by applicant .
U.S. Appl. No. 14/057,467, Final Office Action, dated Dec. 7, 2016. cited by applicant .
U.S. Appl. No. 14/057,467, Final Office Action, dated Mar. 16, 2016. cited by applicant .
U.S. Appl. No. 14/057,467, Nonfinal Office Action, dated Jul. 1, 2016. cited by applicant .
U.S. Appl. No. 14/057,467, Nonfinal Office Action, Nov. 12, 2015. cited by applicant .
U.S. Appl. No. 14/201,491, Final Office Action, dated Sep. 11, 2015. cited by applicant .
U.S. Appl. No. 14/208,626, Notice of Allowance, dated May 11, 2015. cited by applicant .
U.S. Appl. No. 14/208,626, Notice of Allowance, dated Sep. 1, 2015. cited by applicant .
U.S. Appl. No. 14/215,789, Final Office Action, dated Mar. 11, 2016. cited by applicant .
U.S. Appl. No. 14/255,934, Nonfinal Office Action, dated Jan. 15, 2015. cited by applicant .
U.S. Appl. No. 14/255,934, Nonfinal Office Action, dated Jun. 18, 2014. cited by applicant .
U.S. Appl. No. 14/255,934, Notice of Allowance, dated May 27, 2015. cited by applicant .
U.S. Appl. No. 14/269,490, Nonfinal Office Action, dated Sep. 12, 2014. cited by applicant .
U.S. Appl. No. 14/269,490, Notice of Allowance, dated Nov. 17, 2015. cited by applicant .
U.S. Appl. No. 14/339,652, Final Office Action, dated Apr. 22, 2016. cited by applicant .
U.S. Appl. No. 14/339,652, Nonfinal Office Action, dated Sep. 24, 2015. cited by applicant .
U.S. Appl. No. 14/511,712, Final Office Action, dated Jun. 25, 2015. cited by applicant .
U.S. Appl. No. 14/511,712, Notice of Allowance, dated Oct. 22, 2015. cited by applicant .
U.S. Appl. No. 14/511,712, Office Action, Dec. 26, 2014. cited by applicant .
U.S. Appl. No. 14/511,750, Nonfinal Office Action, dated Nov. 3, 2015. cited by applicant .
U.S. Appl. No. 14/511,750, Notice of Allowance, dated Mar. 4, 2016. cited by applicant .
U.S. Appl. No. 14/528,424, Final Office Action, dated Apr. 22, 2016. cited by applicant .
U.S. Appl. No. 14/528,424, Nonfinal Office Action, dated Dec. 3, 2015. cited by applicant .
U.S. Appl. No. 14/528,642, Final Office Action, dated Mar. 9, 2016. cited by applicant .
U.S. Appl. No. 14/713,184, Final Office Action, dated Jul. 15, 2016. cited by applicant .
U.S. Appl. No. 14/713,184, Nonfinal office action, dated Mar. 10, 2017. cited by applicant .
U.S. Appl. No. 14/713,184, Nonfinal Office Action, dated Feb. 1, 2016. cited by applicant .
U.S. Appl. No. 14/713,188, Final Office Action, dated May 31, 2016. cited by applicant .
U.S. Appl. No. 14/713,188, Nonfinal Office Action, dated Dec. 3, 2015. cited by applicant .
U.S. Appl. No. 14/713,188, Nonfinal Office Action, dated Feb. 24, 2017. cited by applicant .
U.S. Appl. No. 14/713,194, Final Office Action, dated Jan. 25, 2017. cited by applicant .
U.S. Appl. No. 14/713,194, Nonfinal Office Action, dated Jul. 29, 2016. cited by applicant .
U.S. Appl. No. 14/713,201, Final Office Action, dated Sep. 27, 2016. cited by applicant .
U.S. Appl. No. 14/713,201, Nonfinal Office Action, dated May 19, 2016. cited by applicant .
U.S. Appl. No. 14/713,206, Final Office Action, dated May 13, 2016. cited by applicant .
U.S. Appl. No. 14/713,206, Nonfinal Office Action, dated Feb. 13, 2017. cited by applicant .
U.S. Appl. No. 14/713,206, Nonfinal Office Action, dated Nov. 20, 2015. cited by applicant .
U.S. Appl. No. 14/713,214, Final Office Action, dated Aug. 26, 2016. cited by applicant .
U.S. Appl. No. 14/713,214, Nonfinal Office Action, dated Feb. 26, 2016. cited by applicant .
U.S. Appl. No. 14/713,217, Final Office Action, dated Jul. 22, 2016. cited by applicant .
U.S. Appl. No. 14/713,217, Nonfinal Office Action, dated Mar. 10, 2017. cited by applicant .
U.S. Appl. No. 14/713,217, Nonfinal Office Action, dated Feb. 12, 2016. cited by applicant .
U.S. Appl. No. 14/713,223, Final Office Action, dated Sep. 1, 2016. cited by applicant .
U.S. Appl. No. 14/713,223, Nonfinal Office Action, dated Feb. 26, 2016. cited by applicant .
U.S. Appl. No. 14/713,226, Final Office Action, dated May 26, 2016. cited by applicant .
U.S. Appl. No. 14/713,226, Nonfinal Office Action, dated Jan. 13, 2016. cited by applicant .
U.S. Appl. No. 14/713,226, Notice of Allowance, dated Sep. 22, 2016. cited by applicant .
U.S. Appl. No. 14/713,226, Second Notice of Allowance, dated Jan. 12, 2017. cited by applicant .
U.S. Appl. No. 14/713,230, Final Office Action, dated Mar. 22, 2016. cited by applicant .
U.S. Appl. No. 14/713,230, Nonfinal Office Action, dated Feb. 10, 2017. cited by applicant .
U.S. Appl. No. 14/713,237, Final Office Action, Sep. 9, 2016. cited by applicant .
U.S. Appl. No. 14/713,237, Nonfinal Office Action, dated Apr. 18, 2016. cited by applicant .
U.S. Appl. No. 14/713,240, Final Office Action, Sep. 12, 2016. cited by applicant .
U.S. Appl. No. 14/713,240, Nonfinal Office Action, dated Apr. 7, 2016. cited by applicant .
U.S. Appl. No. 14/713,249, Final Office Action, dated Jul. 12, 2016. cited by applicant .
U.S. Appl. No. 14/713,249, Nonfinal Office Action, dated Mar. 7, 2017. cited by applicant .
U.S. Appl. No. 14/713,249, Nonfinal Office Action, dated Jan. 20, 2016. cited by applicant .
U.S. Appl. No. 14/713,254, Final Office Action, dated Mar. 16, 2016. cited by applicant .
U.S. Appl. No. 14/713,254, Nonfinal Office Action, dated Jan. 30, 2017. cited by applicant .
U.S. Appl. No. 14/713,261, Final Office Action, dated Apr. 1, 2016. cited by applicant .
U.S. Appl. No. 14/713,261, Nonfinal Office Action, dated Feb. 23, 2017. cited by applicant .
U.S. Appl. No. 14/713,266, Final Office Action, dated Sep. 12, 2016. cited by applicant .
U.S. Appl. No. 14/713,266, Nonfinal Office Action, dated Mar. 23, 2016. cited by applicant .
U.S. Appl. No. 14/713,271, Final Office Action, dated Jun. 17, 2016. cited by applicant .
U.S. Appl. No. 14/713,271, Nonfinal Office Action, dated Feb. 28, 2017. cited by applicant .
U.S. Appl. No. 14/713,271, Nonfinal Office Action, dated Nov. 6, 2015. cited by applicant .
U.S. Appl. No. 14/718,338, Notice of Allowance, dated Nov. 2, 2015. cited by applicant .
U.S. Appl. No. 14/729,290, Notice of Allowance, dated Aug. 5, 2015. cited by applicant .
U.S. Appl. No. 14/798,769, Final Office Action, dated Mar. 14, 2017. cited by applicant .
U.S. Appl. No. 14/798,769, Nonfinal Office Action, dated Oct. 6, 2016. cited by applicant .
U.S. Appl. No. 14/857,242, Final Office Action, dated Apr. 20, 2016. cited by applicant .
U.S. Appl. No. 14/857,242, Nonfinal Office Action, dated Jan. 22, 2016. cited by applicant .
U.S. Appl. No. 14/857,242, Notice of Allowance, dated Jul. 1, 2016. cited by applicant .
U.S. Appl. No. 14/887,580, Final Office Action, dated Mar. 21, 2017. cited by applicant .
U.S. Appl. No. 14/887,580, Nonfinal Office Action, dated Apr. 7, 2016. cited by applicant .
U.S. Appl. No. 14/887,580, Nonfinal Office Action, dated Oct. 18, 2016. cited by applicant .
U.S. Appl. No. 14/934,326, filed Nov. 6, 2015, Fields et al., "Autonomous Vehicle Operating Status Assessment". cited by applicant .
U.S. Appl. No. 14/934,333, filed Nov. 6, 2015, Fields et al., "Autonomous Vehicle Control Assessment and Selection". cited by applicant .
U.S. Appl. No. 14/934,339, filed Nov. 6, 2015, Fields et al., "Autonomous Vehicle Operator Identification". cited by applicant .
U.S. Appl. No. 14/934,343, filed Nov. 6, 2015, Fields et al., "Autonomous Vehicle Operating Style and Mode Monitoring". cited by applicant .
U.S. Appl. No. 14/934,345, filed Nov. 6, 2015, Fields et al., "Autonomous Vehicle Feature Recommendations". cited by applicant .
U.S. Appl. No. 14/934,347, filed Nov. 6, 2015, Fields et al., "Autonomous Vehicle Software Version Assessment". cited by applicant .
U.S. Appl. No. 14/934,347, Nonfinal Office Action, dated Mar. 16, 2017. cited by applicant .
U.S. Appl. No. 14/934,352, filed Nov. 6, 2015, Fields et al., "Autonomous Vehicle Automatic Parking". cited by applicant .
U.S. Appl. No. 14/934,355, filed Nov. 6, 2015, Fields et al., "Autonomous Vehicle Insurance Based Upon Usage". cited by applicant .
U.S. Appl. No. 14/934,357, filed Nov. 6, 2015, Fields et al., "Autonomous Vehicle Salvage and Repair". cited by applicant .
U.S. Appl. No. 14/934,361, filed Nov. 6, 2015, Fields et al., "Autonomous Vehicle Infrastructure Communication Device". cited by applicant .
U.S. Appl. No. 14/934,371, filed Nov. 6, 2015, Fields et al., "Autonomous Vehicle Accident and Emergency Response". cited by applicant .
U.S. Appl. No. 14/934,381, filed Nov. 6, 2015, Fields et al., "Personal Insurance Policies". cited by applicant .
U.S. Appl. No. 14/934,385, filed Nov. 6, 2015, Fields et al., "Autonomous Vehicle Operating Status Assessment". cited by applicant .
U.S. Appl. No. 14/934,388, filed Nov. 6, 2015, Fields et al., "Autonomous Vehicle Control Assessment and Selection". cited by applicant .
U.S. Appl. No. 14/934,393, filed Nov. 6, 2015, Fields et al., "Autonomous Vehicle Control Assessment and Selection". cited by applicant .
U.S. Appl. No. 14/934,400, filed Nov. 6, 2015, Fields et al., "Autonomous Vehicle Control Assessment and Selection". cited by applicant .
U.S. Appl. No. 14/934,405, filed Nov. 6, 2015, Fields et al., "Autonomous Vehicle Automatic Parking". cited by applicant .
U.S. Appl. No. 14/950,492, Final Office Action, dated May 3, 2016. cited by applicant .
U.S. Appl. No. 14/950,492, Nonfinal Office Action, dated Jan. 22, 2016. cited by applicant .
U.S. Appl. No. 14/950,492, Notice of Allowance, dated Aug. 3, 2016. cited by applicant .
U.S. Appl. No. 14/951,798, Nonfinal Office Action, dated Jan. 27, 2017. cited by applicant .
U.S. Appl. No. 14/951,803, "Accident Fault Determination for Autonomous Vehicles", Konrardy et al., filed Nov. 25, 2015. cited by applicant .
U.S. Appl. No. 14/978,266, "Autonomous Feature Use Monitoring and Telematics", Konrardy et al., filed Dec. 22, 2015. cited by applicant .
U.S. Appl. No. 15/005,498, Nonfinal Office Action, dated Mar. 31, 2016. cited by applicant .
U.S. Appl. No. 15/005,498, Notice of Allowance, dated Aug. 2, 2016. cited by applicant .
U.S. Appl. No. 15/076,142, Nonfinal Office Action, dated Aug. 9, 2016. cited by applicant .
U.S. Appl. No. 15/076,142, Notice of Allowance, dated Sep. 19, 2016. cited by applicant .
U.S. Appl. No. 15/229,926, "Advanced Vehicle Operator Intelligence System", filed Aug. 5, 2016. cited by applicant .
U.S. Appl. No. 15/410,192, "Autonomous Vehicle Operation Feature Monitoring and Evaluation of Effectiveness", Konrardy et al., filed Jan. 19, 2017. cited by applicant .
U.S. Appl. No. 15/421,508, "Autonomous Vehicle Operation Feature Monitoring and Evaluation of Effectiveness", Konrardy et al., filed Feb. 1, 2017. cited by applicant .
U.S. Appl. No. 15/421,521, "Autonomous Vehicle Operation Feature Monitoring and Evaluation of Effectiveness", Konrardy et al., filed Feb. 1, 2017. cited by applicant .
U.S. Appl. No. 14/255,934, Final Office Action, dated Sep. 23, 2014. cited by applicant .
U.S. Appl. No. 14/269,490, Final Office Action, dated Jan. 23, 2015. cited by applicant .
Wiesenthal et al., "The Influence of Music on Driver Stress," Journal of Applied Social Psychology 30(8):1709-19 (2000). cited by applicant .
Zhou et al., A Simulation Model to Evaluate and Verify Functions of Autonomous Vehicle Based on Simulink, Tongji University, 12 pages (2009). cited by applicant.
This claims the benefit of U.S. Provisional Application No. 62/027,021 (filed Jul. 21, 2014); U.S. Provisional Application No. 62/040,735 (filed Aug. 22, 2014); U.S. Provisional Application No. 62/145,022 (filed Apr. 9, 2015); U.S. Provisional Application No. 62/145,024 (filed Apr. 9, 2015); U.S. Provisional Application No. 62/145,027 (filed Apr. 9, 2015); U.S. Provisional Application No. 62/145,028 (filed Apr. 9, 2015); U.S. Provisional Application No. 62/145,029 (filed Apr. 9, 2015); U.S. Provisional Application No. 62/145,145 (filed Apr. 9, 2015); U.S. Provisional Application No. 62/145,228 (filed Apr. 9, 2015); U.S. Provisional Application No. 62/145,232 (filed Apr. 9, 2015); U.S. Provisional Application No. 62/145,234 (filed Apr. 9, 2015); U.S. Provisional Application No. 62/145,032 (filed Apr. 9, 2015); and U.S. Provisional Application No. 62/145,033 (filed Apr. 9, 2015). The entirety of each of the foregoing provisional applications is incorporated by reference herein.
Additionally, the present application is related to co-pending U.S. patent application Ser. No. 14/798,741 (filed Jul. 14, 2015); co-pending U.S. patent application Ser. No. 14/798,750 (filed Jul. 14, 2015); co-pending U.S. patent application Ser. No. 14/798,745 (filed Jul. 14, 2015); co-pending U.S. patent application Ser. No. 14/798,763 (filed Jul. 14, 2015); co-pending U.S. patent application Ser. No. 14/798,609 (filed Jul. 14, 2015); co-pending U.S. patent application Ser. No. 14/798,615 (filed Jul. 14, 2015); co-pending U.S. patent application Ser. No. 14/798,626 (filed Jul. 14, 2015); co-pending U.S. patent application Ser. No. 14/798,633 (filed Jul. 14, 2015); co-pending U.S. patent application Ser. No. 14/798,769 (filed Jul. 14, 2015); and co-pending U.S. patent application Ser. No. 14/798,770 (filed Jul. 14, 2015). The entire contents of these related applications are hereby incorporated by reference in their entireties.
1. A computer-implemented method of loss mitigation, the method comprising: collecting, by one or more remote servers associated with an insurance provider, accident data associated with a vehicle accident involving a driver, the accident data including vehicle telematics data, and the driver being associated with an insurance policy issued by the insurance provider; analyzing, by the one or more remote servers, the accident data; determining, by the one or more remote servers and based upon the analysis of the accident data, a likely severity of the vehicle accident; generating, by the one or more remote servers and based upon the determined likely severity of the vehicle accident, a communication related to emergency assistance or an emergency assistance recommendation; transmitting, via wireless communication, the communication related to the emergency assistance or emergency assistance recommendation from the one or more remote servers to a mobile device associated with the driver; receiving, at the one or more remote servers, a wireless communication from the driver indicating approval or modification of the emergency assistance or emergency assistance recommendation; and notifying, via a communication sent from the one or more remote servers, a third party of requested emergency assistance in accordance with the emergency assistance or emergency assistance recommendation as approved or modified by the driver.
2. The computer-implemented method of claim 1, wherein the method further comprises: adjusting, generating or updating, at the one or more remote servers, one or more insurance-related items based upon the driver having emergency assistance functionality, the one or more insurance-related items including one or more of (i) parameters of the insurance policy; (ii) a premium; (iii) a rate; (iv) a discount; or (v) a reward.
3. The computer-implemented method of claim 2, the method further comprising transmitting information indicative of the adjusted, generated, or updated insurance-related items from the one or more remote servers to a mobile device associated with either the driver or another individual associated with the insurance policy, to be displayed on the mobile device for review, modification, or approval by the driver or other individual.
4. The computer-implemented method of claim 1, wherein collecting accident data includes collecting data associated with, or generated by, one or both of (i) one or more mobile devices; and (ii) an insured vehicle or a computer system of the insured vehicle.
5. The computer-implemented method of claim 1, wherein collecting accident data includes collecting data associated with, or generated by, one or more of (i) a vehicle other than the insured vehicle; (ii) vehicle-to-vehicle (V2V) communication; or (iii) roadside equipment or infrastructure located near a location of the vehicle accident.
6. A computer-implemented method of loss mitigation, the method comprising: collecting, by one or more remote servers associated with an insurance provider, accident data associated with a vehicle accident involving a driver, the accident data including vehicle telematics data, and the driver being associated with an insurance policy issued by the insurance provider; analyzing, by the one or more remote servers, the accident data; determining, by the one or more remote servers and based upon the analysis of the accident data, a likely severity of the vehicle accident; generating, by the one or more remote servers and based upon the determined likely severity of the vehicle accident, a communication related to emergency assistance or an emergency assistance recommendation; transmitting the communication related to the emergency assistance or emergency assistance recommendation from the one or more remote servers to a third party to facilitate a prompt and appropriate emergency responder response to the vehicle accident; notifying the driver, via a communication sent from the one or more remote servers, that emergency assistance from the third party has been requested; and receiving from the driver, at the one or more remote servers, a wireless communication indicating one or both of (i) a cancellation of the emergency assistance from the third party, and (ii) that the emergency assistance from the third party is not necessary.
7. The computer-implemented method of claim 6, wherein the method further comprises: adjusting, generating, or updating, at the one or more remote servers, one or more insurance-related items based upon the driver having emergency assistance functionality, the one or more insurance-related items including one or more of (i) parameters of the insurance policy; (ii) a premium; (iii) a rate; (iv) a discount; or (v) a reward.
8. The computer-implemented method of claim 7, the method further comprising transmitting information indicative of the adjusted, generated, or updated insurance-related items from the one or more remote servers to a mobile device associated with either the driver or another individual associated with the insurance policy, to be displayed on the mobile device for review, modification, or approval by the driver or other individual.
9. The computer-implemented method of claim 6, wherein collecting accident data includes collecting data associated with, or generated by, one or both of (i) one or more mobile devices; and (ii) an insured vehicle or a computer system of the insured vehicle.
10. The computer-implemented method of claim 9, wherein collecting accident data includes collecting data associated with, or generated by, one or more of (i) a vehicle other than the insured vehicle; (ii) vehicle-to-vehicle (V2V) communication; or (iii) roadside equipment or infrastructure located near a location of the vehicle accident.
11. A system for facilitating loss mitigation, the system comprising: one or more processors; and one or more memories storing instructions that, when executed by the one or more processors, cause the one or more processors to collect accident data associated with a vehicle accident involving a driver, the accident data including vehicle telematics data, and the driver being associated with an insurance policy issued by the insurance provider, analyze the accident data, determine, based upon the analysis of the accident data, a likely severity of the vehicle accident, generate, based upon the determined likely severity of the vehicle accident, a communication related to emergency assistance or an emergency assistance recommendation, cause the communication related to the emergency assistance or emergency assistance recommendation to be transmitted, via wireless communication, to a mobile device associated with the driver, receive a wireless communication from the driver indicating approval or modification of the emergency assistance or emergency assistance recommendation, and cause a third party to be notified of requested emergency assistance in accordance with the emergency assistance or emergency assistance recommendation as approved or modified by the driver.
12. The system of claim 11, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to: adjust, generate or update one or more insurance-related items based upon the driver having emergency assistance functionality, the one or more insurance-related items including one or more of (i) parameters of the insurance policy; (ii) a premium; (iii) a rate; (iv) a discount; or (v) a reward.
13. The system of claim 11, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to: cause information indicative of the adjusted, generated, or updated insurance-related items to be transmitted to a mobile device associated with either the driver or another individual associated with the insurance policy, to be displayed on the mobile device for review, modification, or approval by the driver or other individual.
14. The system of claim 11, wherein the accident data includes data associated with, or generated by, one or more mobile devices.
15. The system of claim 11, wherein the accident data includes data associated with, or generated by, an insured vehicle or a computer system of the insured vehicle.
16. The system of claim 11, wherein the accident data includes data associated with, or generated by, a vehicle other than the insured vehicle.
17. The system of claim 11, wherein the accident data includes data associated with, or generated by, vehicle-to-vehicle (V2V) communication.
18. The system of claim 11, wherein the accident data includes data associated with, or generated by, roadside equipment or infrastructure located near a location of the vehicle accident.
The present embodiments relate generally to telematics data and/or insurance policies. More particularly, the present embodiments relate to performing certain actions, and/or adjusting insurance policies, based upon telematics and/or other data indicative of risk or insured behavior.
At times, insurance providers are able to provide helpful information to customers who have recently been in an accident. When a customer calls a claims associate to report an accident and initiate a claim, for example, the associate may be able to offer suggestions with respect to the next steps that the customer should take. Often, however, customers do not call their insurance providers promptly after an accident, and/or it takes a significant amount of time for the associate to locate and relay useful information. Moreover, in an emergency situation (e.g., a serious car accident), a claim associate may be very limited in his or her ability to provide assistance. In such a situation, the customer may be unable to contact a claim associate and, more importantly, may be unable to contact emergency services/responders.
The present embodiments may overcome these and/or other deficiencies.
The present embodiments disclose systems and methods that may relate to the intersection of telematics and insurance. In some embodiments, for example, telematics and/or other data may be collected and used to determine a likely severity of a vehicle accident. The data may be gathered from one or more sources, such as mobile devices (e.g., smart phones, smart glasses, smart watches, smart wearable devices, smart contact lenses, and/or other devices capable of wireless communication); smart vehicles; smart vehicle or smart home mounted sensors; third party sensors or sources of data (e.g., other vehicles, public transportation systems, government entities, and/or the Internet); and/or other sources of information. Based upon the likely severity, a communication related to emergency assistance or an emergency assistance request may be generated. The communication may be sent to a driver involved in the accident (e.g., for approval, rejection or modification prior to being sent to an emergency service provider), and/or sent directly to an emergency service provider, for example.
In one aspect, a computer-implemented method of loss mitigation may include (1) collecting, by one or more remote servers associated with an insurance provider, accident data associated with a vehicle accident involving a driver. The accident data may include vehicle telematics data, and/or the driver may be associated with an insurance policy issued by the insurance provider. The method may also include (2) analyzing, by the one or more remote servers, the accident data; (3) determining, by the one or more remote servers and based upon the analysis of the accident data, a likely severity of the vehicle accident; (4) generating, by the one or more remote servers and based upon the determined likely severity of the vehicle accident, a communication related to emergency assistance or an emergency assistance recommendation; (5) transmitting, via wireless communication, the communication related to the emergency assistance or emergency assistance recommendation from the one or more remote servers to a mobile device associated with the driver; (6) receiving, at the one or more remote servers, a wireless communication from the driver indicating approval or modification of the emergency assistance or emergency assistance recommendation; and/or (7) notifying, via a communication sent from the one or more remote servers, a third party of requested emergency assistance in accordance with the emergency assistance or emergency assistance recommendation as approved or modified by the driver. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
In another aspect, a computer-implemented method of loss mitigation may include (1) collecting, by one or more remote servers associated with an insurance provider, accident data associated with a vehicle accident involving a driver. The accident data may include vehicle telematics data, and/or the driver may be associated with an insurance policy issued by the insurance provider. The method may also include (2) analyzing, by the one or more remote servers, the accident data; (3) determining, by the one or more remote servers and based upon the analysis of the accident data, a likely severity of the vehicle accident; (4) generating, by the one or more remote servers and based upon the determined likely severity of the vehicle accident, a communication related to emergency assistance or an emergency assistance recommendation; and/or (5) transmitting the communication related to the emergency assistance or emergency assistance recommendation from the one or more remote servers to a third party to facilitate a prompt and appropriate emergency responder response to the vehicle accident. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
In another aspect, a system for facilitating loss mitigation may include one or more processors and one or more memories. The one or more memories may store instructions that, when executed by the one or more processors, cause the one or more processors to (1) collect accident data associated with a vehicle accident involving a driver. The accident data may include vehicle telematics data, and/or the driver may be associated with an insurance policy issued by the insurance provider. The instructions may also cause the one or more processors to (2) analyze the accident data; (3) determine, based upon the analysis of the accident data, a likely severity of the vehicle accident; (4) generate, based upon the determined likely severity of the vehicle accident, a communication related to emergency assistance or an emergency assistance recommendation; (5) cause the communication related to the emergency assistance or emergency assistance recommendation to be transmitted, via wireless communication, to a mobile device associated with the driver; (6) receive a wireless communication from the driver indicating approval or modification of the emergency assistance or emergency assistance recommendation; and/or (7) cause a third party to be notified of requested emergency assistance in accordance with the emergency assistance or emergency assistance recommendation as approved or modified by the driver.
There are shown in the drawings arrangements which are presently discussed. It is understood, however, that the present embodiments are not limited to the precise arrangements and instrumentalities shown.
FIG. 1 illustrates an exemplary computer system on which the techniques described herein may be implemented, according to one embodiment.
FIG. 2 illustrates an exemplary mobile device or smart vehicle controller that may collect, receive, generate and/or send telematics and/or other data for purposes of the techniques described herein, according to one embodiment.
FIG. 3 illustrates an exemplary computer-implemented method of loss mitigation associated with an insured event, according to one embodiment.
FIG. 4 illustrates an exemplary computer-implemented method of providing intelligent routing to reduce risk and/or the likelihood of an insured event occurring, according to one embodiment.
FIG. 5 illustrates an exemplary computer-implemented method of theft prevention and/or mitigation, according to one embodiment.
The present embodiments may relate to, inter alia, collecting data, including telematics and/or other data, and analyzing the data (e.g., by an insurance provider server or processor) to provide insurance-related benefits to insured individuals, and/or to apply the insurance-related benefits to insurance policies or premiums of insured individuals. For example, the insurance-related benefits may include risk or loss mitigation and/or prevention, and/or may include theft protection, mitigation, and/or avoidance. The insurance-related benefits may also, or instead, include other products and/or services, such as intelligent vehicle routing in real-time, for example. The present embodiments may prevent losses/injury/damage to persons and/or property, and/or reward an insured for exhibiting risk-averse behavior (e.g., in the form of lower insurance premiums or rates, or additional insurance discounts, points, and/or rewards).
I. Exemplary Telematics Data System
FIG. 1 illustrates a block diagram of an exemplary telematics system 1 on which the exemplary methods described herein may be implemented. The high-level architecture includes both hardware and software applications, as well as various data communications channels for communicating data between the various hardware and software components. The telematics system 1 may be roughly divided into front-end components 2 and back-end components 4.
The front-end components 2 may obtain information regarding a vehicle 8 (e.g., a car, truck, motorcycle, etc.) and/or the surrounding environment. Information regarding the surrounding environment may be obtained by one or more other vehicles 6, public transportation system components 22 (e.g., a train, a bus, a trolley, a ferry, etc.), infrastructure components 26 (e.g., a bridge, a stoplight, a tunnel, a rail crossing, etc.), smart homes 28 having smart home controllers 29, and/or other components communicatively connected to a network 30. Information regarding the vehicle 8 may be obtained by a mobile device 10 (e.g., a smart phone, a tablet computer, a special purpose computing device, etc.) and/or a smart vehicle controller 14 (e.g., an on-board computer, a vehicle diagnostic system, a vehicle control system or sub-system, etc.), which may be communicatively connected to each other and/or the network 30.
In some embodiments, telematics data may be generated by and/or received from sensors 20 associated with the vehicle 8. Such telematics data from the sensors 20 may be received by the mobile device 10 and/or the smart vehicle controller 14, in some embodiments. Other, external sensors 24 (e.g., sensors associated with one or more other vehicles 6, public transportation system components 22, infrastructure components 26, and/or smart homes 28) may provide further data regarding the vehicle 8 and/or its environment, in some embodiments. For example, the external sensors 24 may obtain information pertaining to other transportation components or systems within the environment of the vehicle 8, and/or information pertaining to other aspect so of that environment. The sensors 20 and the external sensors 24 are described further below, according to some embodiments.
In some embodiments, the mobile device 10 and/or the smart vehicle controller 14 may process the sensor data from sensors 20, and/or other of the front-end components 2 may process the sensor data from external sensors 24. The processed data (and/or information derived therefrom) may then be communicated to the back-end components 4 via the network 30. In other embodiments, the front-end components 2 may communicate the raw sensor data from sensors 20 and/or external sensors 24, and/or other telematics data, to the back-end components 4 for processing. In thin-client embodiments, for example, the mobile device 10 and/or the smart vehicle controller 14 may act as a pass-through communication node for communication with the back-end components 4, with minimal or no processing performed by the mobile device 10 and/or the smart vehicle controller 14. In other embodiments, the mobile device 10 and/or the smart vehicle controller 14 may perform substantial processing of received sensor, telematics, or other data. Summary information, processed data, and/or unprocessed data may be communicated to the back-end components 4 via the network 30.
The mobile device 10 may be a general-use personal computer, cellular phone, smart phone, tablet computer, or a dedicated vehicle use monitoring device. In some embodiments, the mobile device 10 may include a wearable device such as a smart watch, smart glasses, wearable smart technology, or a pager. Although only one mobile device 10 is illustrated, it should be understood that a plurality of mobile devices may be used in some embodiments. The smart vehicle controller 14 may be a general-use on-board computer capable of performing many functions relating to vehicle operation, an on-board computer system or sub-system, or a dedicated computer for monitoring vehicle operation and/or generating telematics data. Further, the smart vehicle controller 14 may be installed by the manufacturer of the vehicle 8 or as an aftermarket modification or addition to the vehicle 8. Either or both of the mobile device 10 and the smart vehicle controller 14 may communicate with the network 30 over link 12 and link 18, respectively. Additionally, the mobile device 10 and smart vehicle controller 14 may communicate with one another directly over link 16. In some embodiments, the mobile device 10 and/or the smart vehicle controller 14 may communicate with other of the front-end components 2, such as the vehicles 6, public transit system components 22, infrastructure components 26, and/or smart homes 28, either directly or indirectly (e.g., via the network 30).
The one or more sensors 20 referenced above may be removably or fixedly disposed within (and/or on the exterior of) the vehicle 8, within the mobile device 10, and/or within the smart vehicle controller 14, for example. The sensors 20 may include any one or more of various different sensor types, such as an ignition sensor, an odometer, a system clock, a speedometer, a tachometer, an accelerometer, a gyroscope, a compass, a geolocation unit (e.g., a GPS unit), a camera and/or video camera, a distance sensor (e.g., radar, LIDAR, etc.), and/or any other sensor or component capable of generating or receiving data regarding the vehicle 8 and/or the environment in which the vehicle 8 is located.
Some of the sensors 20 (e.g., radar, LIDAR, ultrasonic, infrared, or camera units) may actively or passively scan the vehicle environment for objects (e.g., other vehicles, buildings, pedestrians, etc.), traffic control elements (e.g., lane markings, signs, signals, etc.), external conditions (e.g., weather conditions, traffic conditions, road conditions, etc.), and/or other physical characteristics of the environment. Other sensors of sensors 20 (e.g., GPS, accelerometer, or tachometer units) may provide operational and/or other data for determining the location and/or movement of the vehicle 8. Still other sensors of sensors 20 may be directed to the interior or passenger compartment of the vehicle 8, such as cameras, microphones, pressure sensors, thermometers, or similar sensors to monitor the vehicle operator and/or passengers within the vehicle 8.
The external sensors 24 may be disposed on or within other devices or components within the vehicle's environment (e.g., other vehicles 6, infrastructure components 26, etc.), and may include any of the types of sensors listed above. For example, the external sensors 24 may include sensors that are the same as or similar to sensors 20, but disposed on or within some of the vehicles 6 rather than the vehicle 8.
To send and receive information, each of the sensors 20 and/or external sensors 24 may include a transmitter and/or a receiver designed to operate according to predetermined specifications, such as the dedicated short-range communication (DSRC) channel, wireless telephony, Wi-Fi, or other existing or later-developed communications protocols. As used herein, the terms "sensor" or "sensors" may refer to the sensors 20 and/or external sensors 24.
The other vehicles 6, public transportation system components 22, infrastructure components 26, and/or smart homes 28 may be referred to herein as "external" data sources. The other vehicles 6 may include any other vehicles, including smart vehicles, vehicles with telematics-capable mobile devices, autonomous vehicles, and/or other vehicles communicatively connected to the network 30 via links 32.
The public transportation system components 22 may include bus, train, ferry, ship, airline, and/or other public transportation system components. Such components may include vehicles, tracks, switches, access points (e.g., turnstiles, entry gates, ticket counters, etc.), and/or payment locations (e.g., ticket windows, fare card vending machines, electronic payment devices operated by conductors or passengers, etc.), for example. The public transportation system components 22 may further be communicatively connected to the network 30 via a link 34, in some embodiments.
The infrastructure components 26 may include smart infrastructure or devices (e.g., sensors, transmitters, etc.) disposed within or communicatively connected to transportation or other infrastructure, such as roads, bridges, viaducts, terminals, stations, fueling stations, traffic control devices (e.g., traffic lights, toll booths, entry ramp traffic regulators, crossing gates, speed radar, cameras, etc.), bicycle docks, footpaths, or other infrastructure system components. In some embodiments, the infrastructure components 26 may be communicatively connected to the network 30 via a link (not shown in FIG. 1).
The smart homes 28 may include dwellings or other buildings that generate or collect data regarding their condition, occupancy, proximity to a mobile device 10 or vehicle 8, and/or other information. The smart homes 28 may include smart home controllers 29 that monitor the local environment of the smart home, which may include sensors (e.g., smoke detectors, radon detectors, door sensors, window sensors, motion sensors, cameras, etc.). In some embodiments, the smart home controller 29 may include or be communicatively connected to a security system controller for monitoring access and activity within the environment. The smart home 28 may further be communicatively connected to the network 30 via a link 36, in some embodiments.
The external data sources may collect data regarding the vehicle 8, a vehicle operator, a user of an insurance program, and/or an insured of an insurance policy. Additionally, or alternatively, the other vehicles 6, the public transportation system components 22, the infrastructure components 26, and/or the smart homes 28 may collect such data, and provide that data to the mobile device 10 and/or the smart vehicle controller 14 via links not shown in FIG. 1.
In some embodiments, the front-end components 2 communicate with the back-end components 4 via the network 30. The network 30 may include a proprietary network, a secure public internet, a virtual private network and/or one or more other types of networks, such as dedicated access lines, plain ordinary telephone lines, satellite links, cellular data networks, or combinations thereof. In embodiments where the network 30 comprises the Internet, data communications may take place over the network 30 via an Internet communication protocol.
The back-end components 4 may use a remote server 40 to receive data from the front-end components 2, determine characteristics of vehicle use, determine risk levels, modify insurance policies, and/or perform other processing functions in accordance with any of the methods described herein. In some embodiments, the server 40 may be associated with an insurance provider, either directly or indirectly. The server 40 may include one or more computer processors adapted and configured to execute various software applications and components of the telematics system 1.
The server 40 may further include a database 46, which may be adapted to store data related to the operation of the vehicle 8 and/or other information. As used herein, the term "database" may refer to a single database or other structured data storage, or to a collection of two or more different databases or structured data storage components. Additionally, the server 40 may be communicatively coupled via the network 30 to one or more data sources, which may include an accident database 42 and/or a third party database 44. The accident database 42 and/or third party database 44 may be communicatively connected to the network via a communication link 38. The accident database 42 and/or the third party database 44 may be operated or maintained by third parties, such as commercial vendors, governmental entities, industry associations, nonprofit organizations, or others.
The data stored in the database 46 might include, for example, dates and times of vehicle use, duration of vehicle use, speed of the vehicle 8, RPM or other tachometer readings of the vehicle 8, lateral and longitudinal acceleration of the vehicle 8, incidents or near-collisions of the vehicle 8, communications between the vehicle 8 and external sources (e.g., other vehicles 6, public transportation system components 22, infrastructure components 26, smart homes 28, and/or external information sources communicating through the network 30), environmental conditions of vehicle operation (e.g., weather, traffic, road condition, etc.), errors or failures of vehicle features, and/or other data relating to use of the vehicle 8 and/or the vehicle operator. Prior to storage in the database 46, some of the data may have been uploaded to the server 40 via the network 30 from the mobile device 10 and/or the smart vehicle controller 14. Additionally, or alternatively, some of the data may have been obtained from additional or external data sources via the network 30. Additionally, or alternatively, some of the data may have been generated by the server 40. The server 40 may store data in the database 46 and/or may access data stored in the database 46 when executing various functions and tasks associated with the methods described herein.
The server 40 may include a controller 55 that is operatively connected to the database 46 via a link 56. It should be noted that, while not shown in FIG. 1, one or more additional databases may be linked to the controller 55 in a known manner. For example, separate databases may be used for sensor data, vehicle insurance policy information, and vehicle use information. The controller 55 may include a program memory 60, a processor 62 (which may be called a microcontroller or a microprocessor), a random-access memory (RAM) 64, and an input/output (I/O) circuit 66, all of which may be interconnected via an address/data bus 65. It should be appreciated that although only one microprocessor 62 is shown, the controller 55 may include multiple microprocessors 62. Similarly, the memory of the controller 55 may include multiple RAMs 64 and multiple program memories 60. Although the I/O circuit 66 is shown as a single block, it should be appreciated that the I/O circuit 66 may include a number of different types of I/O circuits. The RAM 64 and program memories 60 may be implemented as semiconductor memories, magnetically readable memories, or optically readable memories, for example. The controller 55 may also be operatively connected to the network 30 via a link 35.
The server 40 may further include a number of software applications stored in a program memory 60. The various software applications on the server 40 may include specific programs, routines, or scripts for performing processing functions associated with the methods described herein. Additionally, or alternatively, the various software application on the server 40 may include general-purpose software applications for data processing, database management, data analysis, network communication, web server operation, or other functions described herein or typically performed by a server. The various software applications may be executed on the same computer processor or on different computer processors. Additionally, or alternatively, the software applications may interact with various hardware modules that may be installed within or connected to the server 40. Such modules may implement part of all of the various exemplary methods discussed herein or other related embodiments.
In some embodiments, the server 40 may be a remote server associated with or operated by or on behalf of an insurance provider. The server 40 may be configured to receive, collect, and/or analyze telematics and/or other data in accordance with any of the methods described herein. The server 40 may be configured for one-way or two-way wired or wireless communication via the network 30 with a number of telematics and/or other data sources, including the accident database 42, the third party database 44, the database 46 and/or the front-end components 2. For example, the server 40 may be in wireless communication with mobile device 10; insured smart vehicles 8; smart vehicles of other motorists 6; smart homes 28; present or past accident database 42; third party database 44 operated by one or more government entities and/or others; public transportation system components 22 and/or databases associated therewith; smart infrastructure components 26; and/or the Internet. The server 40 may be in wired or wireless communications with other sources of data, including those discussed elsewhere herein.
Although the telematics system 1 is shown in FIG. 1 to include one vehicle 8, one mobile device 10, one smart vehicle controller 14, one other vehicle 6, one public transportation system component 22, one infrastructure component 26, one smart home 28, and one server 40, it should be understood that different numbers of each may be utilized. For example, the system 1 may include a plurality of servers 40 and hundreds or thousands of mobile devices 10 and/or smart vehicle controllers 14, all of which may be interconnected via the network 30. Furthermore, the database storage or processing performed by the server 40 may be distributed among a plurality of servers in an arrangement known as "cloud computing." This configuration may provide various advantages, such as enabling near real-time uploads and downloads of information as well as periodic uploads and downloads of information. This may in turn support a thin-client embodiment of the mobile device 10 or smart vehicle controller 14 discussed herein.
FIG. 2 illustrates a block diagram of an exemplary mobile device 10 and/or smart vehicle controller 14. The mobile device 10 and/or smart vehicle controller 14 may include a processor 72, display 74, sensor 76, memory 78, power supply 80, wireless radio frequency transceiver 82, clock 84, microphone and/or speaker 86, and/or camera or video camera 88. In other embodiments, the mobile device and/or smart vehicle controller may include additional, fewer, and/or alternate components.
The sensor 76 may be able to record audio or visual information. If FIG. 2 corresponds to the mobile device 10, for example, the sensor 76 may be a camera integrated within the mobile device 10. The sensor 76 may alternatively be configured to sense speed, acceleration, directional, fluid, water, moisture, temperature, fire, smoke, wind, rain, snow, hail, motion, and/or other type of condition or parameter, and/or may include a gyro, compass, accelerometer, or any other type of sensor described herein (e.g., any of the sensors 20 described above in connection with FIG. 1). Generally, the sensor 76 may be any type of sensor that is currently existing or hereafter developed and is capable of providing information regarding the vehicle 8, the environment of the vehicle 8, and/or a person.
The memory 78 may include software applications that control the mobile device 10 and/or smart vehicle controller 14, and/or control the display 74 configured for accepting user input. The memory 78 may include instructions for controlling or directing the operation of vehicle equipment that may prevent, detect, and/or mitigate vehicle damage. The memory 78 may further include instructions for controlling a wireless or wired network of a smart vehicle, and/or interacting with mobile device 10 and remote server 40 (e.g., via the network 30).
The power supply 80 may be a battery or dedicated energy generator that powers the mobile device 10 and/or smart vehicle controller 14. The power supply 80 may harvest energy from the vehicle environment and be partially or completely energy self-sufficient, for example.
The transceiver 82 may be configured for wireless communication with sensors 20 located about the vehicle 8, other vehicles 6, other mobile devices similar to mobile device 10, and/or other smart vehicle controllers similar to smart vehicle controller 14. Additionally, or alternatively, the transceiver 82 may be configured for wireless communication with the server 40, which may be remotely located at an insurance provider location.
The clock 84 may be used to time-stamp the date and time that information is gathered or sensed by various sensors. For example, the clock 84 may record the time and date that photographs are taken by the camera 88, video is captured by the camera 88, and/or other data is received by the mobile device 10 and/or smart vehicle controller 14.
The microphone and speaker 86 may be configured for recognizing voice or audio input and/or commands. The clock 84 may record the time and date that various sounds are collected by the microphone and speaker 86, such as sounds of windows breaking, air bags deploying, tires skidding, conversations or voices of passengers, music within the vehicle 8, rain or wind noise, and/or other sound heard within or outside of the vehicle 8.
The present embodiments may be implemented without changes or extensions to existing communications standards. The smart vehicle controller 14 may also include a relay, node, access point, Wi-Fi AP (Access Point), local node, pico-node, relay node, and/or the mobile device 10 may be capable of RF (Radio Frequency) communication, for example. The mobile device 10 and/or smart vehicle controller 14 may include Wi-Fi, Bluetooth, GSM (Global System for Mobile communications), LTE (Long Term Evolution), CDMA (Code Division Multiple Access), UMTS (Universal Mobile Telecommunications System), and/or other types of components and functionality.
II. Telematics Data
Telematics data, as used herein, may include telematics data, and/or other types of data that have not been conventionally viewed as "telematics data." The telematics data may be generated by, and/or collected or received from, various sources. For example, the data may include, indicate, and/or relate to vehicle (and/or mobile device) speed; acceleration; braking; deceleration; turning; time; GPS (Global Positioning System) or GPS-derived location, speed, acceleration, or braking information; vehicle and/or vehicle equipment operation; external conditions (e.g., road, weather, traffic, and/or construction conditions); other vehicles or drivers in the vicinity of an accident; vehicle-to-vehicle (V2V) communications; vehicle-to-infrastructure communications; and/or image and/or audio information of the vehicle and/or insured driver before, during, and/or after an accident. The data may include other types of data, including those discussed elsewhere herein. The data may be collected via wired or wireless communication.
The data may be generated by mobile devices (smart phones, cell phones, lap tops, tablets, phablets, PDAs (Personal Digital Assistants), computers, smart watches, pagers, hand-held mobile or portable computing devices, smart glasses, smart electronic devices, wearable devices, smart contact lenses, and/or other computing devices); smart vehicles; dash or vehicle mounted systems or original telematics devices; public transportation systems; smart street signs or traffic lights; smart infrastructure, roads, or highway systems (including smart intersections, exit ramps, and/or toll booths); smart trains, buses, or planes (including those equipped with Wi-Fi or hotspot functionality); smart train or bus stations; internet sites; aerial, drone, or satellite images; third party systems or data; nodes, relays, and/or other devices capable of wireless RF (Radio Frequency) communications; and/or other devices or systems that capture image, audio, or other data and/or are configured for wired or wireless communication.
In some embodiments, the data collected may also derive from police or fire departments, hospitals, and/or emergency responder communications; police reports; municipality information; automated Freedom of Information Act requests; and/or other data collected from government agencies and officials. The data from different sources or feeds may be aggregated.
The data generated may be transmitted, via wired or wireless communication, to a remote server, such as a remote server and/or other processor(s) associated with an insurance provider. The remote server and/or associated processors may build a database of the telematics and/or other data, and/or otherwise store the data collected.
The remote server and/or associated processors may analyze the data collected and then perform certain actions and/or issue tailored communications based upon the data, including the insurance-related actions or communications discussed elsewhere herein. The automatic gathering and collecting of data from several sources by the insurance provider, such as via wired or wireless communication, may lead to expedited insurance-related activity, including the automatic identification of insured events, and/or the automatic or semi-automatic processing or adjusting of insurance claims.
In one embodiment, telematics data may be collected by a mobile device (e.g., smart phone) application. An application that collects telematics data may ask an insured for permission to collect and send data about driver behavior and/or vehicle usage to a remote server associated with an insurance provider. In return, the insurance provider may provide incentives to the insured, such as lower premiums or rates, or discounts. The application for the mobile device may be downloadable off of the internet.
III. Pre-Generated Requests for Assistance
Gathered telematics and/or other data (e.g., any type or types of telematics and/or other data described above in Section I and/or Section II) may facilitate determining the severity of (i) an accident; (ii) damage to a vehicle; and/or (iii) the injuries to the persons involved. The data gathered, such as data gathered after the accident, may facilitate determining what vehicle systems are broken or damaged, and/or are in need of minor or substantial repairs. The data gathered may indicate how much vehicle damage has occurred, and whether or not emergency services may be necessary and/or should be called or otherwise contacted.
The telematics and/or other data may also be used to (a) identify a first notice of loss, which in turn may be used to automatically start or initiate the claim handling process; and/or (b) accident reconstruction. Loss identification and/or accident reconstruction may then be paired individually and/or collectively with insurance policy data to automatically generate an insurance claim for an insured event. External data (e.g., public infrastructure or transportation system data) may also be used to determine the type and/or severity of the insured event, and the insurance claim may be modified accordingly.
A. Accident Identification
An insurance provider remote server (e.g., server 40 of FIG. 1) may promptly identify that an accident has occurred from the data gathered. Immediately after which, the remote server may automatically push a pre-generated or tailored message to the insured via wireless communication. The message may request that assistance be sent or directed to the current location of the insured or the vehicle accident. The insured may approve or modify the pre-generated message. The pre-generation of the message requesting assistance may substantially reduce an amount of time that it takes emergency responders to arrive at the scene of a serious accident in some instances. Such time savings may facilitate the saving of human lives with respect to certain vehicle accidents.
As an example, in the case of an accident, communications and/or options may be pushed to the insured's mobile device (e.g., mobile device 10 of FIG. 1). The insured or driver may be asked "Are you injured?"; "Do you need assistance or an ambulance?"; "Do you need the police sent?"; "Is the accident serious or minor?"; "How many people are injured?"; "Is anyone seriously injured?"; and/or "Is your vehicle still drivable?" via their mobile device (such as a smart phone, smart glasses, or wearable device) and/or vehicle wireless communication system.
In some embodiments, a customer or insured may control whether or not emergency responders (e.g., police, fire fighters, ambulances, tow trucks, or even insurance agents) are deployed to the scene of an accident. As suggested above, for example, a mobile device or smart phone application may ask the insured: "Have you been in an accident"; "Do you need assistance?"; "Is the accident serious?"; and/or other questions. The mobile device application may allow an insured to communicate with an insurance provider, and/or communicate directly to emergency responders, more effectively and efficiently than with conventional techniques, and/or may save time when it is of critical importance for those injured in a vehicle accident. Additionally or alternatively, the mobile device (and/or insurance provider remote server, such as remote server 40 of FIG. 1) may automatically call emergency services for the insured once (a) an accident has been detected from analysis of the telematics and/or other data collected, and/or (b) the severity of the accident has been automatically and remotely determined from the data.
B. Post-Accident Services
The mobile device application may (1) include and/or present a list of next steps that the insured should take after a vehicle accident (including instructions on how to submit an insurance claim, or automatically generate an insurance claim, for the insured event); (2) provide post-accident assistance; (3) allow for pre-selecting towing and/or auto repair service providers; and/or (4) call pre-determined persons (e.g., spouse, significant other, loved one, parents, children, friends, etc.). The mobile device application may allow the insured to customize the automatic or semi-automatic services that may be provided and/or presented to the insured when an insured event (e.g., vehicle accident) is detected from analysis of the telematics and/or other data.
The mobile device application (and/or application or functionality of a smart vehicle display or controller, such as smart vehicle controller 14 of FIG. 1) may automatically determine that a vehicle is likely no longer drivable from the data collected. After which, the mobile device application may present towing services (and ratings thereof) on a mobile device of the insured promptly and/or immediately after an accident. The insured may then pick a towing service using the mobile device (and/or smart vehicle) application. The application may then direct the mobile device and/or smart vehicle to electronically notify the towing service of a request for immediate service, such as via wireless communication.
The mobile device and/or smart vehicle application may also present options, such as whether to direct the mobile device and/or smart vehicle to call an insurance agent and/or family members. The options may allow the insured to control the communications, and/or the communications may be pre-set by the insured to automatically occur. For instance, if the telematics and/or other data gathered indicates that the insured is in a serious vehicle accident, the mobile device and/or smart vehicle application may direct the mobile device and/or smart vehicle to automatically notify the insured's spouse of the details of the accident, including severity, accident location, status of the insured or driver, and/or current location of the insured or driver (e.g., in an ambulance or at a hospital).
The mobile device and/or smart vehicle application may automatically generate an insurance claim, and/or attach associated data gathered from various sensors or systems pertinent to the insured event. The application may present the insured an option to automatically submit the automatically generated insurance claim, such as by pressing an icon or button on a user interface or display screen of a mobile device application or smart vehicle control system.
C. Application Customization
The mobile device and/or smart vehicle application may allow the insured to customize the application. The application may allow the insured to select services that are requested when an accident is detected from the data collected. The accident detection may trigger the pre-selected services being requested and/or include contacting police, an ambulance, and/or an insurance agent.
In one embodiment, the insurance provider may keep a user-customized profile of user preferences for an insured. The profile may indicate if a customer call center should proactively call the insured when collected data indicates that an accident has occurred. Also, for a serious accident, the insurance provider remote server may send a text or other message to the responsible insurance agent. The responsible insurance agent may then reach out to the insured promptly to provide individual customer service.
IV. Loss Mitigation Services
Gathered telematics and/or other data (e.g., any type or types of telematics and/or other data described above in Section I and/or Section II) may facilitate loss mitigation services. If an insured event happens, an insurance provider may be remotely notified via wireless communication and/or may identify such insured events based upon data remotely received from vehicles, mobile devices, and/or other electronic devices or systems.
The telematics and/or other data gathered may lead to triage of an auto accident. The data gathered may facilitate identification of whether the claim is minor and may be a "self-serve" type of claim. Additionally or alternatively, the data gathered may indicate that the claim is major, and may involve a fatality or a total loss claim. An application on a smart phone (e.g., mobile device 10 of FIG. 1, or on a smart vehicle controller such as smart vehicle controller 14 of FIG. 1) of the insured may automatically present options for the insured to submit a self-serve type of claim, and/or automatically or semi-automatically get the insured in contact with a representative of the insurance provider for more serious and complex claims. Moreover, any of the assistance requests discussed above in Section III may be automatically sent to the insured, to a first responder (e.g., hospital), and/or to other individuals or entities, for example (e.g., after approval or modification of the request by the insured).
The mobile device and/or smart vehicle application may allow two customers of the same insurance provider to exchange information after an accident. For instance, the applications and/or mobile devices may be equipped for Near Field Communication (NFC). The insurance customers may agree upon the facts of the accident, including who was at fault, and submit a single or joint insurance claim to the insurance provider via their mobile devices. Such submission, especially for minor accidents, may facilitate prompt and efficient handling of the insurance claim(s) by the insurance provider, and alleviate any inconvenience incurred on the part of the insured or group of insurance customers with respect to filing insurance claims and/or other paperwork.
V. Intelligent Routing and Other Recommendations
The present embodiments may facilitate generating intelligent routing and/or other recommendations, and transmitting those to an insured. Intelligent routing recommendations may be based upon vehicle location, route, and/or destination information. The intelligent routing may also be based upon historical data and/or real-time data. The historical and/or real-time data may relate to past or current accidents, weather, traffic, traffic patterns, road conditions, and/or road construction. The intelligent routing functionality, and/or usage (or percentage of usage) thereof, may be used to adjust insurance premiums or rates, and/or discounts.
The intelligent routing recommendations may provide (e.g., via wireless communication, from server 40 of FIG. 1 to mobile device 10, and/or smart vehicle controller 14, of FIG. 1) directions and/or route guidance to a driver or insured based upon traffic patterns and/or actual accident data. The intelligent routing may also take into consideration current weather, construction, traffic, and/or other current conditions.
The intelligent routing recommendations may provide real-time warnings or updates to drivers or insurance customers. Moreover, the intelligent routing recommendations may lead to collision or accident avoidance; more efficient or quicker trips; driving through less traffic or construction; better gas mileage; and/or other benefits.
For instance, short-term or minor road construction projects that may occur with little or no notice may be promptly detected by an insured or the insured's smart vehicle. The GPS location of the minor road construction project (which may be temporarily shutting down a main traffic route or otherwise slowing down traffic) may be sent from the smart vehicle of the insured to the insurance provider remote server. The remote server may then estimate routes to divert traffic around the construction project and notify other insurance customers in the area of an alternate recommended route, such as via wireless communication to their smart vehicles (e.g., vehicle 8 or smart vehicle controller 14 of FIG. 1) or mobile devices (e.g. mobile device 10 of FIG. 1).
The telematics and/or other data may be used to generate messages or alerts transmitted to a smart vehicle or mobile device. A message may indicate that the driver is entering a danger zone associated with an above average risk. For instance, the area may have a lot of ongoing construction, and/or be associated with a higher than average number of accidents.
In one embodiment, the intelligent routing may utilize vehicle-to-vehicle (V2V) communication. The V2V communication may reveal that the vehicles ahead of an insured vehicle are all braking, indicating an accident ahead. The V2V communication data may be sent directly from one vehicle to an insured vehicle (e.g., from vehicle 6 to vehicle 8 of FIG. 1), or alternatively, from one vehicle to a remote telematics or an insurance provider server (e.g., from vehicle 6 to server 40 of FIG. 1). The remote server may then send a message or warning to the insured or insured vehicle to slow down, or even exit a highway and take an alternate route. Access to the remote server may be granted via a subscription service or as a customer service provided by the insurance provider.
V2V communication may include sending a message to a smart vehicle or mobile device directing the smart vehicle or mobile device to automatically start recording telematics data. For instance, V2V communication may indicate that an accident has occurred or is likely to happen. In such situations, automatically recording telematics and/or other data may facilitate accident reconstruction and/or cause of accident determination.
B. Accident Location Reporting
In one embodiment, an insured may opt-in to a program that allows or facilitates, from telematics and/or other data, automatic vehicle accident location reporting. Reporting accident locations in real-time to an insurance provider remote server may facilitate the remote server determining intelligent routes for a group of other insurance customers presently on the road. Customers currently traveling toward the scene of the accident may be re-directed by the remote server. The intelligent routes may direct each of the other insurance customers away from, or to avoid, the scene of the accident, facilitating more efficient and safer travel.
In other words, if one insured self-reports an accident location (e.g., via automatic wireless communication indicating GPS location information), other insurance customers or drivers may be able to promptly and effectively avoid the accident scene through intelligent routing. The intelligent routing may not only consider avoidance of the accident scene, but also other driving risk conditions, such as current traffic, construction, and/or weather conditions, to determine an overall lowest risk alternate route to each vehicle's respective destination.
Telematics and/or other data gathered (e.g., any type or types of telematics and/or other data described above in Section I and/or Section II) may reveal certain trends about an insured. The data may indicate that the insured is typically driving in areas associated with an above-average number of accidents and/or high crime neighborhoods. The data may also indicate that the insured is driving over the speed limit too much and/or taking turns while driving above a recommended speed. The high risk accident areas or corners may be highlighted on a road map display, such as a vehicle navigation unit, for ease of viewing.
In response, the insurance provider remote server may push appropriate recommendations to the insured, such as recommendations to take certain corners at a slower speed and/or avoid traveling on roads, or through areas, associated with a high number of past accidents. The insurance provider remote server may also present an insurance-related benefit on a display that may be earned if the insured follows the insurance-related recommendations as a means of incentivizing lower risk driving behavior.
VI. Theft Prevention & Mitigation
A telematics device may determine that the driver of a vehicle is not the owner or an authorized driver (e.g., not someone covered under the auto insurance policy). The vehicle and/or mobile device may determine that an unknown driver is attempting or may attempt to start an insured vehicle, or is already driving the insured vehicle, by detecting that an unknown or unrecognized mobile device (e.g., smart phone) is in the vehicle.
As an example, allowed/authorized mobile device Bluetooth signatures may be detected from normal mobile device operation. However, if an unrecognized Bluetooth signal is detected, it may be determined that the vehicle has been stolen, especially if GPS information from the insured's mobile device indicates that the insured is not presently in the insured vehicle. The insured, insurance provider, and/or police may all be automatically notified of the theft.
Additionally or alternatively, a current GPS location of the insured vehicle may be displayed on a virtual map of a mobile device application, along with speed and direction information. The mobile device application with "Find My Car" functionality may be used to locate vehicles parked in large parking lots, such as a shopping mall or airport, where the insured may have forgotten where they have parked, and/or may be used to locate stolen vehicles.
The telematics and/or other data may indicate that a home is left unoccupied for a substantial length of time. For instance, it may be determined from the data collected indicates how often an insured visits and/or how much the insured spends at a second or vacation home. If an insured home is left unoccupied for a substantial amount of time, a recommendation may be sent to the insured to monitor the condition or status of the home more closely to alleviate the risk of theft and/or needed repairs being left unattended to. Insurance savings (e.g., a premium discount) may be provided to the insured in return for following the recommendations provided by the insurance provider.
VII. Exemplary Loss Mitigation Method
FIG. 3 illustrates an exemplary computer-implemented method 100 of loss mitigation associated with a vehicle accident. In some embodiments, the method 100 may be implemented in whole or in part by one or more components of the system 1 depicted in FIG. 1. For example, the method 100 may be implemented by one or more servers remote from the components (e.g., sensors, vehicles, mobile devices, etc.) sourcing telematics data, such as the server 40 (e.g., processor(s) 62 of the server 40 when executing instructions stored in the program memory 60 of the server 40) or another server not shown in FIG. 1.
The method 100 may include collecting accident data associated with a vehicle accident involving a driver (block 102). The driver may be associated with an insurance policy issued by the insurance provider (e.g., an owner of the policy, or another individual listed on the policy). The accident data may include telematics data, and possibly other data, collected from one or more sources. For example, the accident data may include data associated with or generated by one or more mobile devices (e.g., mobile device 10 of FIGS. 1 and 2); an insured vehicle or a computer system of the insured vehicle (e.g., vehicle 8 or smart vehicle controller 14 of FIGS. 1 and 2, or one or more sensors mounted on the vehicle); a vehicle other than the insured vehicle (e.g., vehicle 6 of FIG. 1); vehicle-to-vehicle (V2V) communication (e.g., communications between vehicle 8 and vehicle 6 in FIG. 1); and/or roadside equipment or infrastructure located near a location of the vehicle accident (e.g., infrastructure components 26 of FIG. 1). Generally, the accident data may include any one or more of the types of data discussed above in Section I and/or II (and/or other suitable types of data), and may be collected according to any of the techniques discussed above in Section I and/or II (and/or other suitable techniques). The accident data may have been generated by the respective source(s), and/or collected, before, during and/or after the accident.
The method 100 may also include analyzing any or all of the collected accident data (block 104), and determining a likely severity of the accident based upon the analysis (block 106). For example, it may be determined that an accident is likely severe (e.g., likely involves severe personal injury) if accelerometer data included in the accident data indicates a very large and abrupt change in speed. As another example, it may be determined that an accident is likely severe if the accident data (e.g., from a vehicle-mounted camera) shows that the accident was a head-on accident between two vehicles.
The method 100 may also include automatically communicating with the driver (e.g., the insured) (block 108). For example, a communication related to emergency assistance or an emergency assistance recommendation may be generated based upon the likely severity as determined at block 106, and then transmitted from one or more remote servers implementing the method 100 to a mobile device associated with (e.g., owned and/or carried by) the driver, such as mobile device 10 of FIG. 1. The communication may take any of various different forms, such as, for example, "Are you injured?"; "Do you need assistance or an ambulance?"; "Do you need the police sent?"; "Is the accident serious or minor?"; "How many people are injured?"; "Is anyone seriously injured?"; and/or "Is your vehicle still drivable?"
Alternative embodiments and/or scenarios corresponding to block 108 (and/or a process subsequent to block 108) are reflected in blocks 108A through 108C. For example, the driver (e.g., insured) may either accept or reject the emergency assistance indicated in the communication (block 108A), e.g., by making a selection via a user interface of the mobile device, in response to a prompt that appears in connection with the communication. Alternatively, the driver may modify the emergency assistance request or recommendation (block 108B), e.g., by indicating a different type of emergency assistance (ambulance, police, etc.). Again, the modification may be made via a user interface of the mobile device, in response to a prompt that appears in connection with the communication. As yet another alternative, an emergency assistance request may automatically be sent to a third party (e.g., police department, fire department, hospital, etc.) without waiting for any feedback from the driver (block 108C). For example, the communication at block 108 may merely notify the driver that emergency assistance has been requested, and possibly specify the type of assistance requested.
Although not shown in FIG. 3, the method 100 may also include receiving a wireless communication from the driver (e.g., from the mobile device of the driver) in response to the communication at block 108. The wireless communication may indicate whether the driver approved and/or modified (or rejected) the recommended or proposed emergency assistance, for example. In such an embodiment, if the assistance is not rejected, the method 100 may further include notifying a third party (e.g., police department, fire department, hospital, etc.) of the proposed emergency assistance, in accordance with the modifications, if any, made by the driver.
The method 100 may also include determining (e.g., based upon the analysis at block 104) fault of the driver for the accident. As seen in FIG. 3, for example, the fault for the driver (e.g., the insured) and/or for another driver may be compared or otherwise analyzed, and assigned to the appropriate party or parties (block 110). The fault may be determined as one or more binary indicators (e.g., "at fault" or "not at fault"), percentages (e.g., "25% responsible"), ratios or fractions, and/or any other suitable indicator(s) or measure(s) of fault. In some embodiments and/or scenarios, fault for a first individual is implicitly determined based upon the fault that is explicitly determined for another individual (e.g., an insured may implicitly be determined to have 0% fault if another driver is explicitly determined to be 100% at fault).
The method 100 may also include handling an insurance claim associated with the accident (block 112). For example, the fault of the driver (e.g., insured) determined at block 110 may be used to determine the appropriate payout by the insurance provider, or whether another insurance provider should be responsible for payment, etc.
The method 100 may also include adjusting, generating and/or updating one or more insurance-related items (block 114). The insurance-related item(s) may include, for example, parameters of the insurance policy (e.g., a deductible), a premium, a rate, a discount, and/or a reward. The adjustment, generation and/or update may be based upon the fault determined at block 110, or based upon the driver having the emergency assistance functionality that allows the method 100 to be performed (e.g., a mobile device application that enables the driver to receive the communication sent at block 108 and/or to send the wireless communication received at block 108), for example.
In other embodiments, the method 100 may include additional, fewer, or alternate actions as compared to those shown in FIG. 3, including any of those discussed elsewhere herein. For example, the method 100 may further include transmitting information indicative of the adjusted, generated, or updated insurance-related items to a mobile device associated with the driver (or another individual associated with the insurance policy), such as mobile device 10 of FIG. 1, to be displayed on the mobile device for review, modification, or approval by the driver or other individual.
As another example, the method 100 may further include receiving a wireless communication from the driver cancelling emergency assistance that has already been requested from a third party. As yet another example, the method 100 may include (1) generating an estimated insurance claim based upon the likely severity determined at block 106; (2) transmitting the estimated insurance claim to the driver's or insured's mobile device to facilitate presenting all or some of the claim to the driver or insured; (3) receiving a wireless communication from the driver or insured indicating approval, rejection or modification of the claim; and/or (4) handling the claim in accordance with the approval, rejection or modification. In still other example embodiments, the method 100 may omit blocks 110, 112 and/or 114.
As can be seen from the above discussion, the method 100 may enable a prompt response by the appropriate personnel (e.g., by first responders with an ambulance), and various components (e.g., in the example system 1) may complete their associated tasks relatively quickly and/or efficiently. For instance, the processor 62 of FIG. 1 may require much less time and/or far fewer processing cycles to request emergency assistance than if an insurance provider employee were to learn about the accident via other means (e.g., a phone call from the insured or passenger) and then instruct processor 62 to generate a request for help.
VIII. Additional Exemplary Loss Mitigation Methods
In one aspect, a computer-implemented method of loss mitigation may be provided. The method may include (1) collecting or receiving telematics and/or other data at or via a remote server associated with an insurance provider, the telematics and/or other data being associated with a vehicle accident involving a specific driver and/or an insured. The insured may own an insurance policy issued by the insurance provider, and the telematics and/or other data may be gathered before, during, and/or after the vehicle accident. The method may include (2) analyzing the telematics and/or other data at and/or via the remote server; (3) determining, at and/or via the remote server, a likely severity of the vehicle accident from the analysis of the telematics and/or other data; (4) generating a communication related to emergency assistance or an emergency assistance recommendation, at the remote server, based upon the likely severity of the vehicle accident that is determined from the analysis of the telematics and/or other data; (5) transmitting, via wireless communication, the communication related to the emergency assistance or emergency assistance recommendation from the remote server to a mobile device or smart vehicle associated with the specific driver and/or insured; (6) receiving, at and/or via the remote server, a wireless communication from the specific driver and/or insured indicating approval, rejection, or modification of the emergency assistance or emergency assistance recommendation; and/or (7) notifying, via communication sent from the remote server, the emergency assistance approved and/or requested by the specific driver to a third party, such as emergency responders (i.e., police or medical personnel). The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
For instance, the method may include adjusting, generating, and/or updating, at and/or via the remote server, an insurance policy, premium, rate, discount, and/or reward for the specific driver and/or the insured based upon having the emergency assistance functionality. The method may further comprise transmitting information related to the adjusted, generated, and/or updated insurance policy, premium, rate, discount, and/or reward from the remote server to a mobile device associated with the specific driver and/or insured to facilitate presenting, on a display of the mobile device, all or a portion of the adjusted, generated, and/or updated insurance policy, premium, rate, discount, and/or reward to the specific driver and/or insured for their review, modification, and/or approval. Also, the telematics and/or other data may include the types of data discussed elsewhere herein.
In another aspect, another computer-implemented method of loss mitigation may be provided. The method may include (1) collecting or receiving telematics and/or other data at or via a remote server associated with an insurance provider, the telematics and/or other data being associated with a vehicle accident involving a specific driver and/or an insured. The insured may own an insurance policy issued by the insurance provider, and the telematics and/or other data may be gathered before, during, and/or after the vehicle accident. The method may include (2) analyzing the telematics and/or other data at and/or via the remote server; (3) determining, at and/or via the remote server, a likely severity of the vehicle accident from the analysis of the telematics and/or other data; (4) generating a communication related to emergency assistance or an emergency assistance recommendation, at and/or via the remote server, based upon the likely severity of the vehicle accident that is determined from the analysis of the telematics and/or other data; and/or (5) transmitting, via wireless communication, the communication related to the emergency assistance or emergency assistance recommendation from the remote server directly to a third party, such as a police department, fire department, and/or hospital to facilitate prompt and appropriate emergency responder response to the vehicle accident.
The method may further comprise notifying the specific driver and/or insured, via wireless communication sent from the remote server, that the emergency assistance from the third party has been requested, and/or receiving from the specific driver and/or insured, at or via the remote server, a wireless communication indicating a cancellation of the emergency assistance from the third party and/or that the emergency assistance is not necessary. The method may include adjusting, generating, and/or updating, via the remote server, an insurance policy, premium, rate, discount, and/or reward for the specific driver and/or the insured based upon having the emergency assistance functionality.
The method may include transmitting information related to the adjusted, generated, and/or updated insurance policy, premium, rate, discount, and/or reward from the remote server to a mobile device associated with the specific driver and/or insured to facilitate presenting, on a display of the mobile device, all or a portion of the adjusted, generated, and/or updated insurance policy, premium, rate, discount, and/or reward to the specific driver and/or insured for their review, modification, and/or approval.
IX. Exemplary Estimated Claim Generation Method
In one aspect, a computer-implemented method of generating an insurance claim for an insured may be provided. The method may include: (1) collecting or receiving telematics and/or other data (e.g., any of the telematics and/or other data described above in Section I and/or Section II) at or via a remote server associated with an insurance provider (e.g., server 40 of FIG. 1), the telematics and/or other data being associated with a vehicle accident involving a specific driver and/or an insured, the insured owning an insurance policy issued by the insurance provider and the telematics and/or other data being gathered before, during, and/or after the vehicle accident; (2) analyzing the telematics and/or other data at or via the remote server; (3) determining, at or via the remote server, a likely severity of the vehicle accident from the analysis of the telematics and/or other data; (4) generating an estimated insurance claim, at or via the remote server, based upon the severity of the vehicle accident determined from the analysis of the telematics and/or other data; (5) transmitting, via wireless communication, the estimated insurance claim from the remote server to a mobile device associated with the specific driver and/or insured (e.g., mobile device 10 of FIG. 1) to facilitate presenting all, or a portion of, the estimated insurance claim to the specific driver and/or insured; (6) receiving, at or via the remote server, a wireless communication from the specific driver and/or insured indicating approval, rejection, or modification of the estimated insurance claim; and/or (7) handling or addressing the estimated insurance claim, at or via the remote server, in accordance with the specific driver and/or insured's approval, rejection, or modification of the estimated insurance claim. The method may further include (8) adjusting, generating, and/or updating, at or via the remote server, an insurance policy, premium, rate, discount, and/or reward for the specific driver and/or the insured (or insured vehicle) based upon the estimated insurance claim. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
X. Exemplary Intelligent Routing Method
FIG. 4 illustrates an exemplary computer-implemented method 200 of providing intelligent routing to reduce risk and/or the likelihood of an insured event from occurring. In some embodiments, the method 200 may be implemented in whole or in part by one or more components of the system 1 depicted in FIG. 1. For example, the method 200 may be implemented by one or more servers remote from the components (e.g., sensors, vehicles, mobile devices, etc.) sourcing telematics data, such as the server 40 (e.g., processor(s) 62 of the server 40 when executing instructions stored in the program memory 60 of the server 40) or another server not shown in FIG. 1.
The method 200 may include receiving trip information including a vehicle's destination, planned route, and/or current location. As seen in FIG. 4, for example, the method 200 may include collecting telematics and/or other data associated with the vehicle's location, route, and/or destination (and possibly other information, such as the vehicle's origination point) at an insurance provider remote server (block 202). The data may include GPS, navigation, and/or other data associated with, or generated by, the driver's mobile device, the driver's vehicle (or a computer system thereof), another vehicle (e.g., a vehicle in the vicinity of the driver's vehicle), V2V communication, and/or roadside equipment and/or infrastructure, for example.
The method 200 may also include analyzing the data/information collected at block 202 (block 204). In some embodiments and/or scenarios, the method 200 may include comparing/analyzing the vehicle location, route, and/or destination with real-time traffic, construction, and/or weather conditions (block 206A). The real-time traffic, construction, and/or weather conditions may be telematics data collected from other vehicles (and/or roadside equipment or infrastructure, etc.), for example. In other embodiments and/or scenarios, the method 200 may include comparing/analyzing the vehicle location, route, and/or destination with information in a database of traffic conditions, construction conditions, weather conditions, and/or past accidents (block 206B). The method 200 may include building the database using traffic, construction, weather, and/or accident information gathered from one or more sources (e.g., news feeds, telematics data, etc.), for example.
The method 200 may also include identifying a lower risk route or routes between the vehicle's current location and the destination (block 208). For example, the method 200 may include identifying areas (e.g., roads or road segments) associated with higher risk of vehicle accident using collected vehicle telematics data and/or database (e.g., traffic, construction, weather, accident, etc.) information, and the route(s) may be identified/determined at block 208 such that those high-risk areas are avoided. Alternatively, as seen in FIG. 4, the method 200 may include identifying a more fuel-efficient route from the vehicle's current location to the destination at block 208.
The method 200 may also include communicating at least one of the one or more identified lower risk routes to the driver (e.g., the insured) as a recommended route to the destination (block 210). The route may be communicated via wireless communication to a mobile device and/or a smart vehicle of the driver (e.g., to mobile device 10, and/or a vehicle navigation system of vehicle 8, of FIG. 1), for example.
The method 200 may also include determining whether the recommended route was taken by the driver based upon analysis of telematics and/or other data (block 212). For example, GPS data may be received from the driver's mobile device or smart vehicle, and used to determine whether the recommended route was followed or a different route was taken instead.
The method 200 may also include adjusting, updating, and/or generating one or more insurance-related items based upon the determination at block 212 (block 214). The insurance-related item(s) may include, for example, parameters of the insurance policy (e.g., a deductible), a premium, a rate, a discount, and/or a reward. Alternatively, or additionally, the insurance-related item(s) may be adjusted, updated, and/or generated (e.g., insurance discounts may be provided) based upon an amount of usage, by the driver or another individual associated with the same insurance policy, of the intelligent routing functionality (e.g., a number or percentage of recommended routes taken, etc.).
In other embodiments, the method 200 may include additional, fewer, or alternate actions as compared to those shown in FIG. 4, including any of those discussed elsewhere herein. For example, the method 200 may omit block 212 and/or block 214.
As can be seen from the above discussion, the method 200 may efficiently determine low-risk routes for drivers. For instance, the processor 62 of FIG. 1 may centrally determine low-risk routes for numerous different drivers in much less time than would be needed if those drivers were to instead use personal (e.g., mobile) computing devices to directly collect, and manually review, information (e.g., past or current accident information) needed to identify their own low-risk routes.
XI. Additional Exemplary Intelligent Routing Methods
In another aspect, a computer-implemented method of intelligent routing may be provided. The method may include (1) collecting telematics and/or other data and/or building a database related to multiple vehicle accidents; (2) identifying, via a processor or remote sever, areas of higher than average vehicle accidents and/or less risky travel routes or roads; (3) receiving, at or via the remote server, a destination, a planned route, and/or a current location of a vehicle, such as from telematics related data; (4) based upon the destination, planned route, or current location of the vehicle, determining, at or via the remote server, a recommended route to the destination that avoids the areas of higher than average vehicle accidents and/or reduces accident associated risk; and/or (5) transmitting the recommended route from the remote server to the insured and/or driver via wireless communication for display on the vehicle navigation system and/or a mobile device associated with the insured and/or driver to facilitate the insured and/or driver traveling via a route associated with lower risk of accident.
The method may include generating insurance discounts based upon an amount that the insured uses the intelligent routing functionality provided by an insurance provider. The telematics and/or other data may include the data indicated elsewhere herein. The method of intelligent routing may include additional, fewer, or alternative actions, including those discussed elsewhere herein.
In another aspect, another method of intelligent routing may be provided. The method may include: (1) building a database associated with road traffic, construction areas, and/or vehicle accidents; (2) receiving, at or via an insurance provider remote server, a vehicle destination and a current vehicle location associated with an insured vehicle from the insured vehicle and/or a mobile device of a driver and/or insured associated with the insured vehicle, such as from telematics related data; (3) analyzing, at or via the insurance provider remote server, the vehicle destination and the current vehicle location associated with the insured vehicle in conjunction with the database associated with the road traffic, construction areas, and/or vehicle accidents to determine a low risk recommended or alternate route to the destination; and/or (4) transmitting from the remote server, the low risk recommended or alternate route to the destination to the vehicle and/or a mobile device associated with the driver and/or insured to facilitate the driver and/or insured taking the low risk recommended or alternate route to the destination.
The method may include generating insurance discounts based upon an amount of usage (by an insured) of the intelligent routing functionality provided by an insurance provider. The telematics and/or other data may include the data indicated elsewhere herein. The method of intelligent routing may include additional, fewer, or alternative actions, including those discussed elsewhere herein.
XII. Exemplary Theft Prevention or Mitigation Method
FIG. 5 illustrates an exemplary computer-implemented method 300 of theft prevention or mitigation. In some embodiments, the method 300 may be implemented in whole or in part by one or more components of the system 1 depicted in FIG. 1. For example, the method 300 may be implemented by one or more servers remote from the components (e.g., sensors, vehicles, mobile devices, etc.) sourcing telematics data, such as the server 40 (e.g., processor(s) 62 of the server 40 when executing instructions stored in the program memory 60 of the server 40) or another server not shown in FIG. 1. While the blocks of FIG. 5 refer to a "remote server," however, it is understood that other components may implement the method 300 in other embodiments. For example, the method 300 may be implemented by a vehicle controller, such as the smart vehicle controller 14 of FIGS. 1 and 2, or another vehicle controller not shown in FIG. 1 or 2.
The method 300 may include collecting driver-related data over time (block 302). The data may be associated with one or more authorized drivers of an insured vehicle (e.g., a policy owner and one or more family members), with the driver(s) and vehicle being covered by an insurance policy issued by an insurance provider (e.g., an insurance provider associated with one or more servers implementing the method 300, in one embodiment). In particular, the collected driver-related data may be associated with identification and/or driving behavior of the driver(s). For example, the driver-related data may include data indicative of driver weights, driver appearances, acceleration, braking and/or cornering behaviors of the drivers, and so on.
The driver-related data may include telematics data, and possibly other data, collected from one or more sources. For example, the driver-related data may include data associated with or generated by one or more mobile devices (e.g., mobile device 10 of FIGS. 1 and 2); an insured vehicle or a computer system of the insured vehicle (e.g., vehicle 8 or smart vehicle controller 14 of FIGS. 1 and 2, or one or more sensors mounted on the vehicle, such as a driver's seat weight sensor, or a vehicle-mounted camera for capturing images of drivers, etc.); a vehicle other than the insured vehicle (e.g., vehicle 6 of FIG. 1); vehicle-to-vehicle (V2V) communication (e.g., communications between vehicle 8 and vehicle 6 in FIG. 1); and/or roadside equipment or infrastructure located near a location of the vehicle accident (e.g., infrastructure components 26 of FIG. 1). Generally, the driver-related data may include any one or more of the types of data discussed above in Section I and/or II (and/or other suitable types of data), and may be collected according to any of the techniques discussed above in Section I and/or II (and/or other suitable techniques).
The collected driver-related data may be analyzed (block 304). For example, the data may be analyzed in order to determine an "electronic signature" for the mobile device of each authorized driver. As another example, vehicle operation data such as acceleration, braking and cornering, and/or other data, may be analyzed to determine higher-level behaviors of a driver (e.g., how often the driver brakes suddenly, or how often and/or by how much the driver exceeds the speed limit, etc.). Data may also be analyzed to categorize the data according to driver (e.g., determine, based upon weights or other identifying data, which driving behaviors correspond to which authorized driver, etc.).
While not shown in FIG. 5, the method 300 may also include a block in which a database associated with the authorized driver(s) is built based upon the driver-related data. For example, the output data produced by the analysis at block 304 (e.g., driver-specific weights, images or facial features, driving behaviors, etc.) may be stored in the database.
The known data (e.g., stored in the database) may be compared to new data to determine that a driver is unauthorized, i.e., not one of the individuals covered by the insurance policy (block 306). While referred to here as an unauthorized "driver," the individual may be currently driving the insured vehicle, or may merely be attempting to start the vehicle or even just sitting in a seat (e.g., driver's seat) of the vehicle.
While not shown in FIG. 5, the method 300 may include a block in which current or real-time driver-related data is collected prior to making the comparison at block 306. For example, current telematics and/or other data associated with the unauthorized individual may be collected (e.g., in a manner similar to that described above in connection with block 302) in order to determine identifying characteristics and/or driving behaviors of the individual.
The comparison at block 306 may include, for example, comparing a weight of the current driver with the weights of each authorized driver (e.g., based upon data that was generated by a driver's seat weight sensor of the insured vehicle), comparing an appearance of the current driver with the appearance of each authorized driver (e.g., based upon image data captured by a vehicle-mounted camera and using suitable image processing techniques), and/or comparing electronic signatures or signals of mobile devices of the authorized drivers with an unknown electronic signature or signal of an unrecognizable mobile device associated with the unauthorized individual. Additionally or alternatively, the comparison may include comparing acceleration, braking and/or cornering behaviors or patterns of the current driver with like behaviors or patterns of each authorized driver, etc.
After determining that the current driver is unauthorized, the insured vehicle may be disabled (block 308). For example, a remote server implementing the method 300 may send a wireless signal to a vehicle controller within the insured vehicle (e.g., smart vehicle controller 14 of FIG. 1), causing the insured vehicle to gradually and slowly come to a halt (if currently moving), or preventing the insured vehicle from being started (if not yet moving), etc. In some embodiments, the disablement/prevention may only occur if an authorized driver (e.g., the policy owner) acknowledges/confirms that the person currently driving (or attempting to start, etc.) the insured vehicle does not have the permission of the policy owner and/or vehicle owner to drive the insured vehicle.
Disablement of the vehicle may also depend upon other conditions being satisfied. For example, it may first need to be verified that the unauthorized individual is sitting in a driver's seat of the insured vehicle (e.g., rather than simply being a passenger). The verification may be made by triangulation or communication techniques between the unauthorized individual's mobile device and a vehicle-mounted transmitter, and/or using a visual image of the unauthorized individual, for example.
As an alternative to block 308, the method 300 may include tracking the location of the insured vehicle (block 310). Vehicle tracking may be accomplished using GPS coordinates, for example, and may persist until the vehicle is returned to the vehicle owner. The method 300 may also include transmitting a current GPS location of the insured vehicle to a mobile device of one of the authorized drivers (e.g., the policy owner and/or vehicle owner), and/or to a third party remote server (e.g., a server associated with a police department).
In other embodiments, the method 300 may include additional, fewer, or alternate actions as compared to those shown in FIG. 5, including any of those discussed elsewhere herein. For example, instead of (or in addition to) block 308, the method 300 may include notifying one of the authorized drivers (e.g., the policy owner) and/or authorities (e.g., a server of a police department), via wired or wireless communications, that the insured vehicle was (or may be) stolen.
As can be seen from the above discussion, the method 300 may efficiently prevent vehicle theft, or efficiently mitigate the losses and/or inconveniences due to such a theft. For instance, the processor 62 of FIG. 1 may detect a likely vehicle theft far more quickly than if an insurance provider employee were to input theft reporting data to server 40 only after an insured or other individual recognized, and then called to report, the theft.
XIII. Additional Exemplary Theft Prevention or Mitigation Method
In one aspect, a computer-implemented method of vehicle theft prevention or mitigation may be provided. The method may include: (1) collecting or receiving telematics and/or other data at or via a remote server associated with an insurance provider (or at or via a vehicle controller) over time, the telematics and/or other data being associated with an insured driver or family member driving an insured vehicle (and/or their identification), the insured vehicle being covered by an insurance policy issued by the insurance provider; (2) building, at or via the remote server (or vehicle controller), a database of insured drivers or family members (i) authorized to drive the insured vehicle, and/or (ii) covered by the insurance policy; (3) collecting or receiving current telematics and/or other data at or via the remote server (or vehicle controller) associated with an individual attempting to start or currently driving the insured vehicle; (4) determining, at or via the remote server (or vehicle controller), that the individual attempting to start or currently driving the insured vehicle is not among the insured drivers or family members (i) authorized to drive the insured vehicle, or (ii) covered by the insurance policy; and/or (5) if so, then directing or controlling, at or via the remote server (or vehicle controller), a disablement of an operation of the insured vehicle (i.e., preventing the vehicle from operating, or safely or orderly slowing the down the vehicle to a halt and/or moving the vehicle off to the side of the road) and/or preventing the individual from starting or otherwise operating the insured vehicle to facilitate preventing or mitigating theft of the insured vehicle.
The determining, at or via the remote server (or vehicle controller), that the individual attempting to start, or currently driving, the insured vehicle is not among the insured drivers or family members (i) authorized to drive the insured vehicle, or (ii) covered by the insurance policy may be performed by comparing electronic signatures or signals of mobile devices of the insured drivers or family members with an unknown electronic signature or signal of a unrecognizable mobile device associated with the individual attempting to start, or currently driving, the insured vehicle, or otherwise sitting in a driver's seat of the insured vehicle. The method may include verifying, before preventing operation of the insured vehicle, that the unknown individual attempting to start, or currently driving, the insured vehicle is sitting in the driver's seat of the insured vehicle, such as via (a) triangulation or communication techniques between the unrecognizable mobile device and vehicle mounted transmitters, and/or (b) using visual images gathered or collected from the telematics and/or other data.
In one embodiment, determining, at or via the remote server (or vehicle controller), that the individual attempting to start, or currently driving, the insured vehicle is not among the insured drivers or family members (i) authorized to drive the insured vehicle, or (ii) covered by the insurance policy is performed by comparing electronic signatures or signals of various mobile devices. In another embodiment, determining, at or via the remote server (or vehicle controller), that the individual attempting to start, or currently driving, the insured vehicle is not among the insured drivers or family members (i) authorized to drive the insured vehicle, or (ii) covered by the insurance policy is performed by comparing (a) visual images (such as gathered by vehicle mounted cameras or mobile devices) or weights (such as determined from seat sensors) of the insured drivers or family members with (b) visual images or a weight of the individual attempting to start, or currently driving, the insured vehicle, respectively.
In one aspect, the telematics and/or other data may include data associated with, or generated by, mobile devices, such as smart phones, smart glasses, and/or smart wearable electronic devices capable of wireless communication. The telematics and/or other data may include data associated with, or generated by, an insured vehicle or a computer system of the insured vehicle. The telematics and/or other data may include data associated with, or generated by, (i) a vehicle other than the insured vehicle; (ii) vehicle-to-vehicle (V2V) communication; and/or (iii) road side equipment or infrastructure.
The method may further include, when it is determined, at or via the remote server (or vehicle controller), that the individual attempting to start, or currently driving, the insured vehicle is not among the insured drivers or family members (i) authorized to drive the insured vehicle, or (ii) covered by the insurance policy, generating a message (or wireless communication) and transmitting the message from the remote server (or vehicle controller) to a mobile device of one of the insured drivers or family members, or to authorities to facilitate vehicle recapture or safety. The method may include tracking the GPS location of the insured vehicle at the remote server (or vehicle controller), and/or transmitting the present GPS location of the insured vehicle to a mobile device of an insured or to a third party remote server, such as a police department. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
XIV. Additional Considerations
In addition, use of "a" or "an" is employed to describe elements and components of the embodiments herein. This is done merely for convenience and to give a general sense of the invention. This description should be read to include one or at least one and the singular also includes the plural unless it is obvious that it is meant otherwise.
Upon reading this disclosure, those of skill in the art will appreciate still additional alternative structural and functional designs through the principles disclosed herein. Thus, while particular embodiments and applications have been illustrated and described, it is to be understood that the disclosed embodiments are not limited to the precise construction and components disclosed herein. Various modifications, changes and variations, which will be apparent to those skilled in the art, may be made in the arrangement, operation and details of the methods and systems disclosed herein without departing from the spirit and scope defined in the appended claims. Finally, the patent claims at the end of this patent application are not intended to be construed under 35 U.S.C. .sctn.112(f) unless traditional means-plus-function language is expressly recited, such as "means for" or "step for" language being explicitly recited in the claim(s).
Previous Patent US 9,786,153 | Next Patent US 9,786,155