Systems and user interfaces for dynamic access of multiple remote databases and synchronization of data based on user rules Patent Grant Charyk , et al. October 25, 2 [ConsumerInfo.com, Inc.]

Systems and user interfaces for dynamic access of multiple remote databases and synchronization of data based on user rules

Charyk , et al. October 25, 2

Patent Grant 9477737

U.S. patent number 9,477,737 [Application Number 14/548,016] was granted by the patent office on 2016-10-25 for systems and user interfaces for dynamic access of multiple remote databases and synchronization of data based on user rules. This patent grant is currently assigned to CONSUMERINFO.COM, INC.. The grantee listed for this patent is ConsumerInfo.com, Inc.. Invention is credited to Mike Charyk, Nelson Yu.

United States Patent	9,477,737
Charyk , et al.	October 25, 2016

**Please see images for: ( Certificate of Correction ) **

Systems and user interfaces for dynamic access of multiple remote databases and synchronization of data based on user rules

Abstract

A computing system is configured to access a plurality of remote databases in order to identify data inconsistencies between the remote databases and provide user interfaces to a user in order to initiate communication via one or more APIs to certain remote databases indicating updates that reconcile said data inconsistencies.

Inventors:

Charyk; Mike (Huntington Beach, CA), Yu; Nelson (El Monte, CA)

Applicant:

Name	City	State	Country	Type
ConsumerInfo.com, Inc.	Costa Mesa	CA	US

Assignee:

CONSUMERINFO.COM, INC. (Costa Mesa, CA)

Family ID:

57137641

Appl. No.:

14/548,016

Filed:

November 19, 2014

Related U.S. Patent Documents


Application Number	Filing Date	Patent Number	Issue Date
61906786	Nov 20, 2013

Current U.S. Class:	1/1
Current CPC Class:	G06F 3/0482 (20130101); G06F 21/604 (20130101); G06Q 40/025 (20130101); H04L 67/306 (20130101); G06F 16/2379 (20190101); H04L 67/1095 (20130101); G06F 16/27 (20190101); H04L 63/0815 (20130101); G06F 16/951 (20190101); G06F 21/45 (20130101); Y10S 707/99943 (20130101); G06F 2221/2115 (20130101); H04L 63/08 (20130101)
Current International Class:	G06F 17/30 (20060101); G06F 21/00 (20130101); H04L 29/06 (20060101); G06F 21/62 (20130101); G06F 3/0484 (20130101); H04L 7/00 (20060101)

References Cited [Referenced By]

U.S. Patent Documents


3405457	October 1968	Bitzer
4346442	August 1982	Musmanno
4734858	March 1988	Schlafly
4755940	July 1988	Brachtl et al.
4774664	September 1988	Campbell et al.
4891503	January 1990	Jewell
4977595	December 1990	Ohta et al.
4989141	January 1991	Lyons et al.
5126936	June 1992	Champion et al.
5148365	September 1992	Dembo
5220501	June 1993	Lawlor et al.
5274547	December 1993	Zoffel et al.
5336870	August 1994	Hughes et al.
5383113	January 1995	Kight et al.
5404518	April 1995	Gilbertson et al.
5500513	March 1996	Langhans et al.
5590038	December 1996	Pitroda
5592560	January 1997	Deaton et al.
5640577	June 1997	Scharmer
5659725	August 1997	Levy et al.
5659731	August 1997	Gustafson
5719941	February 1998	Swift et al.
5729735	March 1998	Meyering
5739512	April 1998	Tognazzini
5754632	May 1998	Smith
5819234	October 1998	Slavin et al.
5832068	November 1998	Smith
5842211	November 1998	Horadan et al.
5844218	December 1998	Kawan et al.
5878403	March 1999	DeFrancesco et al.
5881131	March 1999	Farris et al.
5884302	March 1999	Ho
5903830	May 1999	Joao et al.
5903881	May 1999	Schrader et al.
5956693	September 1999	Geerlings
5963939	October 1999	McCann et al.
5966695	October 1999	Melchione et al.
5978780	November 1999	Watson
5995947	November 1999	Fraser et al.
5999596	December 1999	Walker et al.
6006333	December 1999	Nielsen
6009415	December 1999	Shurling et al.
6021397	February 2000	Jones et al.
6021943	February 2000	Chastain
6026440	February 2000	Shrader et al.
6038551	March 2000	Barlow et al.
6064990	May 2000	Goldsmith
6072894	June 2000	Payne
6073140	June 2000	Morgan et al.
6085242	July 2000	Chandra
6088686	July 2000	Walker et al.
6119103	September 2000	Basch et al.
6128602	October 2000	Northington et al.
6149441	November 2000	Pellegrino et al.
6157707	December 2000	Baulier et al.
6161139	December 2000	Win et al.
6178420	January 2001	Sassano
6182068	January 2001	Culliss
6182229	January 2001	Nielsen
6202053	March 2001	Christiansen et al.
6202067	March 2001	Blood
6233566	May 2001	Levine et al.
6247000	June 2001	Hawkins et al.
6254000	July 2001	Degen et al.
6263447	July 2001	French et al.
6282658	August 2001	French et al.
6295541	September 2001	Bodnar
6304860	October 2001	Martin et al.
6311169	October 2001	Duhon
6321339	November 2001	French et al.
6327578	December 2001	Linehan
6330551	December 2001	Burchetta et al.
6343279	January 2002	Bissonette et al.
6353778	March 2002	Brown
6356937	March 2002	Montville et al.
6374262	April 2002	Kodama
6384844	May 2002	Stewart et al.
6386444	May 2002	Sullivan
6397197	May 2002	Gindlesperger
6397212	May 2002	Biffar
6421675	July 2002	Ryan et al.
6422462	July 2002	Cohen
6453353	September 2002	Win et al.
6457012	September 2002	Jatkowski
6496936	December 2002	French et al.
6523021	February 2003	Monberg et al.
6523041	February 2003	Morgan et al.
6539377	March 2003	Culliss
6539392	March 2003	Rebane
6543683	April 2003	Hoffman
6564210	May 2003	Korda et al.
6571236	May 2003	Ruppelt
6574736	June 2003	Andrews
6581025	June 2003	Lehman
6587841	July 2003	DeFrancesco
6615193	September 2003	Kingdon et al.
6629245	September 2003	Stone et al.
6647383	November 2003	August et al.
6658393	December 2003	Basch et al.
6665715	December 2003	Houri
6678694	January 2004	Zimmermann et al.
6703930	March 2004	Skinner
6714944	March 2004	Shapiro et al.
6725381	April 2004	Smith et al.
6745938	June 2004	Sullivan
6750985	June 2004	Rhoads
6766327	July 2004	Morgan, Jr. et al.
6781608	August 2004	Crawford
6782379	August 2004	Lee
6792088	September 2004	Takeuchi
6792263	September 2004	Kite
6796497	September 2004	Benkert et al.
6804346	October 2004	Mewhinney
6805287	October 2004	Bishop et al.
6816850	November 2004	Culliss
6816871	November 2004	Lee
6845448	January 2005	Chaganti et al.
6857073	February 2005	French et al.
6871287	March 2005	Ellingson
6892307	May 2005	Wood et al.
6900731	May 2005	Kreiner et al.
6910624	June 2005	Natsuno
6928487	August 2005	Eggebraaten et al.
6934714	August 2005	Meinig
6941323	September 2005	Galperin
6947989	September 2005	Gullotta et al.
6950807	September 2005	Brock
6962336	November 2005	Glass
6965881	November 2005	Brickell et al.
6968319	November 2005	Remington et al.
6973462	December 2005	Dattero et al.
6985887	January 2006	Sunstein et al.
6988085	January 2006	Hedy
6999941	February 2006	Agarwal
7013315	March 2006	Boothby
7016907	March 2006	Boreham et al.
7028013	April 2006	Saeki
7028052	April 2006	Chapman et al.
7039607	May 2006	Watarai et al.
7043476	May 2006	Robson
7046139	May 2006	Kuhn et al.
7058386	June 2006	McGregor et al.
7058817	June 2006	Ellmore
7062475	June 2006	Szabo et al.
7069240	June 2006	Spero et al.
7072909	July 2006	Polk
7076462	July 2006	Nelson et al.
7085727	August 2006	VanOrman
7089594	August 2006	Lal et al.
7107241	September 2006	Pinto
7117172	October 2006	Black
7124144	October 2006	Christianson et al.
7155739	December 2006	Bari et al.
7181418	February 2007	Zucker et al.
7181427	February 2007	DeFrancesco
7194416	March 2007	Provost et al.
7200602	April 2007	Jonas
7209895	April 2007	Kundtz et al.
7209911	April 2007	Boothby
7218912	May 2007	Erskine et al.
7219107	May 2007	Beringer
7222369	May 2007	Vering et al.
7234156	June 2007	French et al.
7236950	June 2007	Savage et al.
7243369	July 2007	Bhat et al.
7246740	July 2007	Swift et al.
7249076	July 2007	Pendleton et al.
7249113	July 2007	Continelli et al.
7263497	August 2007	Wiser et al.
7281652	October 2007	Foss
7289971	October 2007	O'Neil et al.
7296734	November 2007	Pliha
7302272	November 2007	Ackley
7310611	December 2007	Shibuya et al.
7310617	December 2007	Cunningham
7314167	January 2008	Kiliccote
7315837	January 2008	Sloan et al.
7328233	February 2008	Salim et al.
7330717	February 2008	Gidron et al.
7330835	February 2008	Deggendorf
7333635	February 2008	Tsantes et al.
7340679	March 2008	Botscheck et al.
7343149	March 2008	Benco et al.
7343295	March 2008	Pomerance
7356516	April 2008	Richey et al.
7366694	April 2008	Lazerson
7370044	May 2008	Mulhern et al.
7373324	May 2008	Engin et al.
7383988	June 2008	Slonecker, Jr.
7386511	June 2008	Buchanan et al.
7389913	June 2008	Starrs
7395273	July 2008	Khan et al.
7403942	July 2008	Bayliss
7409369	August 2008	Homuth et al.
7412228	August 2008	Barclay et al.
7433864	October 2008	Malik
7437679	October 2008	Uemura et al.
7444518	October 2008	Dharmarajan et al.
7451095	November 2008	Bradley et al.
7451113	November 2008	Kasower
7458508	December 2008	Shao et al.
7467401	December 2008	Cicchitto
7475032	January 2009	Patnode et al.
7479949	January 2009	Jobs et al.
7480631	January 2009	Merced et al.
7490356	February 2009	Lieblich et al.
7503489	March 2009	Heffez
7509117	March 2009	Yum
7509278	March 2009	Jones
7512221	March 2009	Toms
7529698	May 2009	Joao
7530097	May 2009	Casco-Arias et al.
7536329	May 2009	Goldberg et al.
7536348	May 2009	Shao et al.
7542993	June 2009	Satterfield et al.
7543739	June 2009	Brown et al.
7546271	June 2009	Chmielewski et al.
7548886	June 2009	Kirkland et al.
7552086	June 2009	Rajasekar et al.
7552089	June 2009	Bruer et al.
7552467	June 2009	Lindsay
7559217	July 2009	Bass
7562184	July 2009	Henmi et al.
7562814	July 2009	Shao et al.
7571138	August 2009	Miri et al.
7571473	August 2009	Boydstun et al.
7575157	August 2009	Barnhardt et al.
7577665	August 2009	Ramer et al.
7577934	August 2009	Anonsen et al.
7580884	August 2009	Cook
7581112	August 2009	Brown et al.
7584126	September 2009	White
7587368	September 2009	Felsher
7593891	September 2009	Kornegay et al.
7594019	September 2009	Clapper
7610216	October 2009	May et al.
7610229	October 2009	Kornegay
7613600	November 2009	Krane
7620596	November 2009	Knudson et al.
7623844	November 2009	Herrmann et al.
7630903	December 2009	Vaidyanathan
7634737	December 2009	Beringer et al.
7640200	December 2009	Gardner et al.
7644035	January 2010	Biffle et al.
7647274	January 2010	Peterson et al.
7647344	January 2010	Skurtovich, Jr. et al.
7653592	January 2010	Flaxman et al.
7653600	January 2010	Gustin et al.
7653688	January 2010	Bittner
7672833	March 2010	Blume et al.
7685209	March 2010	Norton et al.
7686214	March 2010	Shao et al.
7688813	March 2010	Shin et al.
7689487	March 2010	Britto et al.
7689505	March 2010	Kasower
7689563	March 2010	Jacobson
7690032	March 2010	Peirce
7693787	April 2010	Provinse
7698214	April 2010	Lindgren
7698217	April 2010	Phillips et al.
7707122	April 2010	Hull et al.
7707271	April 2010	Rudkin et al.
7708190	May 2010	Brandt et al.
7711635	May 2010	Steele et al.
7711707	May 2010	Kelley
7715832	May 2010	Zhou
7720846	May 2010	Bayliss
7725385	May 2010	Royer et al.
7729959	June 2010	Wells et al.
7730078	June 2010	Schwabe et al.
7739707	June 2010	Sie et al.
7747520	June 2010	Livermore et al.
7747521	June 2010	Serio
7756789	July 2010	Welker et al.
7761373	July 2010	Metz
7761384	July 2010	Madhogarhia
7765148	July 2010	German et al.
7765166	July 2010	Beringer et al.
7769697	August 2010	Fieschi et al.
7774257	August 2010	Maggioncalda et al.
7774270	August 2010	MacCloskey
7783515	August 2010	Kumar et al.
7787869	August 2010	Rice et al.
7788040	August 2010	Haskell et al.
7792715	September 2010	Kasower
7792725	September 2010	Booraem et al.
7792903	September 2010	Fischer et al.
7793835	September 2010	Coggeshall et al.
7797252	September 2010	Rosskamm et al.
7801807	September 2010	DeFrancesco et al.
7801811	September 2010	Merrell et al.
7801956	September 2010	Cumberbatch et al.
7802104	September 2010	Dickinson et al.
7805362	September 2010	Merrell et al.
7809398	October 2010	Pearson
7809797	October 2010	Cooley et al.
7810036	October 2010	Bales et al.
7814002	October 2010	DeFrancesco et al.
7814005	October 2010	Imrey et al.
7818228	October 2010	Coulter
7818229	October 2010	Imrey et al.
7827115	November 2010	Weller et al.
7832006	November 2010	Chen et al.
7840484	November 2010	Haggerty et al.
7841004	November 2010	Balducci et al.
7841008	November 2010	Cole et al.
7844520	November 2010	Franklin
7844604	November 2010	Baio et al.
7848972	December 2010	Sharma
7848978	December 2010	Imrey et al.
7849014	December 2010	Erikson
7853493	December 2010	DeBie et al.
7856203	December 2010	Lipovski
7856386	December 2010	Hazlehurst et al.
7870066	January 2011	Lin et al.
7870078	January 2011	Clark et al.
7877304	January 2011	Coulter
7877784	January 2011	Chow et al.
7890403	February 2011	Smith
7899750	March 2011	Klieman et al.
7908242	March 2011	Achanta
7909246	March 2011	Hogg et al.
7912842	March 2011	Bayliss
7912865	March 2011	Akerman et al.
7925582	April 2011	Kornegay et al.
7925982	April 2011	Parker
7954698	June 2011	Pliha
7958046	June 2011	Doerner et al.
7966192	June 2011	Pagliari et al.
7970679	June 2011	Kasower
7975299	July 2011	Balducci et al.
7979908	July 2011	Millwee
7983932	July 2011	Kane
7987501	July 2011	Miller
8001153	August 2011	Skurtovich, Jr. et al.
8001235	August 2011	Russ et al.
8032932	October 2011	Speyer et al.
8037097	October 2011	Guo et al.
8055904	November 2011	Cato et al.
8060424	November 2011	Kasower
8060916	November 2011	Bajaj et al.
8065233	November 2011	Lee et al.
8078453	December 2011	Shaw
8078524	December 2011	Crawford et al.
8078527	December 2011	Cerise et al.
8078528	December 2011	Vicente et al.
8078881	December 2011	Liu
8095443	January 2012	DeBie
8095458	January 2012	Peterson et al.
8099309	January 2012	Bober
8099341	January 2012	Varghese
8104679	January 2012	Brown
8127982	March 2012	Casey et al.
8127986	March 2012	Taylor et al.
8131685	March 2012	Gedalius et al.
8131777	March 2012	McCullough
8160960	April 2012	Fei et al.
8175889	May 2012	Girulat et al.
8195549	June 2012	Kasower
8201257	June 2012	Andres et al.
8204812	June 2012	Stewart et al.
8224723	July 2012	Bosch et al.
8234498	July 2012	Britti et al.
8244848	August 2012	Narayanan et al.
8249968	August 2012	Oldham et al.
8271393	September 2012	Twining et al.
8281372	October 2012	Vidal
8285613	October 2012	Coulter
8285656	October 2012	Chang et al.
8290840	October 2012	Kasower
8290856	October 2012	Kasower
8296229	October 2012	Yellin et al.
8312033	November 2012	McMillan
8321339	November 2012	Imrey et al.
8327429	December 2012	Speyer et al.
8355967	January 2013	Debie et al.
8374973	February 2013	Herbrich et al.
8412593	April 2013	Song et al.
8433654	April 2013	Subbarao et al.
8456293	June 2013	Trundle et al.
8464939	June 2013	Taylor et al.
8473318	June 2013	Nielson et al.
8478674	July 2013	Kapczynski et al.
8484186	July 2013	Kapczynski et al.
8515828	August 2013	Wolf et al.
8515844	August 2013	Kasower
8527357	September 2013	Ganesan
8533118	September 2013	Weller et al.
8560436	October 2013	Ingram et al.
8560447	October 2013	Hinghole et al.
8572083	October 2013	Snell et al.
8578496	November 2013	Krishnappa
8600886	December 2013	Ramavarjula et al.
8601602	December 2013	Zheng
8606694	December 2013	Campbell et al.
8630938	January 2014	Cheng et al.
8646051	February 2014	Paden et al.
8705718	April 2014	Baniak et al.
8706599	April 2014	Koenig et al.
8725613	May 2014	Celka et al.
8738516	May 2014	Dean et al.
8768914	July 2014	Scriffignano et al.
8781953	July 2014	Kasower
8782217	July 2014	Arone et al.
8818888	August 2014	Kapczynski et al.
8856894	October 2014	Dean et al.
8930251	January 2015	DeBie
8930263	January 2015	Mahacek et al.
8938399	January 2015	Herman
8949981	February 2015	Trollope et al.
8954459	February 2015	McMillan et al.
8972400	March 2015	Kapczynski et al.
9058627	June 2015	Wasser et al.
9106691	August 2015	Burger et al.
9147042	September 2015	Haller et al.
9230283	January 2016	Taylor et al.
9256904	February 2016	Haller
2001/0029470	October 2001	Schultz et al.
2001/0029482	October 2001	Tealdi et al.
2001/0037204	November 2001	Horn et al.
2001/0037289	November 2001	Mayr et al.
2001/0039532	November 2001	Coleman, Jr. et al.
2001/0039563	November 2001	Tian
2001/0042785	November 2001	Walker et al.
2001/0044729	November 2001	Pomerance
2001/0044756	November 2001	Watkins et al.
2001/0047332	November 2001	Gonen-Friedman et al.
2001/0049274	December 2001	Degraeve
2002/0010616	January 2002	Itzhaki
2002/0013827	January 2002	Edstrom et al.
2002/0013899	January 2002	Faul
2002/0029192	March 2002	Nakagawa et al.
2002/0032635	March 2002	Harris et al.
2002/0033846	March 2002	Balasubramanian et al.
2002/0035480	March 2002	Gordon et al.
2002/0045154	April 2002	Wood et al.
2002/0052841	May 2002	Guthrie et al.
2002/0055906	May 2002	Katz et al.
2002/0059139	May 2002	Evans
2002/0059201	May 2002	Work
2002/0069122	June 2002	Yun et al.
2002/0069182	June 2002	Dwyer
2002/0072927	June 2002	Phelan et al.
2002/0077964	June 2002	Brody et al.
2002/0087460	July 2002	Hornung
2002/0099635	July 2002	Guiragosian
2002/0103933	August 2002	Garon et al.
2002/0111816	August 2002	Lortscher et al.
2002/0111890	August 2002	Sloan et al.
2002/0120757	August 2002	Sutherland et al.
2002/0120846	August 2002	Stewart et al.
2002/0128962	September 2002	Kasower
2002/0133365	September 2002	Grey et al.
2002/0133462	September 2002	Shteyn
2002/0138409	September 2002	Bass
2002/0138470	September 2002	Zhou
2002/0143943	October 2002	Lee et al.
2002/0147801	October 2002	Gullotta et al.
2002/0152166	October 2002	Dutta et al.
2002/0156676	October 2002	Ahrens et al.
2002/0161664	October 2002	Shaya et al.
2002/0169747	November 2002	Chapman et al.
2002/0173994	November 2002	Ferguson, III
2002/0194120	December 2002	Russell et al.
2002/0198800	December 2002	Shamrakov
2002/0198806	December 2002	Blagg et al.
2002/0198824	December 2002	Cook
2002/0198830	December 2002	Randell et al.
2003/0002671	January 2003	Inchalik et al.
2003/0007283	January 2003	Ostwald et al.
2003/0009415	January 2003	Lutnick et al.
2003/0009418	January 2003	Green et al.
2003/0009426	January 2003	Ruiz-Sanchez
2003/0018578	January 2003	Schultz
2003/0023531	January 2003	Fergusson
2003/0028466	February 2003	Jenson et al.
2003/0028477	February 2003	Stevenson et al.
2003/0046311	March 2003	Baidya et al.
2003/0050929	March 2003	Bookman et al.
2003/0061104	March 2003	Thomson et al.
2003/0061163	March 2003	Durfield
2003/0069839	April 2003	Whittington et al.
2003/0069943	April 2003	Bahrs et al.
2003/0097342	May 2003	Whittingtom
2003/0097380	May 2003	Mulhern et al.
2003/0105646	June 2003	Siepser
2003/0105710	June 2003	Barbara et al.
2003/0105733	June 2003	Boreham
2003/0105742	June 2003	Boreham et al.
2003/0115133	June 2003	Bian
2003/0158960	August 2003	Engberg
2003/0163435	August 2003	Payone
2003/0163513	August 2003	Schaeck et al.
2003/0163733	August 2003	Barriga-Caceres et al.
2003/0171942	September 2003	Gaito
2003/0187768	October 2003	Ryan et al.
2003/0187837	October 2003	Culliss
2003/0195859	October 2003	Lawrence
2003/0204429	October 2003	Botscheck et al.
2003/0204752	October 2003	Garrison
2003/0208412	November 2003	Hillestad et al.
2003/0220858	November 2003	Lam et al.
2003/0225742	December 2003	Tenner et al.
2003/0229580	December 2003	Gass et al.
2004/0001565	January 2004	Jones
2004/0006536	January 2004	Kawashima et al.
2004/0010458	January 2004	Friedman
2004/0015714	January 2004	Abraham et al.
2004/0015715	January 2004	Brown
2004/0019518	January 2004	Abraham et al.
2004/0019549	January 2004	Gulbrandsen
2004/0019799	January 2004	Vering et al.
2004/0024671	February 2004	Freund
2004/0024709	February 2004	Yu et al.
2004/0030574	February 2004	DiCostanzo et al.
2004/0030649	February 2004	Nelson et al.
2004/0039586	February 2004	Garvey et al.
2004/0044563	March 2004	Stein
2004/0044601	March 2004	Kim
2004/0044628	March 2004	Mathew et al.
2004/0044673	March 2004	Brady et al.
2004/0046033	March 2004	Kolodziej et al.
2004/0062213	April 2004	Koss
2004/0083159	April 2004	Crosby et al.
2004/0088237	May 2004	Moenickheim et al.
2004/0088255	May 2004	Zielke et al.
2004/0093278	May 2004	Burchetta et al.
2004/0102197	May 2004	Dietz
2004/0107250	June 2004	Marciano
2004/0110119	June 2004	Riconda et al.
2004/0111359	June 2004	Hudock
2004/0117302	June 2004	Weichert et al.
2004/0122681	June 2004	Ruvolo et al.
2004/0122696	June 2004	Beringer
2004/0122697	June 2004	Becerra et al.
2004/0128150	July 2004	Lundegren
2004/0128156	July 2004	Beringer et al.
2004/0128215	July 2004	Florance et al.
2004/0133440	July 2004	Carolan et al.
2004/0133509	July 2004	McCoy et al.
2004/0133513	July 2004	McCoy et al.
2004/0133514	July 2004	Zielke et al.
2004/0133515	July 2004	McCoy et al.
2004/0138992	July 2004	DeFrancesco et al.
2004/0138994	July 2004	DeFrancesco et al.
2004/0138997	July 2004	DeFrancesco et al.
2004/0141005	July 2004	Banatwala et al.
2004/0143546	July 2004	Wood et al.
2004/0143596	July 2004	Sirkin
2004/0158723	August 2004	Root
2004/0159700	August 2004	Khan et al.
2004/0167793	August 2004	Masuoka et al.
2004/0177035	September 2004	Silva
2004/0186807	September 2004	Nathans et al.
2004/0193538	September 2004	Raines
2004/0193891	September 2004	Ollila
2004/0199789	October 2004	Shaw et al.
2004/0210661	October 2004	Thompson
2004/0220865	November 2004	Lozowski et al.
2004/0220918	November 2004	Scriffignano et al.
2004/0225545	November 2004	Turner et al.
2004/0225609	November 2004	Greene
2004/0225643	November 2004	Alpha et al.
2004/0230527	November 2004	Hansen et al.
2004/0236688	November 2004	Bozeman
2004/0243508	December 2004	Samson et al.
2004/0243588	December 2004	Tanner et al.
2004/0249811	December 2004	Shostack
2004/0250107	December 2004	Guo
2004/0254935	December 2004	Chagoly et al.
2004/0255127	December 2004	Arnouse
2004/0267714	December 2004	Frid et al.
2005/0010513	January 2005	Duckworth et al.
2005/0015273	January 2005	Iyer
2005/0021476	January 2005	Candella et al.
2005/0021551	January 2005	Silva et al.
2005/0027632	February 2005	Zeitoun et al.
2005/0027666	February 2005	Beck et al.
2005/0027983	February 2005	Klawon
2005/0050027	March 2005	Yeh et al.
2005/0055231	March 2005	Lee
2005/0055296	March 2005	Hattersley et al.
2005/0058262	March 2005	Timmins et al.
2005/0060332	March 2005	Bernstein et al.
2005/0071328	March 2005	Lawrence
2005/0080723	April 2005	Burchetta et al.
2005/0080796	April 2005	Midgley
2005/0086126	April 2005	Patterson
2005/0091164	April 2005	Varble
2005/0097017	May 2005	Hanratty
2005/0097039	May 2005	Kulcsar et al.
2005/0097320	May 2005	Golan et al.
2005/0102180	May 2005	Gailey et al.
2005/0105719	May 2005	Hada
2005/0108396	May 2005	Bittner
2005/0108631	May 2005	Amorin et al.
2005/0114335	May 2005	Wesinger, Jr. et al.
2005/0114344	May 2005	Wesinger, Jr. et al.
2005/0114345	May 2005	Wesinger, Jr. et al.
2005/0125291	June 2005	Demkiw Grayson et al.
2005/0125397	June 2005	Gross et al.
2005/0125686	June 2005	Brandt
2005/0137899	June 2005	Davies et al.
2005/0144452	June 2005	Lynch et al.
2005/0154664	July 2005	Guy et al.
2005/0154665	July 2005	Kerr
2005/0154769	July 2005	Eckart et al.
2005/0171884	August 2005	Arnott
2005/0203768	September 2005	Florance
2005/0208461	September 2005	Krebs et al.
2005/0216434	September 2005	Haveliwala et al.
2005/0216524	September 2005	Gomes
2005/0216955	September 2005	Wilkins et al.
2005/0226224	October 2005	Lee et al.
2005/0240578	October 2005	Biederman et al.
2005/0251474	November 2005	Shinn et al.
2005/0267840	December 2005	Holm-Blagg et al.
2005/0273431	December 2005	Abel et al.
2005/0288998	December 2005	Verma et al.
2006/0004623	January 2006	Jasti
2006/0004626	January 2006	Holmen et al.
2006/0010391	January 2006	Uemura et al.
2006/0031158	February 2006	Orman
2006/0031177	February 2006	Rule
2006/0032909	February 2006	Seegar
2006/0036543	February 2006	Blagg et al.
2006/0036748	February 2006	Nusbaum et al.
2006/0041464	February 2006	Powers et al.
2006/0041670	February 2006	Musseleck et al.
2006/0059110	March 2006	Madhok et al.
2006/0059362	March 2006	Paden et al.
2006/0074986	April 2006	Mallalieu et al.
2006/0074991	April 2006	Lussier et al.
2006/0079211	April 2006	Degraeve
2006/0080230	April 2006	Freiberg
2006/0080251	April 2006	Fried et al.
2006/0080263	April 2006	Willis et al.
2006/0085334	April 2006	Murphy
2006/0085361	April 2006	Hoerle et al.
2006/0095289	May 2006	Bunning
2006/0101508	May 2006	Taylor
2006/0106670	May 2006	Cai et al.
2006/0129419	June 2006	Flaxer et al.
2006/0129481	June 2006	Bhatt et al.
2006/0129533	June 2006	Purvis
2006/0131390	June 2006	Kim
2006/0136595	June 2006	Satyavolu
2006/0155780	July 2006	Sakairi et al.
2006/0161435	July 2006	Atef et al.
2006/0161554	July 2006	Lucovsky et al.
2006/0173776	August 2006	Shalley et al.
2006/0173792	August 2006	Glass
2006/0178971	August 2006	Owen et al.
2006/0179050	August 2006	Giang et al.
2006/0184585	August 2006	Grear et al.
2006/0190394	August 2006	Fraser et al.
2006/0195351	August 2006	Bayburtian
2006/0200396	September 2006	Satterfield
2006/0200583	September 2006	Le Lann
2006/0202012	September 2006	Grano et al.
2006/0212407	September 2006	Lyon
2006/0218067	September 2006	Steele
2006/0218407	September 2006	Toms
2006/0223043	October 2006	Dancy-Edwards et al.
2006/0229943	October 2006	Mathias et al.
2006/0229961	October 2006	Lyftogt et al.
2006/0235935	October 2006	Ng
2006/0239512	October 2006	Petrillo
2006/0253358	November 2006	Delgrosso et al.
2006/0262929	November 2006	Vatanen et al.
2006/0271456	November 2006	Romain et al.
2006/0271457	November 2006	Romain et al.
2006/0271633	November 2006	Adler
2006/0277089	December 2006	Hubbard et al.
2006/0282359	December 2006	Nobili et al.
2006/0282373	December 2006	Stone
2006/0282374	December 2006	Stone
2006/0282429	December 2006	Hernandez-Sherrington et al.
2006/0282819	December 2006	Graham et al.
2006/0287764	December 2006	Kraft
2006/0287765	December 2006	Kraft
2006/0287766	December 2006	Kraft
2006/0287767	December 2006	Kraft
2006/0288090	December 2006	Kraft
2006/0293987	December 2006	Shapiro
2006/0294199	December 2006	Bertholf
2007/0005508	January 2007	Chiang
2007/0005984	January 2007	Florencio et al.
2007/0016500	January 2007	Chatterji et al.
2007/0022141	January 2007	Singleton et al.
2007/0027816	February 2007	Writer
2007/0032240	February 2007	Finnegan et al.
2007/0038568	February 2007	Greene et al.
2007/0040015	February 2007	Carlson et al.
2007/0043577	February 2007	Kasower
2007/0047714	March 2007	Baniak et al.
2007/0055621	March 2007	Tischler et al.
2007/0067297	March 2007	Kublickis
2007/0072190	March 2007	Aggarwal
2007/0073577	March 2007	Krause et al.
2007/0073889	March 2007	Morris
2007/0078908	April 2007	Rohatgi et al.
2007/0078985	April 2007	Shao et al.
2007/0083460	April 2007	Bachenheimer
2007/0083463	April 2007	Kraft
2007/0093234	April 2007	Willis et al.
2007/0094230	April 2007	Subramaniam et al.
2007/0094241	April 2007	M. Blackwell et al.
2007/0112667	May 2007	Rucker
2007/0112668	May 2007	Celano
2007/0112670	May 2007	DeFrancesco et al.
2007/0121843	May 2007	Atazky et al.
2007/0124235	May 2007	Chakraborty et al.
2007/0124256	May 2007	Crooks et al.
2007/0136109	June 2007	Yager et al.
2007/0143123	June 2007	Goldberg et al.
2007/0156554	July 2007	Nikoley et al.
2007/0156581	July 2007	Imrey et al.
2007/0156692	July 2007	Rosewarne
2007/0160458	July 2007	Yen
2007/0174186	July 2007	Hokland
2007/0174448	July 2007	Ahuja et al.
2007/0174903	July 2007	Greff
2007/0198432	August 2007	Pitroda et al.
2007/0204338	August 2007	Aiello et al.
2007/0205266	September 2007	Carr et al.
2007/0208640	September 2007	Banasiak et al.
2007/0220003	September 2007	Chern et al.
2007/0226047	September 2007	Ward
2007/0226122	September 2007	Burrell et al.
2007/0233591	October 2007	Newton
2007/0239493	October 2007	Sweetland et al.
2007/0240206	October 2007	Wu et al.
2007/0244807	October 2007	Andringa et al.
2007/0245245	October 2007	Blue et al.
2007/0250441	October 2007	Paulsen et al.
2007/0262140	November 2007	Long Sr.
2007/0266439	November 2007	Kraft
2007/0273558	November 2007	Smith
2007/0282743	December 2007	Lovelett
2007/0288355	December 2007	Roland et al.
2007/0288360	December 2007	Seeklus
2007/0294195	December 2007	Curry et al.
2007/0299770	December 2007	Delinsky
2008/0010203	January 2008	Grant
2008/0010206	January 2008	Coleman
2008/0010687	January 2008	Gonen et al.
2008/0021802	January 2008	Pendleton
2008/0027859	January 2008	Nathans et al.
2008/0028446	January 2008	Burgoyne
2008/0033956	February 2008	Saha et al.
2008/0040176	February 2008	Ehling
2008/0040610	February 2008	Fergusson
2008/0047017	February 2008	Renaud
2008/0052182	February 2008	Marshall
2008/0052244	February 2008	Tsuei et al.
2008/0059352	March 2008	Chandran
2008/0059364	March 2008	Tidwell et al.
2008/0065569	March 2008	Dutt et al.
2008/0065774	March 2008	Keeler
2008/0066188	March 2008	Kwak
2008/0071682	March 2008	Dominguez
2008/0072316	March 2008	Chang et al.
2008/0077526	March 2008	Arumugam
2008/0082536	April 2008	Schwabe et al.
2008/0083021	April 2008	Doane et al.
2008/0086400	April 2008	Ardelean et al.
2008/0086431	April 2008	Robinson et al.
2008/0091519	April 2008	Foss
2008/0091530	April 2008	Egnatios et al.
2008/0103800	May 2008	Domenikos et al.
2008/0103972	May 2008	Lanc
2008/0109422	May 2008	Dedhia
2008/0109740	May 2008	Prinsen et al.
2008/0110973	May 2008	Nathans et al.
2008/0114670	May 2008	Friesen
2008/0115226	May 2008	Welingkar et al.
2008/0120155	May 2008	Pliha
2008/0120204	May 2008	Conner et al.
2008/0120569	May 2008	Mann et al.
2008/0120716	May 2008	Hall et al.
2008/0126233	May 2008	Hogan
2008/0133278	June 2008	Stanfield
2008/0140576	June 2008	Lewis et al.
2008/0140734	June 2008	Wagner
2008/0141346	June 2008	Kay et al.
2008/0148368	June 2008	Zurko et al.
2008/0154758	June 2008	Schattmaier et al.
2008/0154766	June 2008	Lewis et al.
2008/0162317	July 2008	Banaugh et al.
2008/0162350	July 2008	Allen-Rouman et al.
2008/0162383	July 2008	Kraft
2008/0175360	July 2008	Schwarz et al.
2008/0177655	July 2008	Zalik
2008/0183480	July 2008	Carlson et al.
2008/0183585	July 2008	Vianello
2008/0195548	August 2008	Chu et al.
2008/0201257	August 2008	Lewis et al.
2008/0201401	August 2008	Pugh et al.
2008/0208735	August 2008	Balet et al.
2008/0212845	September 2008	Lund
2008/0221972	September 2008	Megdal et al.
2008/0222027	September 2008	Megdal et al.
2008/0222706	September 2008	Renaud et al.
2008/0228556	September 2008	Megdal et al.
2008/0228775	September 2008	Abhyanker et al.
2008/0229415	September 2008	Kapoor et al.
2008/0249869	October 2008	Angell et al.
2008/0255992	October 2008	Lin
2008/0270209	October 2008	Mauseth et al.
2008/0270294	October 2008	Lent et al.
2008/0270295	October 2008	Lent et al.
2008/0277465	November 2008	Pletz et al.
2008/0281737	November 2008	Fajardo
2008/0282324	November 2008	Hoal
2008/0288283	November 2008	Baldwin, Jr. et al.
2008/0288299	November 2008	Schultz
2008/0294501	November 2008	Rennich et al.
2008/0301016	December 2008	Durvasula et al.
2008/0319889	December 2008	Hammad
2009/0006230	January 2009	Lyda et al.
2009/0024484	January 2009	Walker et al.
2009/0030776	January 2009	Walker et al.
2009/0037332	February 2009	Cheung et al.
2009/0043691	February 2009	Kasower
2009/0048957	February 2009	Celano
2009/0055322	February 2009	Bykov et al.
2009/0055404	February 2009	Heiden
2009/0064297	March 2009	Selgas et al.
2009/0089190	April 2009	Girulat
2009/0089193	April 2009	Paintin
2009/0094237	April 2009	Churi et al.
2009/0100047	April 2009	Jones et al.
2009/0106141	April 2009	Becker
2009/0106150	April 2009	Pelegero et al.
2009/0106846	April 2009	Dupray et al.
2009/0119299	May 2009	Rhodes
2009/0125369	May 2009	Kloostra et al.
2009/0125972	May 2009	Hinton et al.
2009/0126013	May 2009	Atwood et al.
2009/0132347	May 2009	Anderson et al.
2009/0157564	June 2009	Cross
2009/0157693	June 2009	Palahnuk
2009/0158030	June 2009	Rasti
2009/0164380	June 2009	Brown
2009/0171723	July 2009	Jenkins
2009/0172788	July 2009	Vedula et al.
2009/0172795	July 2009	Ritari et al.
2009/0177529	July 2009	Hadi
2009/0177562	July 2009	Peace et al.
2009/0177670	July 2009	Grenier et al.
2009/0183259	July 2009	Rinek et al.
2009/0187607	July 2009	Yoo
2009/0198557	August 2009	Wang et al.
2009/0198602	August 2009	Wang et al.
2009/0199294	August 2009	Schneider
2009/0204514	August 2009	Bhogal et al.
2009/0204599	August 2009	Morris et al.
2009/0210241	August 2009	Calloway
2009/0210807	August 2009	Xiao et al.
2009/0216640	August 2009	Masi
2009/0217342	August 2009	Nadler
2009/0228918	September 2009	Rolff et al.
2009/0234665	September 2009	Conkel
2009/0234775	September 2009	Whitney et al.
2009/0234876	September 2009	Schigel et al.
2009/0240624	September 2009	James et al.
2009/0247122	October 2009	Fitzgerald et al.
2009/0248573	October 2009	Haggerty et al.
2009/0249451	October 2009	Su et al.
2009/0254375	October 2009	Martinez et al.
2009/0254476	October 2009	Sharma et al.
2009/0254656	October 2009	Vignisson et al.
2009/0254971	October 2009	Herz et al.
2009/0260064	October 2009	Mcdowell et al.
2009/0271265	October 2009	Lay et al.
2009/0276368	November 2009	Martin et al.
2009/0280467	November 2009	Ahart
2009/0289110	November 2009	Regen et al.
2009/0300066	December 2009	Guo et al.
2009/0300604	December 2009	Barringer
2009/0300641	December 2009	Friedman
2009/0307778	December 2009	Mardikar
2009/0313562	December 2009	Appleyard et al.
2009/0327054	December 2009	Yao et al.
2009/0327120	December 2009	Eze et al.
2009/0327270	December 2009	Teevan et al.
2010/0009320	January 2010	Wilkelis
2010/0009332	January 2010	Yaskin et al.
2010/0010935	January 2010	Shelton
2010/0011428	January 2010	Atwood et al.
2010/0023434	January 2010	Bond
2010/0023440	January 2010	Fraser et al.
2010/0023448	January 2010	Eze
2010/0030578	February 2010	Siddique et al.
2010/0030677	February 2010	Melik-Aslanian et al.
2010/0036697	February 2010	Kelnar
2010/0036769	February 2010	Winters
2010/0042542	February 2010	Rose et al.
2010/0043055	February 2010	Baumgart
2010/0049803	February 2010	Ogilvie et al.
2010/0063942	March 2010	Arnott et al.
2010/0063993	March 2010	Higgins et al.
2010/0077483	March 2010	Stolfo et al.
2010/0082476	April 2010	Bowman
2010/0083371	April 2010	Bennetts et al.
2010/0094768	April 2010	Miltonberger
2010/0094774	April 2010	Jackowitz et al.
2010/0094910	April 2010	Bayliss
2010/0100945	April 2010	Ozzie et al.
2010/0114724	May 2010	Ghosh et al.
2010/0114744	May 2010	Gonen
2010/0114776	May 2010	Weller et al.
2010/0122324	May 2010	Welingkar et al.
2010/0122333	May 2010	Noe et al.
2010/0130172	May 2010	Vendrow et al.
2010/0136956	June 2010	Drachev et al.
2010/0145836	June 2010	Baker et al.
2010/0153278	June 2010	Farsedakis
2010/0153290	June 2010	Duggan
2010/0161816	June 2010	Kraft et al.
2010/0169159	July 2010	Rose et al.
2010/0174813	July 2010	Hildreth et al.
2010/0179906	July 2010	Hawkes
2010/0185546	July 2010	Pollard
2010/0188684	July 2010	Kumara
2010/0205076	August 2010	Parson et al.
2010/0205662	August 2010	Ibrahim et al.
2010/0211445	August 2010	Bodington
2010/0211636	August 2010	Starkenburg et al.
2010/0217837	August 2010	Ansari et al.
2010/0223160	September 2010	Brown
2010/0223192	September 2010	Levine et al.
2010/0228658	September 2010	Ketelsen et al.
2010/0229245	September 2010	Singhal
2010/0241535	September 2010	Nightengale et al.
2010/0250338	September 2010	Banerjee et al.
2010/0250410	September 2010	Song et al.
2010/0250411	September 2010	Ogrodski
2010/0250509	September 2010	Andersen
2010/0253686	October 2010	Alsbury et al.
2010/0257102	October 2010	Perlman
2010/0257577	October 2010	Grandison et al.
2010/0258623	October 2010	Beemer et al.
2010/0262932	October 2010	Pan
2010/0268557	October 2010	Faith et al.
2010/0280914	November 2010	Carlson
2010/0281020	November 2010	Drubner
2010/0293090	November 2010	Domenikos et al.
2010/0323446	December 2010	Barnett et al.
2010/0325048	December 2010	Carlson et al.
2010/0332393	December 2010	Weller et al.
2011/0004498	January 2011	Readshaw
2011/0023115	January 2011	Wright
2011/0029388	February 2011	Kendall et al.
2011/0035452	February 2011	Gittleman
2011/0035788	February 2011	White et al.
2011/0040629	February 2011	Chiu et al.
2011/0066618	March 2011	Sigurbjornsson et al.
2011/0071950	March 2011	Ivanovic
2011/0078073	March 2011	Annappindi et al.
2011/0083181	April 2011	Nazarov
2011/0113084	May 2011	Ramnani
2011/0113086	May 2011	Long et al.
2011/0113096	May 2011	Long et al.
2011/0125924	May 2011	McAleer
2011/0126275	May 2011	Anderson et al.
2011/0131123	June 2011	Griffin et al.
2011/0137760	June 2011	Rudie et al.
2011/0137765	June 2011	Nonaka
2011/0142213	June 2011	Baniak et al.
2011/0145899	June 2011	Cao et al.
2011/0148625	June 2011	Velusamy
2011/0166988	July 2011	Coulter
2011/0167011	July 2011	Paltenghe et al.
2011/0178841	July 2011	Rane et al.
2011/0179139	July 2011	Starkenburg et al.
2011/0184780	July 2011	Alderson et al.
2011/0196791	August 2011	Dominguez
2011/0211445	September 2011	Chen
2011/0264566	October 2011	Brown
2011/0264581	October 2011	Clyne
2011/0270618	November 2011	Banerjee et al.
2011/0270754	November 2011	Kelly et al.
2011/0276396	November 2011	Rathod
2011/0307397	December 2011	Benmbarek
2011/0307434	December 2011	Rostampour et al.
2011/0307957	December 2011	Barcelo et al.
2012/0005070	January 2012	McFall et al.
2012/0011158	January 2012	Avner et al.
2012/0016948	January 2012	Sinha
2012/0022990	January 2012	Kasower
2012/0030216	February 2012	Churi et al.
2012/0030771	February 2012	Pierson et al.
2012/0047219	February 2012	Feng et al.
2012/0054088	March 2012	Edrington et al.
2012/0054592	March 2012	Jaffe et al.
2012/0060105	March 2012	Brown et al.
2012/0066106	March 2012	Papadimitriou
2012/0072382	March 2012	Pearson et al.
2012/0078932	March 2012	Skurtovich, Jr. et al.
2012/0084866	April 2012	Stolfo
2012/0089438	April 2012	Tavares et al.
2012/0101938	April 2012	Kasower
2012/0101939	April 2012	Kasower
2012/0110467	May 2012	Blake et al.
2012/0110677	May 2012	Abendroth et al.
2012/0124498	May 2012	Santoro et al.
2012/0136763	May 2012	Megdal et al.
2012/0136774	May 2012	Imrey et al.
2012/0151045	June 2012	Anakata et al.
2012/0158654	June 2012	Behren et al.
2012/0173339	July 2012	Flynt et al.
2012/0173417	July 2012	Lohman et al.
2012/0185515	July 2012	Ferrel
2012/0198556	August 2012	Patel et al.
2012/0215682	August 2012	Lent et al.
2012/0215719	August 2012	Verlander
2012/0216125	August 2012	Pierce
2012/0235897	September 2012	Hirota
2012/0239497	September 2012	Nuzzi
2012/0246060	September 2012	Conyack, Jr. et al.
2012/0253852	October 2012	Pourfallah et al.
2012/0278767	November 2012	Stibel et al.
2012/0290660	November 2012	Rao et al.
2012/0297484	November 2012	Srivastava
2012/0317014	December 2012	Cerise et al.
2012/0324388	December 2012	Rao et al.
2013/0006843	January 2013	Tralvex
2013/0018811	January 2013	Britti et al.
2013/0031109	January 2013	Routson et al.
2013/0031624	January 2013	Britti et al.
2013/0066775	March 2013	Milam
2013/0080467	March 2013	Carson et al.
2013/0085804	April 2013	Leff et al.
2013/0103571	April 2013	Chung et al.
2013/0110557	May 2013	Kasower
2013/0110565	May 2013	Means et al.
2013/0117072	May 2013	Nish
2013/0117087	May 2013	Coppinger
2013/0125010	May 2013	Strandell
2013/0132151	May 2013	Stibel et al.
2013/0173447	July 2013	Rothschild
2013/0173449	July 2013	Ng et al.
2013/0185293	July 2013	Boback
2013/0205135	August 2013	Lutz
2013/0211986	August 2013	Debie et al.
2013/0267171	October 2013	Sarkar
2013/0279676	October 2013	Baniak et al.
2013/0293363	November 2013	Plymouth
2013/0298238	November 2013	Shah et al.
2013/0332341	December 2013	Papadimitriou
2013/0332342	December 2013	Kasower
2013/0339249	December 2013	Weller et al.
2014/0012733	January 2014	Vidal
2014/0012737	January 2014	Evans
2014/0019348	January 2014	Daley
2014/0032300	January 2014	Zhang et al.
2014/0032723	January 2014	Nema
2014/0046872	February 2014	Arnott et al.
2014/0061302	March 2014	Hammad
2014/0089166	March 2014	Padawer
2014/0089167	March 2014	Kasower
2014/0089191	March 2014	Brown
2014/0096249	April 2014	Dupont et al.
2014/0110477	April 2014	Hammad
2014/0129942	May 2014	Rathod
2014/0156500	June 2014	Lassen et al.
2014/0156501	June 2014	Howe
2014/0156503	June 2014	Lassen et al.
2014/0164112	June 2014	Kala
2014/0164398	June 2014	Smith et al.
2014/0164519	June 2014	Shah
2014/0180919	June 2014	Brown
2014/0258083	September 2014	Achanta et al.
2014/0258084	September 2014	Padawer
2014/0279329	September 2014	Dancel
2014/0298485	October 2014	Gardner
2014/0317023	October 2014	Kim
2014/0379554	December 2014	Grossman
2015/0178829	June 2015	Weiss
2015/0310543	October 2015	Debie
2015/0324920	November 2015	Wilson et al.
2015/0326580	November 2015	McMillan et al.

Foreign Patent Documents


0 542 298	May 1993	EP
1 239 378	Jan 2002	EP
1 301 887	Apr 2003	EP
1 850 278	Oct 2007	EP
2 102 606	Feb 1983	GB
2005-208945	Aug 2005	JP
2000-0063313	Nov 2000	KR
2002-0039203	May 2002	KR
10-2007-0081504	Aug 2007	KR
WO 91/16691	Oct 1991	WO
WO 00/55778	Sep 2000	WO
WO 01/09752	Feb 2001	WO
WO 01/09792	Feb 2001	WO
WO 01/84281	Nov 2001	WO
WO 02/29636	Apr 2002	WO
WO 2004/031986	Apr 2004	WO
WO 2005/010683	Feb 2005	WO
WO 2005/033979	Apr 2005	WO
WO 2006/050278	May 2006	WO
WO 2006/069199	Jun 2006	WO
WO 2008/042614	Apr 2008	WO
WO 2009/064694	May 2009	WO
WO 2009/102391	Aug 2009	WO
WO 2010/001406	Jan 2010	WO
WO 2010/062537	Jun 2010	WO
WO 2010/077989	Jul 2010	WO
WO 2010/150251	Dec 2010	WO
WO 2011/005876	Jan 2011	WO

Other References

US. Appl. No. 12/705,489, filed Feb. 12, 2010, Bargoli et al. cited by applicant .
U.S. Appl. No. 12/705,511, filed Feb. 12, 2010, Bargoli et al. cited by applicant .
Actuate, "Delivering Enterprise Information for Corporate Portals", White Paper, 2004, pp. 1-7. cited by applicant .
"Aggregate and Analyze Social Media Content: Gain Faster and Broader Insight to Market Sentiment," SAP Partner, Mantis Technology Group, Apr. 2011, pp. 4. cited by applicant .
Aktas et al., "Personalizing PageRank Based on Domain Profiles", WEBKDD workshop: Webmining and Web Usage Analysis, Aug. 22, 2004, pp. 83-90. cited by applicant .
Aktas et al., "Using Hyperlink Features to Personalize Web Search", WEBKDD workshop: Webmining and Web Usage Analysis, Aug. 2004. cited by applicant .
"Arizona Company Has Found Key in Stopping ID Theft," PR Newswire, New York, Aug. 10, 2005 http://proquest.umi.com/pqdweb?did=880104711&sid=1&Fmt=3&clientId=19649&R- QT=309&Vname=PQD. cited by applicant .
ABC News Now:Money Matters, as broadcasted Nov. 15, 2005 with guest Todd Davis (CEO of Lifelock), pp. 6. cited by applicant .
Anonymous, "Credit-Report Disputes Await Electronic Resolution," Credit Card News, Chicago, Jan. 15, 1993, vol. 5, No. 19, p. 5. cited by applicant .
Anonymous, "MBNA Offers Resolution of Credit Card Disputes," Hempstead, Feb. 2002, vol. 68, No. 2, p. 47. cited by applicant .
Anonymous, "Feedback", Credit Management, ABI/INFORM Global, Sep. 2006, pp. 6. cited by applicant .
"Beware of `Who Viewed My Profile` Apps on Facebook" Tech for Luddites, Mar. 15, 2010 printed Sep. 27, 2013 http://www.techforluddites.com/2010/03/beware-of-who-viewed-my-profile-ap- ps-on-facebook.html. cited by applicant .
Bielski, Lauren, "Will you Spend to Thwart ID Theft?" ABA Banking Journal, Apr. 2005, pp. 54, 56-57, 60. cited by applicant .
BlueCava, "What We Do", http://www.bluecava.com/what-we-do/, printed Nov. 5, 2012 in 3 pages. cited by applicant .
Buxfer, http://www.buxfer.com/printed Feb. 5, 2014 in 1 page. cited by applicant .
Check, http://check.me/ printed Feb. 5, 2014 in 3 pages. cited by applicant .
Chores & Allowances, "Do Kids Have Credit Reports?" Oct. 15, 2007, http://choresandallowances.blogspot.com/2007/10/do-kids-have-credit-repor- ts.html, pp. 5. cited by applicant .
Comlounge.net, "plonesocial.auth.rpx" http://web.archive.org/web/20101026041841/http://comlounge.net/rpx as captured Oct. 26, 2010 in 9 pages. cited by applicant .
CreditKarma, http://www.creditkarma.com printed Feb. 8, 2013 in 2 pages. cited by applicant .
CreditSesame, http://www.creditsesame.com/how-it-works/our-technology/ printed Feb. 5, 2013 in 2 pages. cited by applicant .
Collins, Michael J., "Exploring the Design of Financial Counseling for Mortgage Borrowers in Default," Journal of Family and Economic Issues, Springer Science+Business Media, Mar. 13, 2007, pp. 207-226. cited by applicant .
"Consumers Gain Immediate and Full Access to Credit Score Used by Majority of U.S. Lenders", PR Newswire, ProQuest Copy, Mar. 19, 2001, p. 1. cited by applicant .
"CreditCheck Monitoring Services," Dec. 11, 2000, pp. 1, lines 21-23. cited by applicant .
"Credit Improvement", CreditRepair.com, Mar. 10, 2010, http://web.archive.org/web/20100310134914/http://www.creditrepair.com/cre- dit/, as archived Mar. 10, 2010 in 2 pages. cited by applicant .
Credit Plus, Inc., "Score Wizard", http://web.archive.org/web/20030806080310/www.creditplus.com/scorewizard.- asp, as archived Aug. 6, 2003 in 1 page. cited by applicant .
Cullen, Terri; "The Wall Street Journal Complete Identity Theft Guidebook:How to Protect Yourself from the Most Pervasive Crime in America"; Chapter 3, pp. 59-79; Jul. 10, 2007. cited by applicant .
"D&B Corporate Family Linkage", D&B Internet Access for U.S. Contract Customers, https://www.dnb.com/ecomp/help/linkage.htm as printed Dec. 17, 2009, pp. 1. cited by applicant .
"Data Loss Prevention (DLP) Software", http://www.symantec.com/data-loss-prevention/ printed Apr. 8, 2013 in 8 pages. cited by applicant .
"Data Protection", http://compliantprocessing.com/data-protection/ printed Apr. 8, 2013 in 4 pages. cited by applicant .
Day, Jo and Kevin; "ID-ology: A Planner's Guide to Identity Theft"; Journal of Financial Planning:Tech Talk; pp. 36-38; Sep. 2004. cited by applicant .
"Debt Settlement: Watch Video on how to Pay Your Debt Faster", http://www.debtconsolidationcare.com/debt-settlement.html printed Jan. 9, 2013 in 6 pages. cited by applicant .
Demby, Elayne, "Special Report: Letting Consumers Know the Score--and More", Collections and Credit Risk, New York, Feb. 2003, vol. 8, Issue 2, p. 53, pp. 3. cited by applicant .
Elliehausen et al., The Impact of Credit Counseling on Subsequent Borrower Behavior, The Journal of Consumer Affairs, Summer 2007, vol. 41, No. 1, pp. 1-28. cited by applicant .
Equifax Consumer Credit Report http://www.equifax.com/home/, as retrieved on Sep. 17, 2008. cited by applicant .
Equifax; "Equifax Credit Watch"; https://www.econsumer.equifax.co.uk/consumer/uk/sitepage.ehtml, dated Jun. 27, 2007 on www.archive.org. cited by applicant .
"Equifax: Debt Wise.TM. Credit Monitoring Service," Product Review, http://www.mdmproofing.com/iym/reviews/equifax/debt-wise/, Jan. 2010, pp. 11. cited by applicant .
Equifax; "Places", http://web.archive.org/web/20111111113930/http://www.equifax.com/places as archived Nov. 11, 2011 in 1 page. cited by applicant .
Equifax; "Places", http://www.equifax.com/places/ as printed Nov. 16, 2015 in 1 page. cited by applicant .
Equifax; "Welcome to Equifax Mobile", http://www.equifax.com/mobile/ as printed Mar. 18, 2011 in 2 pages. cited by applicant .
Ettorre, "Paul Kahn on Exceptional Marketing," Management Review, vol. 83, No. 11, Nov. 1994, pp. 48-51. cited by applicant .
Experian Consumer Credit Report http://www.experian.com/, as retrieved on Sep. 17, 2008. cited by applicant .
Facebook, "Facebook helps you connect and share with the people in your life," www.facebook.com printed Nov. 16, 2010 in 1 page. cited by applicant .
FamilySecure.com, "Frequently Asked Questions", http://www.familysecure.com/FAQ.aspx asarchived Jul. 15, 2007 in 3 pages. cited by applicant .
FamilySecure.com; "Identity Theft Protection for the Whole Family | FamilySecure.com" http://www.familysecure.com/, as retrieved on Nov. 5, 2009. cited by applicant .
Fenner, Peter, "Mobil Address Management and Billing for Personal Communications", 1st International Conference on Universal Personal Communications, 1992, ICUPC '92 Proceedings, pp. 253-257. cited by applicant .
"Fictitious Business Name Records", Westlaw Database Directory, http://directoy.westlaw.com/scope/default.asp?db=FBN-ALL&RS-W&VR=2.0 as printed Dec. 17, 2009, pp. 5. cited by applicant .
Fitzpatrick, Alex, "Facebook Monitors Your Chats for Criminal Activity [Report]," Mashable, Jul. 12, 2012 printed Sep. 27, 2013 http://mashable.com/2012/07/12/facebook-scanning-chats/. cited by applicant .
"Fund Manager," Portfolio Management Software website, indexed into Google on Jan. 7, 2005, Retrieved Oct. 24, 2014 http://www.fundmanagersoftware.com/, http://www.fundmanagersoftware.com/help/gph.sub.--tp.sub.--pieasset.html, http://www.fundmanagersoftware.com/demo2.html. cited by applicant .
Gibbs, Adrienne; "Protecting Your Children from Identity Theft," Nov. 25, 2008, http://www.creditcards.com/credit-card-news/identity-ID-theft-and-k- ids-children-1282.php, pp. 4. cited by applicant .
"GLBA Compliance and FFIEC Compliance" http://www.trustwave.com/financial-services.php printed Apr. 8, 2013 in 1 page. cited by applicant .
Gordon et al., "Identity Fraud: A Critical National and Global Threat," LexisNexis, Oct. 28, 2003, pp. 1-48. cited by applicant .
"Guide to Benefits, MasterCard.RTM. Cardholder Smart Shopper Benefits", May 2005, pp. 10. cited by applicant .
Herzberg, Amir, "Payments and Banking with Mobile Personal Devices," Communications of the ACM, May 2003, vol. 46, No. 5, pp. 53-58. cited by applicant .
Hoofnagle, Chris Jay, "Identity Theft: Making the Known Unknowns Known," Harvard Journal of Law & Technology, Fall 2007, vol. 21, No. 1, pp. 98-122. cited by applicant .
Hunt, Robert M.; Whither Consumer Credit Counseling? Business Review, Dec. 31, 2005, pp. 9-20. cited by applicant .
ID Analytics, "ID Analytics.RTM. Consumer Notification Service" printed Apr. 16, 2013 in 2 pages. cited by applicant .
ID Theft Assist, "Do You Know Where Your Child's Credit Is?", Nov. 26, 2007, http://www.idtheftassist.com/pages/story14, pp. 3. cited by applicant .
"ID Thieves These Days Want Your Number, Not Your Name", The Colombus Dispatch, Columbus, Ohio, http://www.dispatch.com/content/stories/business/2014/08/03/id-thieves-th- ese-days-want-your-number-not-your-name.html, Aug. 3, 2014 in 2 pages. cited by applicant .
Identity Theft Resource Center; Fact Sheet 120 A--To Order a Credit Report for a Child; Fact Sheets, Victim Resources; Apr. 30, 2007. cited by applicant .
"Identity Thieves Beware: Lifelock Introduces Nation's First Guaranteed Proactive Solution to Identity Theft Protection," PR Newswire, New York, Jun. 13, 2005 http://proquest.umi.com/pqdweb?did=852869731&sid=1&Fmt=3&clientId=19649&R- QT=309&Vname=PQD. cited by applicant .
IDEON, Credit-Card Registry that Bellyflopped this Year, Is Drawing some Bottom-Fishers, The Wall Street Journal, Aug. 21, 1995, pp. C2. cited by applicant .
Information Brokers of America, "Information Brokers of America Child Identity Theft Protection" http://web.archive.org/web/20080706135451/http://iboainfo.com/child-order- .html as archived Jul. 6, 2008 in 1 page. cited by applicant .
Information Brokers of America, "Safeguard Your Child's Credit", http://web.archive.org/web/20071215210406/http://www.iboainfo.com/child-i- d-protect.html as archived Dec. 15, 2007 in 1 page. cited by applicant .
Intelius, "People Search--Updated Daily, Accurate and Fast!" http://www.intelius.com/people-search.html?=&gclid=CJqZIZP7paUCFYK5KgodbC- UJJQ printed Nov. 16, 2010 in 1 page. cited by applicant .
Iovation, Device Identification & Device Fingerprinting, http://www.iovation.com/risk-management/device-identification printed Nov. 5, 2012 in 6 pages. cited by applicant .
Irby, LaToya, "How Will a Late Payment Hurt My Credit Score?" http://web.archive.org/web/20101024113603/http://credit.about.com/od/cred- itscorefaq/f/how-late-payment-affects-credit-score.htm, Oct. 24, 2010, pp. 1. cited by applicant .
"Judging Credit: Consumers Need Better Finance Tools", News Journal, Daytona Beach, FL, Dec. 28, 2002. cited by applicant .
Khan, Mickey Alam, "Equifax Recognizes Changing Customer Behavior with Four-Pronged Mobile Strategy", Mobile Marketer, http://web.archive.org/web/20151117005818/http://www.mobilemarketer.com/c- ms/news/strategy/9733.html, Apr. 19, 2011 in 10 pages. cited by applicant .
Lan, Joe, "The Top Portfolio Management Software," http://www.aaii.com/computerizedinvesting/article/the-top-portfolio-manag- ement-software, Includes Discussion thread, Fourth Quarter 2011, pp. 17. cited by applicant .
Lanubile, et al., "Evaluating Empirical Models for the Detection of High-Risk Components: Some Lessons Learned", 20th Annual Software Engineering Workshop, Nov. 29-30, 1995, Greenbelt, Maryland, pp. 1-6. cited by applicant .
Lee, W.A.; "Experian, on Deal Hunt, Nets Identity Theft Insurer", American Banker: The Financial Services Daily, Jun. 4, 2003, New York, NY, 1 page. cited by applicant .
Leskovec, Jure, "Social Media Analytics: Tracking, Modeling and Predicting the Flow of Information through Networks", WWW 2011--Tutorial, Mar. 28-Apr. 1, 2011, Hyderabad, India, pp. 277-278. cited by applicant .
Letter to Donald A. Robert from Carolyn B. Maloney, dated Oct. 31, 2007, pp. 2. cited by applicant .
Letter to Donald A. Robert from Senator Charles E. Schumer, dated Oct. 11, 2007, pp. 2. cited by applicant .
Letter to Harry C. Gambill from Carolyn B. Maloney, dated Oct. 31, 2007, pp. 2. cited by applicant .
Letter to Harry C. Gambill from Senator Charles E. Schumer, dated Oct. 11, 2007, pp. 2. cited by applicant .
Letter to Richard F. Smith from Carolyn B. Maloney, dated Oct. 31, 2007, pp. 2. cited by applicant .
Letter to Richard F. Smith from Senator Charles E. Schumer, dated Oct. 11, 2007, pp. 2. cited by applicant .
Li et al., "Automatic Verbal Information Verification for User Authentication", IEEE Transactions on Speech and Audio Processing, vol. 8, No. 5, Sep. 2000, pp. 585-596. cited by applicant .
LifeLock, "How LifeLock Works," http://www.lifelock.com/lifelock-for-people printed Mar. 14, 2008 in 1 page. cited by applicant .
LifeLock, "LifeLock Launches First ID Theft Prevention Program for the Protection of Children," Press Release, Oct. 14, 2005, http://www.lifelock.com/about-us/press-room/2005-press-releases/lifelock-- protection-for-children. cited by applicant .
LifeLock; "How Can LifeLock Protect My Kids and Family?" http://www.lifelock.com/lifelock-for-people/how-we-do-it/how-can-lifelock- -protect-my-kids-and-family printed Mar. 14, 2008 in 1 page. cited by applicant .
LifeLock, Various Pages, www.lifelock.com/, 2007. cited by applicant .
Littwin, Angela, "Beyond Usury: A Study of Credit-Card Use and Preference Among Low-Income Consumers", Texas Law Review, vol. 86, No. 3, pp. 451-506; Feb. 2008. cited by applicant .
Lobo, Jude, "MySAP.com Enterprise Portal Cookbook," SAP Technical Delivery, Feb. 2002, vol. 1, pp. 1-13. cited by applicant .
Lund, Graham, "Credit Bureau Data: Maximizing the Benefits," Credit Management, May 2004, ProQuest Central, pp. 44-45. cited by applicant .
Magid, Lawrence, J., Business Tools: When Selecting an ASP Ensure Data Mobility, Los Angeles Times, Los Angeles, CA, Feb. 26, 2001, vol. C, Issue 4, pp. 3. cited by applicant .
"Managing Debt?" Federal Trade Commission: Consumer Information, http://www.consumer.ftc.gov/articles/0158-managing-debt, printed Mar. 22, 2013 in 4 pages. cited by applicant .
Manilla, http://www.manilla.com/how-it-works/ printed Feb. 5, 2014 in 1 page. cited by applicant .
Meyers et al., "Using Your Social Networking Accounts to Log Into NPR.org," NPR.org, Jun. 24, 2010, http://web.archive.org/web/20100627034054/http://www.npr.org/blogs/inside- /2010/06/24/128079309/using-your-social-networking-accounts-to-log-into-np- r-org in 3 pages. cited by applicant .
Micarelli et al., "Personalized Search on the World Wide Web," The Adaptive Web, LNCS 4321, 2007, pp. 195-230. cited by applicant .
Microsoft, "Expand the Reach of Your Business," Microsoft Business Solutions, 2004, in 16 pages. cited by applicant .
Mint.com, http://www.mint.com/ printed Sep. 18, 2008 in 2 pages. cited by applicant .
Mint.com, http://www.mint.com/how-it-works/ printed Feb. 5, 2013 in 2 pages. cited by applicant .
MS Money Software by Microsoft http://www.microsoft.com/Money/default.mspx as retrieved on Sep. 17, 2008. cited by applicant .
Mvelopes, http://www.mvelopes.com/ printed Feb. 5, 2014 in 2 pages. cited by applicant .
My Call Credit http://www.mycallcredit.com/products.asp?product=ALR dated Dec. 10, 2005 on www.archive.org. cited by applicant .
My Call Credit http://www.mycallcredit.com/rewrite.asp?display=faq dated Dec. 10, 2005 on www.archive.org. cited by applicant .
My ID Alerts, "Why ID Alerts" http://www.myidalerts.com/why-id-alerts.jsps printed Apr. 3, 2012 in 2 pages. cited by applicant .
My ID Alerts, "How it Works" http://www.myidalerts.com/how-it-works.jsps printed Apr. 3, 2012 in 3 pages. cited by applicant .
MyReceipts, http://www.myreceipts.com/, printed Oct. 16, 2012 in 1 page. cited by applicant .
MyReceipts--How it Works, http://www.myreceipts.com/howItWorks.do, printed Oct. 16, 2012 in 1 page. cited by applicant .
"Name Availability Records", Westlaw Database Directory, http://directoy.westlaw.com/scope/default.asp?db=NA-ALL&RS=W&VR=2.0 as printed Dec. 17, 2009, pp. 5. cited by applicant .
National Alert Registry Launches RegisteredOffendersList.org to Provide Information on Registered Sex Offenders, May 16, 2005, pp. 2, http://www.prweb.com/printer/240437.htm accessed on Oct. 18, 2011. cited by applicant .
National Alert Registry Offers Free Child Safety "Safe From Harm" DVD and Child Identification Kit, Oct. 24, 2006. pp. 2, http://www.prleap.com/pr/53170 accessed on Oct. 18, 2011. cited by applicant .
National Alert Registry website titled, "Does a sexual offender live in your neighborhood", Oct. 22, 2006, pp. 2, http://web.archive.org/wb/20061022204835/http://www.nationallertregistry.- com/ accessed on Oct. 13, 2011. cited by applicant .
"New for Investors: Asset Allocation, Seasoned Returns and More," Prosper, http://blog.prosper.com/2011/10/27/new-for-investors-asset-allocation-sea- soned-returns-and-more/, pp. 4. cited by applicant .
Next Card: About Us, http://web.cba.neu.edu/.about.awatson/NextCardCase/NextCardAboutUs.htm printed Oct. 23, 2009 in 10 pages. cited by applicant .
Ogg, Erica, "Apple Cracks Down on UDID Use", http://gigaom.com/apple/apple-cracks-down-on-udid-use/ printed Nov. 5, 2012 in 5 Pages. cited by applicant .
Organizing Maniac's Blog--Online Receipts Provided by MyQuickReceipts.com, http://organizingmaniacs.wordpress.com/2011/01/12/online-receipts-provide- d-by-myquickreceipts-com/ dated Jan. 12, 2011 printed Oct. 16, 2012 in 3 pages. cited by applicant .
Paustian, Chuck, "Every Cardholder a King Customers get the Full Treatment at Issuers' Web Sites," Card Marketing, New York, Mar. 2001, vol. 5, No. 3, pp. 4. cited by applicant .
People Finders, http://www.peoplefinders.com/?CMP=Google&utm.sub.--source=google&utm.sub.- --medium=cpc printed Nov. 16, 2010 in 1 page. cited by applicant .
People Lookup, "Your Source for Locating Anyone!" www.peoplelookup.com/people-search.html printed Nov. 16, 2010 in 1 page. cited by applicant .
People Search, "The Leading Premium People Search Site on the Web," http://www.peoplesearch.com printed Nov. 16, 2010 in 2 pages. cited by applicant .
PersonalCapital.com, http://www.personalcapital.com/how-it-works printed Feb. 5, 2014 in 5 pages. cited by applicant .
Planwise, http://planwise.com printed Feb. 8, 2013 in 5 pages. cited by applicant .
Planet Receipt--Home, http://www.planetreceipt.com/home printed Oct. 16, 2012 in 1 page. cited by applicant .
Planet Receipt--Solutions & Features, http://www.planetreceipt.com/solutions-features printed Oct. 16, 2012 in 2 pages. cited by applicant .
Press Release--"Helping Families Protect Against Identity Theft--Experian Announces FamilySecure.com; Parents and guardians are alerted for signs of potential identity theft for them and their children; product features an industry-leading $2 million guarantee"; PR Newswire; Irvine, CA; Oct. 1, 2007. cited by applicant .
Privacy Rights Clearinghouse, "Identity Theft: What to do if it Happens to You," http://web.archive.org/web/19990218180542/http://privacyrights.org/- fs/fs17a.htm printed Feb. 18, 1999. cited by applicant .
"Qualifying for Debt Settlement", http://www.certifieddebt.com/debt/settlement-qualifications.shtml printed Jan. 9, 2013 in 2 pages. cited by applicant .
Quantix Software, "Investment Account Manager," available at https://www.youtube.com/watch?v=1UwNTEER1Kk, as published Mar. 21, 2012. cited by applicant .
Quicken Online by Intuit http://www.quicken.intuit.com/, as retrieved on Sep. 17, 2008. cited by applicant .
"Quicken Support", http://web.archive.org/web/20071231040130/http://web.intuit.com/support/q- uicken/docs/d.sub.--qif.html as archived Dec. 31, 2007 in 6 pages. cited by applicant .
Ramaswamy, Vinita M., Identity-Theft Toolkit, The CPA Journal, Oct. 1, 2006, vol. 76, Issue 10, pp. 66-70. cited by applicant .
Rawe, Julie; "Identity Thieves", Time Bonus Section, Inside Business, Feb. 2002, pp. 2. cited by applicant .
Repici et al., "The Comma Separated Value (CSV) File Format", http://creativyst.com/Doc/Articles/CSV/CSV01.htm, Creativyst, Inc., 2002, pp. 10. cited by applicant .
"Resolve Debt for Less: With Help from Freedom Financial" http://www.debtsettlementusa.com/ printed Jan. 9, 2013 in 6 pages. cited by applicant .
Romig, Shane, "The Truth About Credit Repair", Credit.com, May 5, 2010, http://web.archive.org/web/20100505055526/http://www.credit.com/credit.su- b.--information/credit.sub.--help/The-Truth-About-Credit-Repair.jsp printed Mar. 22, 2013 in 4 pages. cited by applicant .
Roth, Andrew, "CheckFree to Introduce E-Mail Billing Serving," American Banker, New York, Mar. 13, 2001, vol. 166, No. 49, pp. 3. cited by applicant .
SAS, "SAS.RTM. Information Delivery Portal", Fact Sheet, 2008, in 4 pages. cited by applicant .
Scholastic Inc.:Parent's Request for Information http://web.archive.org/web/20070210091055/http://www.scholastic.com/infor- equest/index.htm as archived Feb. 10, 2007 in 1 page. cited by applicant .
Scholastic Inc.:Privacy Policy http://web.archive.org/web/20070127214753/http://www.scholastic.com/priva- cy.htm as archived Jan. 27, 2007 in 3 pages. cited by applicant .
Screenshot for Investment Account Manager v.2.8.3, published at http://www.aaii.com/objects/aet/1642.gif by at least Aug. 30, 2011 in 1 page. cited by applicant .
"Settling Your Debts--Part 1 in Our Debt Settlement Series", http://www.creditinfocenter.com/debt/settle.sub.--debts.shtml printed Jan. 9, 2013 in 6 pages. cited by applicant .
Shin, Laura, "See an Error on Your Credit Report? Credit Karma Now Makes It Easy to Dispute", Nov. 12, 2015, http://www.forbes.com/sites/laurashin/2015/11/12/see-an-error-on-your-cre- dit-report-credit-karma-now-makes-it-easy-to-dispute/, pp. 4. cited by applicant .
ShoeBoxed, https://www.shoeboxed.com/sbx-home/ printed Oct. 16, 2012 in 4 pages. cited by applicant .
Simpson, Glyn, "Microsoft (MS) Money (MSMoney FAQ, Help and Information Pages", pp. 2, Copyright .COPYRGT. Glyn Simpson 1998-2007, http://web.archive.org/web/20071018075531/http://money.mvps.org/faq/artic- le/196.aspx. cited by applicant .
Singletary, Michelle, "The Littlest Victims of ID Theft", The Washington Post, The Color of Money, Oct. 4, 2007. cited by applicant .
Stauffer et al., "Using HTML 3.2," Second Edition, 1996, Que Publishing, pp. 192-193. cited by applicant .
"TransUnion--Child Identity Theft Inquiry", TransUnion, http://www.transunion.com/corporate/personal/fraudIdentityTheft/fraudPrev- ention/childIDInquiry.page as printed Nov. 5, 2009 in 4 pages. cited by applicant .
TransUnion Consumer Credit Report http://www.transunion.com/, as retrieved on Sep. 17, 2008. cited by applicant .
Truston, "Checking if your Child is an ID Theft Victim can be Stressful," as posted by Michelle Pastor on Jan. 22, 2007 at http://www.mytruston.com/blog/credit/checking.sub.--if.sub.--your.sub.--c- hild.sub.--is.sub.--an.sub.--id.sub.--theft.sub.--vi.html. cited by applicant .
US Legal, Description, http://www.uslegalforms.com/us/US-00708-LTR.htm printed Sep. 4, 2007 in 2 pages. cited by applicant .
Vamosi, Robert, "How to Handle ID Fraud's Youngest Victims," Nov. 21, 2008, http://news.cnet.com/8301-10789.sub.--3-10105303-57.html. cited by applicant .
Waggoner, Darren J., "Having a Global Identity Crisis," Collections & Credit Risk, Aug. 2001, vol. vol. 6, No. 8, pp. 6. cited by applicant .
Wesabe.com http://www.wesabe.com/, as retrieved on Sep. 17, 2008. cited by applicant .
Yahoo! Search, "People Search," http://people.yahoo/com printed Nov. 16, 2010 in 1 page. cited by applicant .
Yodlee | Money Center, https://yodleemoneycenter.com/ printed Feb. 5, 2014 in 2 pages. cited by applicant .
You Need a Budget, http://www.youneedabudget.com/features printed Feb. 5, 2014 in 3 pages. cited by applicant .
Application as filed in U.S. Appl. No. 09/411,683, dated Oct. 4, 1999. cited by applicant .
Awoonor-Williams, Princess Josephine, Ph.D. "Gender and Credit: An Analysis of Women's Experience in the Credit Market", ProQuest Dissertations and Theses, 2004, pp. 148. cited by applicant .
"Disputes in Cyberspace 2001: Update of online dispute resolution for consumers in cross-border disputes", Consumers International, Nov. 2001, pp. 45, http://web.archive.org/web/20160414183303/http://www.consumersint- ernational.org/media/304196/disputes%20in%20cyberspace%202001.%20update%20- of%20online%20dispute%20resolution%20for%20consumers%20in%20cross-border%2- 0disputes..pdf. cited by applicant .
Elangovan, A.R., "Managerial Third-Party Dispute Intervention: A Prescriptive Model of Strategy Selection", Academy of Management, Oct. 1, 1995, vol. 20, No. 4, pp. 800-830. cited by applicant.

Primary Examiner: Simitoski; Michael
Attorney, Agent or Firm: Knobbe, Martens, Olson & Bear, LLP

Parent Case Text

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority benefit under 35 U.S.C. .sctn.119(e) of U.S. Provisional Application No. 61/906,786, filed on Nov. 20, 2013, the disclosure of which is hereby incorporated by reference herein in its entirety.

Claims

What is claimed is:

1. A computing system configured to access a plurality of remote databases in order to identify data inconsistencies between the remote databases and provide user interfaces to a user in order to initiate communication via one or more APIs to certain remote databases indicating updates that reconcile said data inconsistencies, the computing system comprising: one or more storage devices configured to store electronic software instructions; and one or more computer processors in communication with the one or more storage devices, the one or more computer processors configured to execute the stored electronic software instructions to cause the computing system to automatically: access, over a network, first user information stored in the one or more storage devices, the first user information including indications of each of a plurality of remote databases having data regarding a first user, the first user information also including: a plurality of data fields; and a corresponding plurality of master data values associated with respective data fields; access a first remote database of the plurality of remote databases via an application programming interface in communication with the first remote database over the network; determine first remote data associated with the first user stored in the first remote database; compare the first remote data to the first user information by comparing a plurality of master data values in the first user information to corresponding remote data values of remote data fields; identify a particular master data value in a particular data field that does not match a corresponding remote data value in an associated remote data field; generate an interactive user interface for transmission to a remote user computing device, the interactive user interface including authentication prompts usable to authenticate an identity of the first user; receive input from the remote user computing device; compare the input from the remote user computing device to expected authentication information associated with the first user; in response to determining that the expected authentication information matches the input from the remote user computing device, authenticate the first user; generate a second interactive user interface for transmission to the remote user computing device, the second interactive user interface including: the particular master data value; the corresponding remote data value; and a first interactive user interface control usable by the first user to instruct the computing system to update the particular master data value with the corresponding remote data value from the first remote data; in response to receiving an indication via the second user interface that the first user selected the first interactive user interface control, update the particular master data value in the first user information with the corresponding remote data value from the first remote data; identify a subset of the plurality of remote databases that each do not include the corresponding remote data value, said identifying comprising, for each of the plurality of remote databases: accessing the remote database using security protocols and/or communication protocols, over the network; determining a remote data value in a remote data field corresponding to the particular data field in the remote database; determining whether the corresponding remote data value is included in the updated master data value; and if the remote data value is not included in the updated master data value, including the remote database in a subset of remote databases for which updates are available; generate a third user interface for transmission to the remote user computing device, the third user interface including: an indication of the subset of remote databases for which updates are available; and a second interactive user interface control usable to select one or more of the subset of remote databases; and in response to receiving an indication of a selected one or more of the subset of remote databases from the remote user computing device, for each of the selected one or more remote databases: determine security protocols and/or communication; and using the determined security protocols and/or communication protocols, transmit the updated master data value to the selected remote database in order to initiate an update at the selected remote databases.

2. The computing system of claim 1, wherein the authentication prompts display a request for information regarding data of the first user identified in a credit report of the first user.

3. The computing system of claim 1, wherein said accessing the first remote database comprises: accessing first access information in the one or more storage device, the first access information indicating one or more communication parameters for accessing the first remote database.

4. The computing system of claim 3, wherein the one or more communication parameters comprise APIs, security protocols and/or communication protocols used to communicate to the first remote database over the network.

5. The computing system of claim 1, wherein the network comprises one or more of: LAN, WAN, or Internet.

6. A method comprising: accessing, over a network, first user information stored in one or more storage devices, the first user information including indications of each of a plurality of remote databases having data regarding a first user, the first user information also including: a plurality of data fields; and a corresponding plurality of master data values associated with respective data fields; accessing a first remote database of the plurality of remote databases via an application programming interface in communication with the first remote database over the network; determining the first remote data associated with the first user stored in the first remote database; comparing the first remote data to the first user information by comparing a plurality of master data values in the first user information to corresponding remote data values of remote data fields; identifying a particular master data value in a particular data field that does not match a corresponding remote data value in an associated remote data field; generating an interactive user interface for transmission to a remote user computing device, the interactive user interface including authentication prompts usable to authenticate an identity of the first user; receiving input from the remote user computing device; comparing the input from the remote user computing device to expected authentication information associated with the first user; in response to determining that the expected authentication information matches the input from the remote user computing device, authenticating the first user; generating a second interactive user interface for transmission to the remote user computing device, the second interactive user interface including: the particular master data value; the corresponding remote data value; and a first interactive user interface control usable by the first user to instruct a computing system to update the particular master data value with the corresponding remote data value from the first remote data; in response to receiving an indication via the second user interface that the first user selected the first interactive user interface control, updating the particular master data value in the first user information with the corresponding remote data value from the first remote data; identifying a subset of the plurality of remote databases that each do not include the corresponding remote data value, said identifying comprising, for each of the plurality of remote databases: accessing the remote database using security protocols and/or communication protocols, over the network; determining, a remote data value in a remote data field corresponding to the particular data field in the remote database; determining whether the corresponding remote data value is included in the updated master data value; if the remote data value is not included in the updated master data value, including the remote database in a subset of remote databases for which updates are available; generating a third user interface for transmission to the remote user computing device, the third user interface including: an indication of the subset of remote databases for which updates are available; and a second interactive user interface control usable to select one or more of the subset of remote databases; and in response to receiving an indication of a selected one or more of the subset of remote databases from the remote user computing device, for each of the selected one or more remote databases: determining security protocols and/or communication protocols; and using the determined security protocols and/or communication protocols, transmitting the updated master data value to the selected remote database in order to initiate an update at the selected remote database.

7. The method of claim 6, wherein the authentication prompts display a request for information regarding data of the first user identified in a credit report of the first user.

8. The method of claim 6, wherein said accessing the first remote database comprises: accessing first access information in the one or more storage device, the first access information indicating one or more communication parameters for accessing the first remote database.

9. The method of claim 8, wherein the one or more communication parameters comprise APIs, security protocols and/or communication protocols used to communicate to the first remote database over the network.

10. The method of claim 8, wherein the network comprises one or more of: LAN, WAN, or Internet.

11. A non-transitory computer-readable medium storing instructions configured to cause one or more computer processors to perform operations comprising: accessing, over a network, first user information stored in the one or more storage devices, the first user information including indications of each of a plurality of remote databases having data regarding a first user, the first user information also including: a plurality of data fields; and a corresponding plurality of master data values associated with respective data fields; accessing a first remote database of the plurality of remote databases via an application programming interface in communication with the first remote database over the network; determining the first remote data associated with the first user stored in the first remote database; comparing the first remote data to the first user information by comparing a plurality of master data values in the first user information to corresponding remote data values of remote data fields; identifying a particular master data value in a particular data field that does not match a corresponding remote data value in an associated remote data field; generating an interactive user interface for transmission to a remote user computing device, the interactive user interface including authentication prompts usable to authenticate an identity of the first user; receiving input from the remote user computing device; comparing the input from the remote user computing device to expected authentication information associated with the first user; in response to determining that the expected authentication information matches the input from the remote user computing device, authenticating the first user; generating a second interactive user interface for transmission to the remote user computing device, the second interactive user interface including: the particular master data value; the corresponding remote data value; and a first interactive user interface control usable by the first user to instruct a computing system to update the particular master data value with the corresponding remote data value from the first remote data; in response to receiving an indication via the second user interface that the first user selected the first interactive user interface control, updating the particular master data value in the first user information with the corresponding remote data value from the first remote data; identifying a subset of the plurality of remote databases that each do not include the corresponding remote data value, said identifying comprising, for each of the plurality of remote databases: accessing the remote database using security protocols and/or communication protocols, over the network; determining, a remote data value in a remote data field corresponding to the particular data field in the remote database; determining whether the corresponding remote data value is included in the updated master data value; if the remote data value is not included in the updated master data value, including the remote database in a subset of remote databases for which updates are available; generating a third user interface for transmission to the remote user computing device, the third user interface including: an indication of the subset of remote databases for which updates are available; and a second interactive user interface control usable to select one or more of the subset of remote databases; and in response to receiving an indication of a selected one or more of the subset of remote databases from the remote user computing device, for each of the selected one or more remote databases: determining security protocols and/or communication protocols; and using the determined security protocols and/or communication protocols, transmitting the updated master data value to the selected remote database in order to initiate an update at the selected remote database.

12. The non-transitory computer-readable medium of claim 11, wherein the authentication prompts display a request for information regarding data of the first user identified in a credit report of the first user.

13. The non-transitory computer-readable medium of claim 11, wherein said accessing the first remote database comprises: accessing first access information in the one or more storage device, the first access information indicating one or more communication parameters for accessing the first remote database.

14. The non-transitory computer-readable medium of claim 13, wherein the one or more communication parameters comprise APIs, security protocols and/or communication protocols used to communicate to the first remote database over the network.

15. The non-transitory computer-readable medium of claim 11, wherein the network comprises one or more of: LAN, WAN, or Internet.

Description

TECHNICAL FIELD

Embodiments of present disclosure relate to systems and techniques for dynamic interactions with user information.

BACKGROUND

Generally, user computing devices and computing systems may facilitate the management of a user's personal data. For example, the user may have information stored in a plurality of remote databases, such as those used by various social networking sites, elastic on-demand storage systems (for example, cloud computing systems), or remote file sharing services, as well as the user's own personal computer or mobile device to store personal data and/or personal information. The user's use of the Internet may result in a wide distribution of the user's personal information to many different computing systems, devices, and other users. For example, social networking sites, online retailers, and/or blogs may contain personal information about the user.

Generally, when a user wishes to update profile information (e.g., address, phone number, etc.), for example, at a social networking site, credit monitoring service, blog, and/or other online service, the user will manually update the information at each of the sites, by logging into multiple sites and providing information for storage in the relevant databases of the multiple sites. Thus, if a user changes phone numbers, he may need to visit multiple websites and navigate to the profile change sections in each in order to make the same change to the phone number on the multiple sites. These tasks become redundant and, accordingly, the user may not make changes to all accounts. Additionally, such manual changes increase the risk of errors (e.g., typos) in the updated information provides to different entities.

SUMMARY

The systems, methods, and devices described herein each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this disclosure, several non-limiting features will now be described briefly.

Disclosed herein are systems and methods that automatically identify updated information associated with a user in one or more remote databases (e.g., databases associated with online web services) and determine updates to me made to other remote databases based on user rules for providing such automatic updates. Thus, the systems and methods disclosed herein may allow a user to update profile information of the user at not just a single website or entity, but with multiple entities, without requiring the user to communicate with each of the entities individually. In some embodiments, the methods disclosed herein are performed by a profile update system that has existing relationships and/or communication channels with multiple entities, such as financial institutions, government institutions, retail companies, and websites, for example. Accordingly, the profile update system may advantageously push any updates to the user's profile information to multiple entities with which the user has a relationship (e.g., an account) in order to implement such profile updates across the multiple entities. Such updates may be implemented, for example, via an application programming interface (API) that the plurality of remote database (also referred to generally as "partners" or "entities" herein) have access to. For example, a change to a user's information in a first remote database may be determined via access to the first remote database through an API, and changes in the user's information that are identified may be pushed to one or more other remote databases via the API.

The term "database," as used herein, may refer to an database (e.g., RDBMS or SQL database), or may refer to any other data structure, such as, for example a comma separated values (CSV), eXtendible markup language (XML), TeXT (TXT) file, flat file, spreadsheet file, and/or any other widely used or proprietary format. In some embodiments, one or more of the databases or data sources may be implemented using a relational database, such as Sybase, Oracle, CodeBase and Microsoft.RTM. SQL Server as well as other types of databases such as, for example, a flat file database, an entity-relationship database, and object-oriented database, and/or a record-based database.

In some embodiments, a profile update system includes an update status module that communicates with remote databases to which updates were provided in order to track if/when the updates are implemented within those remote databases. The status of the updates may they then be provided to the user, such that the user can intervene in making updates if necessary (e.g., if a remote database associated with a particular user account is not recognizing an address update that the user wants to ensure is correct). Additionally, an update status user interface may include an option for re-requesting updates to the user's information, such as at the request of the user interfacing with the update status user interface, and/or may automatically re-request the profile information be updated at one or more remote databases at which the updates are not implemented within a predetermined time period.

In one embodiment, a computing system is configured to access a plurality of remote databases in order to identify data inconsistencies between the remote databases and provide user interfaces to a user in order to initiate communication via one or more APIs to certain remote databases indicating updates that reconcile said data inconsistencies. The computing system may include one or more storage devices configured to store electronic software instructions and one or more computer processors in communication with the storage device. The one or more computer processors may be configured to execute the stored software instructions to cause the computing system to automatically access first user information stored in one or more storage devices, the first user information including indications of each of a plurality of remote databases having data regarding a first user, the first user information including a plurality of first data fields and a corresponding plurality of first data values associated with respective first data fields, wherein at least some of the plurality of remote databases include matching first data values in particular first data fields, access a first remote database of the plurality of remote databases via one or more network connections and an application programming interface in communication with the first remote database, determine first remote data associated with the first user stored in the first remote database, compare the first remote data to the first user information by comparing each of a plurality of first data values in the first user information to corresponding remote data values of associated data fields in the first remote data, identify a particular first data value that does not match a corresponding remote data value for an associated data field, generate an interactive user interface for transmission to a remote user computing device, the interactive user interface including authentication prompts usable to authenticate an identity of the first user, receive input from the remote user computing device, and compare the input from the remote computing device to expected authentication information from the first user. In one embodiment, in response to determining that the expected authentication information from the first user matches the input from the remote computing device, authenticating the first user and: generate a second user interface for transmission to the remote user computing device, the second user interface including, the particular first data value, the corresponding remote data value, and an interactive user interface control usable by the first user to instruct the computing system to update the particular first data value in the first user information with the corresponding remote data value from the first remote data. In one embodiment, in response to receiving an indication via the second user interface that the first user selected the user interface control, replacing the particular first data value in the first user information with the corresponding remote data value from the first remote data, identifying a subset of the plurality of remote databases that each do not include the corresponding remote data value, generate a third user interface for transmission to the remote user computing device, the third user interface including an indication of at least some of the subset of remote databases and interactive user interface controls usable to select one or more of the subset of remote databases. In one embodiment, in response to receiving an indication of a selected one or more of the first subset of remote databases from the remote user computing device: determine access protocols for each of the selected one or more remote databases; and using the determined access protocols for respective of the selected one or more remote databases, transmitting the corresponding remote data value to each of the selected one or more remote databases in order to initiate updates at each of the selected one or more remote databases.

BRIEF DESCRIPTION OF THE DRAWINGS

The following drawings and the associated descriptions are provided to illustrate embodiments of the present disclosure and do not limit the scope of the claims. Aspects and many of the attendant advantages of this disclosure will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:

FIG. 1A illustrates an example interactive user interface including user profile information for an example user John Doe.

FIG. 1B illustrates an example interactive user interface including user profile information for an example user John Doe, and including login credentials for groups of sites.

FIG. 1C illustrates an example interactive user interface including secondary user profile information for the example user John Doe.

FIG. 2 illustrates an example interactive user interface that may be interacted with by a user in order to provide updates to profile information.

FIG. 3 illustrates an example interactive user interface that may be provided to the user in order to indicate changes to the user's profile that have been implemented (or not implemented) in various remote databases.

FIG. 4 illustrates an example interactive user interface that may be displayed on a mobile device providing similar update status information as that in FIG. 3.

FIG. 5A is a flow diagram illustrating an example workflow for the profile update system authenticating a user, identifying updates to profile information of the user (or receiving profile updates from the user), and providing updated information to a plurality of partners.

FIG. 5B is a flow diagram illustrating an example workflow for the profile update system accessing profile information via an API at a partner and then providing detected updates in the profile information to two other partners via an API.

FIG. 6 is a block diagram showing example components of a profile update system.

DETAILED DESCRIPTION

Although certain preferred embodiments and examples are disclosed below, inventive subject matter extends beyond the specifically disclosed embodiments to other alternative embodiments and/or uses and to modifications and equivalents thereof. Thus, the scope of the claims appended hereto is not limited by any of the particular embodiments described below. For example, in any method or process disclosed herein, the acts or operations of the method or process may be performed in any suitable sequence and are not necessarily limited to any particular disclosed sequence. Various operations may be described as multiple discrete operations in turn, in a manner that may be helpful in understanding certain embodiments; however, the order of description should not be construed to imply that these operations are order dependent. Additionally, the structures, systems, and/or devices described herein may be embodied as integrated components or as separate components. For purposes of comparing various embodiments, certain aspects and advantages of these embodiments are described. Not necessarily all such aspects or advantages are achieved by any particular embodiment. Thus, for example, various embodiments may be carried out in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other aspects or advantages as may also be taught or suggested herein.

Example Interactive User Interfaces

FIG. 1 illustrates an example user interface including user profile information 170 for an example user John Doe. In this example, the profile information 170 includes personal information, family information, professional information, and login information for a plurality of remote databases, such as websites or other secure data sources. As discussed further below, the user may maintain this profile as a master profile that, when updated, causes changes to be pushed to multiple entities, without further input from the user. The user profile may be generated in any manner, such as by the user entering the profile information, by crowdsourcing the user profile information, such as is disclosed in co-pending application Ser. No. 13/794,459, filed on Mar. 11, 2013, or via other profile building functionalities, such as those discussed in co-pending application Ser. No. 13/779,492, filed on Feb. 27, 2013, each of which is incorporated by reference in its entirety and for all purposes.

FIG. 1B illustrates an example interactive user interface including user profile information 172 for an example user John Doe. In this example, the database access credentials (e.g., usernames and passwords in this example) are categorized not by specific remote databases, but rather by categories of information that are maintained and accessible at those remote databases. In this particular example, a first username and password is usable at each of six different remote databases that provide "News/Sports Sites". Similarly, a different username and password are usable at two remote databases that provide "Family" information to the user. Thus, as explained further below, the profile update system may access remote databases using access credentials that are shared among different types or categories of remote databases. Additionally, such categories may be usable by the profile update system to automatically determine which of a plurality of remote databases should be updated with new user profile information. For example, a first update to a user's profile information (e.g., that may be provided by the user himself or that may be automatically detected at a remote database) may be provided to a first category of remote databases (e.g. to all of the "News/Sports Sites"), while a second update to the user's profile information may be provided to a second category of remote databases, but not the first category of remote databases. Such selective updating of user profile information to different remote databases may be based on update rules provided by the user or may be determined based on input from a user at the time an update to profile information is provided by the user or detected by the profile update system.

FIG. 1C illustrates an example interactive user interface including secondary user profile information 174 for an example user John Doe. In this embodiment, the user has created a secondary profile that includes some differences in profile information than in the user's primary profile (e.g. the profiles illustrated in FIGS. 1A and 1B may be considered primary profiles). In some embodiments, a user may have different profile information that they would like to share with different remote databases and/or categories of remote databases. In the example of FIG. 1C, the secondary profile for John Doe includes Personal Information that is different than the Personal Information in the user's primary profile and does not include certain categories of information that are included in the user's primary profile. In one embodiment, the user can select which profile (e.g., a primary, secondary, tertiary, etc.) that the user would like to provide to selected remote databases or categories of remote databases. For example, the user may wish to provide the secondary profile to technical websites and databases, while providing the primary profile to other types of websites and/or databases. Depending on the embodiment, categorization of partners may be performed automatically by the profile update system (e.g., based on categorization provided by other users and/or keyword analysis that is automatically performed by the profile update system).

FIG. 2 illustrates an example user interface that may be displayed to a user in response to selecting the edit button with reference to the personal information section of information illustrated in FIG. 1A. As shown in FIG. 2, the user is offered the opportunity to update any of the personal information items by entering new/updated information in the text entry boxes. In other embodiments, information may be added and/or at edited in any other manner, such as using other user interface controls. In one embodiment, if the user makes changes to the profile data (e.g., by entering a new phone number in the text entry field), and then selects the submit button, the new phone number will be pushed out to each of multiple remote databases by the profile update system. In the embodiment of FIG. 2, the user has typed in a new email address (JD123@email.com). In some embodiments, the entities to which the updates are provided are automatically determined by the profile update system, such as based on information obtained from various data sources, including credit data, social network data, financial data, etc., that may be obtained from one or more data sources regarding the user. In some embodiments, the user may provide a list of remote databases for which data should be updated in response to changes to profile data. For example, with reference to FIG. 1 the user has provided login and password information for 3 websites. In one embodiment the user may select which of the 3 websites (or all 3 websites) that should receive updated profile information in response to updates to the profile information (e.g., using the user interface of FIG. 2).

Once the updates have been pushed to the various remote databases, the profile update system may track status of the updates at each of the (or at least some of the) remote databases and provide updates to the user. FIG. 3 is one example user interface that may be provided to the user in order to indicate changes to the user's profile that have been implemented (or not implemented) in various remote databases. In this example, the update status for John Doe's email change (illustrated in FIG. 2) is provided for each of three remote databases (websites in this example) to which the user requested the email address change be pushed. As noted above, the user may push updates to profile information to any number of entities (not limited to only websites), which may be automatically determined by the profile update system and/or provided by the user.

In the example of FIG. 3, the update status indicates that site 1 and site 2 (e.g., two different remote databases associated with partner websites) changed the email address for John Doe in response to the update request from the profile update system on November 15 and November 16, respectively. The status update also indicates that site 3 had not yet changed the email address for John Doe. In this embodiment, John Doe has the option of selecting a link to initiate resending of the updated email address request to site 3 by selecting the "re-send" link. In one embodiment, resending the updated email address causes the profile update system to transmit the profile update in the same manner as was previously provided to site 3. In other embodiments, resending the updated profile information is performed in a different manner. The user also has the option of selecting the "take me to site" link in order to be redirected to site 3, and possibly to the update profile section of site 3, so that the user can manually update the email address with site 3.

FIG. 4 is an example user interface that may be displayed on a mobile device providing similar update status information as that in FIG. 3, with similar options to allow the user to initiate resending of the update request to a particular site and/or be redirected to the site.

Example Workflow for Updating Remote Databases

FIG. 5A is a flow diagram illustrating an example workflow for the profile update system in authenticating a user, identifying updates to profile information of the user (or receiving profile updates from the user), and providing updated information to a plurality of partners. In the embodiment of FIG. 5A, the Profile Update System 100 may be controlled by any entity that has associations with multiple other entities to which profile update changes will likely need to be provided. Having such preexisting links with these entities makes it easier for the user to provide updated information to multiple entities, which the user may not even have an online account established with. A profile update application used by the user may be provided by the same entity that controls the profile update system 100. For example, the profile update app may be a downloadable application that can be installed on a mobile or desktop computer of the user and/or a browser viewable application that the user can interface with via a web browser.

In the embodiment of FIG. 5A, at a first action (indicated by the circled numeral "1"), the user is authenticated in order to confirm that that user is who they really say they are, and to reduce the risk of fraud in the profile update system pushing profile changes to accounts that are not authorized by the user (e.g., changes that are provided by a fraudster impersonating the user). In this embodiment, an authentication module 102 of the profile update system 100 initiates the authentication process, which may be a process that is carried out entirely by the profile update system 100 or which may include actions by a third-party, such as an authentication provider. Depending on the embodiment, the authentication may take various forms. For example, in one embodiment authentication may be based on "knowledge-based" questions that are asked of the user, wherein the questions are formed in such a way that only the particular user should know the answers. In one embodiment, authentication questions are asked based on information regarding the user located in credit data of the user. Such "out of wallet" questions are configured to solicit responses that include information highly likely to only be known by the user (and/or unlikely to be known by a fraudster), such as a monthly payment amount on an outstanding debt obligation which may appear on the user's credit report, the name or address of a particular loan servicer, the date that the last payment was posted to a credit account, and so on.

Once the user is authenticated (e.g., the user of the remote computing device provides answers to authentication questions, or other authentication information, indicating that the user really is the individual identified in the profile information), the user is given an opportunity to provide profile updates (action 2 of FIG. 5A). In this embodiment, an update module 104 interfaces with the user in order to receive profile updates from the user. As discussed below with reference to FIG. 5B, the update module 104 may also detect changes to the user's profile information at various remote databases and/or determine which other remote databases the detected profile update should be provided to.

In the example of FIG. 5A, the user desires to make a change to profile data that is relevant to profile data stored with multiple data sources/entities. As discussed above, in some embodiments the user may have a master profile stored with a particular service, such as a database maintained by the profile update system, and may make changes to that master profile in order to trigger pushing of changes to multiple remote databases. In other embodiments, the user may log into a website (or call a number associated with) the profile update system in order to initiate the process of pushing changes to the user's profile to multiple remote databases. In this embodiment, the user may not need to provide the full profile information, but rather may provide only the profile information that is to be changed (as well as any other information needed for authentication or other procedures performed by the profile update entity), such as an updated email address or telephone number.

In some circumstances, the user may be required to provide proof of the profile information change, such as by submitting a marriage certificate, death certificate, change of address verification, etc., in order for the profile update system to push the requested profile update to certain entities. For example, certain governmental institutions may require such proof of change before making profile updates regarding the user. Thus, depending on embodiment, the profile update system may forward the proof of change information to one or more entities and/or the entities may rely on the indication from the profile update system that the proof of change information was received and accurately indicated the requested profile update. In some embodiments, a third party that specializes in authenticating such information may be consulted by the profile update system 100 in order to determine whether the updates to the user's profile are legitimate.

At action 3 of FIG. 5A, the profile update system 100 pushes the indicated update to a plurality of remote databases of partners, such as financial institutions, governmental institutions, retail companies, and non-commerce companies, such as websites and social media applications. In other embodiments, any other entity may be included as a recipient of profile updates of the user.

The profile update system may then monitor the status of updates at the various entities, such as by accessing the website of those entities periodically in order to determine whether the requested profile updates have been made. As discussed above with reference to the FIGS. 3 and 4, for example, the user may be provided with various user interfaces indicating the status of profile updates and may be offered options for following up with partners that have not yet made the requested profile updates.

Depending on the embodiment, the user profile information may include various information about the user including, for example, the user's name, gender, age, ethnicity, handicaps, address, contact information, photo, employer, education, interests, and any other data associated with the user.

FIG. 5B is a flow diagram illustrating an example workflow for the profile update system 100 accessing profile information via an API at a partner 501 and then providing detected updates in the profile information to two other partners 502, 503 via an API. Beginning at action 1 in FIG. 5B, the profile update system 100 accesses user information at the partner 501 via an API, such as an API that is provided by the profile update system 100 and allows bidirectional communication between the partner 501 and the profile update system 100. Depending on the embodiment, various security protocols may be implemented in order to prevent unauthorized access to partners view the API. Use of any such currently available and/or later developed technologies or protocols are contemplated.

In other embodiments, other communication protocols and methods may be used in order for the profile update system 100 to obtain user information from the partner 501. For example, the profile update system 100 may query the partner 501 database periodically in order to access information from users that are registered with the profile update system 100, e.g., using login credentials provided by respective users. The profile update system 100 may then compare profile data for respective users from the partner 501 with profile data for the users stored at the profile update system 100 and/or profile information of the user at other partners, such as partners 502, 503.

At action 2 of FIG. 5B, the profile update system 100, such as the update module 104, determines if any updates to the user profile information should be pushed to any remote third-party databases. In one embodiment, the user establishes rules that are usable by the profile update system 100 in order to automatically determine which third-party databases should be updated with new profile information discovered at one or more partners. For example, rules may indicate that certain types or categories of information that are identified as new or changed information at certain specific or groups of remote databases (e.g., trusted databases) are automatically pushed to all other remote databases that require the update (e.g. all that have different information for the updated data field of the user). In other embodiments, the user is provided information on updates to the user's profile that are identified at partner 501 and provided an opportunity to indicate which of a plurality of other partners (e.g., partners 502, 503) to which the detected update should be provided. In one embodiment, the user is provided with a list of other partners that have different information in the updated data fields of the user's profile. The user may then select which of the remote databases to update with the identified profile information. Thus, in one embodiment the user can update profile information across multiple remote databases by updating profile information at a particular site so that the profile update system 100 automatically detects that update and initiates provision of the update to other remote databases. Accordingly, the user may not even need to access a website provided by the profile update system 100 in order to initiate changes to multiple remote databases having profile information of the user. The profile update system 100 may then push the detected profile update to partners 502, 503 via the API (or other communication technology). As noted above, in some embodiments rather than use of an API to access the user profile, the user provides authentication credentials (e.g., login and password) that are usable by the profile update system 100 to login to the users account and automatically update the user's profile information.

In one example embodiment, the user provides a profile update to a first partner 501 and the profile update system 100 automatically detects the update. The detected profile update may then be pushed to the user, such as via an application executing on the user's mobile device or a text message sent to the user's mobile device, with a request to authorize pushing of the detected update to all or some of the other remote databases that store profile information of these user (whether the remote databases are indicated by the user or are automatically detected by the profile update system 100, such as based on scanning of user profile databases of multiple partners, in order to identify remote databases having profile information for respective users). Thus, the user may be able to update profile information at any of multiple remote databases (e.g. of various websites or online services) in order to initiate and easily implement updates of those same profile updates to multiple remote databases.

At action 3 of FIG. 5B, a user interface (including graphical user interfaces, information provided to an application installed on a user device, text messages, etc.) may be provided to the user indicating status of profile updates at one or more remote databases to which the detected profile update has been pushed.

Example System Implementation and Architecture

FIG. 6 is a block diagram showing example components of a profile update system 100. The authentication module 102 and update module 104 of the system 100 may include software code configured for execution by the profile update system 100 to perform the various features discussed herein. Depending on the embodiment, the features discussed herein may be performed by a combination of computing devices, such as a server and a mobile computing device. The profile update system 100 may include these multiple devices.

The computing system 100 includes, for example, one or more personal computer that is Windows, Macintosh, or Linux/Unix compatible or a server or workstation. In one embodiment, the computing system 100 comprises a server, a laptop computer, a smart phone, a personal digital assistant, a kiosk, or a media player, for example. In one embodiment, the exemplary computing system 100 includes one or more central processing unit ("CPU") 105, which may each include a conventional or proprietary microprocessor. The computing system 100 further includes one or more memory 130, such as random access memory ("RAM") for temporary storage of information, one or more read only memory ("ROM") for permanent storage of information, and one or more mass storage device 120, such as a hard drive, diskette, solid state drive, or optical media storage device. Typically, the modules of the computing system 100 are connected to the computer using a standard based bus system 180. In different embodiments, the standard based bus system could be implemented in Peripheral Component Interconnect ("PCI"), Microchannel, Small Computer System Interface ("SCSI"), Industrial Standard Architecture ("ISA") and Extended ISA ("EISA") architectures, for example. In addition, the functionality provided for in the components and modules of computing system 100 may be combined into fewer components and modules or further separated into additional components and modules.

The computing system 100 is generally controlled and coordinated by operating system software, such as Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server, Unix, Linux, SunOS, Solaris, iOS, Blackberry OS, or other compatible operating systems. In Macintosh systems, the operating system may be any available operating system, such as MAC OS X. In other embodiments, the computing system 100 may be controlled by a proprietary operating system. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, I/O services, and provide a user interface, such as a graphical user interface ("GUI"), among other things.

The exemplary computing system 100 may include one or more commonly available input/output (I/O) devices and interfaces 110, such as a keyboard, mouse, touchpad, and printer. In one embodiment, the I/O devices and interfaces 110 include one or more display devices, such as a monitor, that allows the visual presentation of data to a user. More particularly, a display device provides for the presentation of GUIs, application software data, and multimedia presentations, for example. The computing system 100 may also include one or more multimedia devices 140, such as speakers, video cards, graphics accelerators, and microphones, for example.

In the embodiment of FIG. 6, the I/O devices and interfaces 110 provide a communication interface to various external devices. In the embodiment of FIG. 6, the computing system 100 is electronically coupled to one or more networks, which comprise one or more of a LAN, WAN, and/or the Internet, for example, via a wired, wireless, or combination of wired and wireless, communication link. The networks communicate with various computing devices and/or other electronic devices via wired or wireless communication links, such as the various entities to which updated profile information is to be sent.

In general, the word "module," as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, Java, Lua, C or C++. A software module may be compiled and linked into an executable program, installed in a dynamic link library, or may be written in an interpreted programming language such as, for example, BASIC, Perl, or Python. It will be appreciated that software modules may be callable from other modules or from themselves, and/or may be invoked in response to detected events or interrupts. Software modules configured for execution on computing devices may be provided on a computer readable medium, such as a compact disc, digital video disc, flash drive, or any other tangible medium. Such software code may be stored, partially or fully, on a memory device of the executing computing device, such as the computing system 100, for execution by the computing device. Software instructions may be embedded in firmware, such as an EPROM. It will be further appreciated that hardware modules may be comprised of connected logic units, such as gates and flip-flops, and/or may be comprised of programmable units, such as programmable gate arrays or processors. The modules described herein are preferably implemented as software modules, but may be represented in hardware or firmware. Generally, the modules described herein refer to logical modules that may be combined with other modules or divided into sub-modules despite their physical organization or storage. As noted above, the authentication module 102 may initiate and/or perform authentication of a user, primarily to determine whether the user that is requesting profile information and/or providing profile information really is the user identified in such information. The update module 104 may perform various tasks, such as interfacing with a user to receive updates to profile information, comparing updates to profile information stored at the profile update system 100 and/or at one or more other remote databases, and determine which remote databases profile updates should be provided to (whether such profile updates are automatically detected by the update module 104 or the updates are provided directly from an authenticated user). These modules may perform fewer or additional tasks in various embodiments. Similarly, the modules may be stored and executed on separate computing devices, even computing devices that are not co-located.

Additional Embodiments

Each of the processes, methods, and algorithms described in the preceding sections may be embodied in, and fully or partially automated by, code modules executed by one or more computer systems or computer processors comprising computer hardware. The code modules may be stored on any type of non-transitory computer-readable medium or computer storage device, such as hard drives, solid state memory, optical disc, and/or the like. The systems and modules may also be transmitted as generated data signals (for example, as part of a carrier wave or other analog or digital propagated signal) on a variety of computer-readable transmission mediums, including wireless-based and wired/cable-based mediums, and may take a variety of forms (for example, as part of a single or multiplexed analog signal, or as multiple discrete digital packets or frames). The processes and algorithms may be implemented partially or wholly in application-specific circuitry. The results of the disclosed processes and process steps may be stored, persistently or otherwise, in any type of non-transitory computer storage such as, for example, volatile or non-volatile storage.

The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and sub-combinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example embodiments.

Conditional language, such as, among others, "can," "could," "might," or "may," unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.

Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.

All of the methods and processes described above may be embodied in, and partially or fully automated via, software code modules executed by one or more general purpose computers. For example, the methods described herein may be performed by the computing system and/or any other suitable computing device. The methods may be executed on the computing devices in response to execution of software instructions or other executable code read from a tangible computer readable medium. A tangible computer readable medium is a data storage device that can store data that is readable by a computer system. Examples of computer readable mediums include read-only memory, random-access memory, other volatile or non-volatile memory devices, CD-ROMs, magnetic tape, flash drives, and optical data storage devices.

It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure. The foregoing description details certain embodiments. It will be appreciated, however, that no matter how detailed the foregoing appears in text, the systems and methods can be practiced in many ways. As is also stated above, it should be noted that the use of particular terminology when describing certain features or aspects of the systems and methods should not be taken to imply that the terminology is being re-defined herein to be restricted to including any specific characteristics of the features or aspects of the systems and methods with which that terminology is associated.

* * * * *