`
` |||l|ll|l||||||||||||||||||||||||||
`
`USOU??39139B2
`
`(12}
`
`United States Patent
`Robertson et a].
`
`(IO) Patent No.:
`
`(45} Date of Patent:
`
`US 7,739,139 32
`Jun. 15, 2010
`
`(54)
`
`(75)
`
`(73)
`
`SOCIAL NETWORKING SYSTEM
`
`Inventors: Brian D. Robertson, Boston. MA (US);
`Warren W. Adams. lidgartown. MA
`(US)
`
`Assignee: Amazon Technologies, Inc.. Reno. NV
`(US)
`
`(*l
`
`Notice:
`
`Subject to any disclaimer, the term ofthis
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`
`(21)
`
`Appl. N0.: ӣ127,495
`
`(22)
`
`Filed:
`
`May 27, 2008
`
`(65)
`
`(60)
`
`(so
`
`(52)
`(58)
`
`(56)
`
`Prior Publication Data
`
`US 20(l8f0228887 A1
`
`Sep. 18, 2008
`
`Related US. Application Data
`
`Continuation of application No. ӣ022,089. filed on
`Dec. 22. 2004. now Pat. No. 7.386.464. which is a
`division ofapplication No. 10t780,486. filed on Feb.
`17. 2004. now Pat. No. 7.194.419. which is a continu—
`ation of application No. 091348.355. filed on Jul. 7.
`1999. now Pat. No. 6314.916. which is a continuation
`of application No. 08;“962397. filed on Nov. 2. 1997.
`now Pat. No. 6.269.369.
`
`Int. C1.
`6061-" 9X44
`
`(2006.01)
`
`
`Field of Classification Search ...................... 70519
`
`See application file for complete search history.
`References Cited
`
`U .S. PA'I'IiN'l DOCUMENTS
`
`4.626.836 A
`
`12-"l986 Curtis etal.
`
`T05r'l
`
`4.862.357 A
`5.086.394 A ’8
`5.263.160 A
`5.276.901 A
`5.459.859 A
`5.539.813 A
`5.796.995 A
`5.?37.T26 A
`5394.210 A
`5.831.611 A
`5.835.08? A
`
`8:"[989 Ahlslrotn elal.
`2-"1992 Shapira
`[131993 Porter. Jr. ct a].
`131994 Howell eta].
`[031995 Senda
`11996 Jonssonct al.
`3:199? DcIIond
`451998 Cameron elal.
`8.0998 Goldhaber ct a].
`11.51998 Kennetiyetal.
`[131998 Hen. et :1].
`
`(Continued)
`FOREIGN PA’I'EN'I‘ DOC UMl-IiN'l'S
`
`JP
`
`405 |08902 A
`
`4-1993
`
`OTHER PUBLICATIONS
`
`Weilman (For A Social Network Analysis of Computer Networks).
`Jan. 1995.ACM.pp. 1412*
`
`(Continued)
`
`Prinmrj’ E.\'arriincr-— Romain Jeanty
`(74) Attorney. Agent, or Finn Knobbc. Martens. Olson &
`Bear 1,1,?
`
`(57)
`
`ABSTRACT
`
`A networked computer system provides various services for
`assisting users in locating. and establishing contact relation-
`ships with. other users. For example. in one embodiment.
`users can identify other users based on their aIIilialions with
`particular schools or other organizations. The system also
`provides a mechanism for a user to selectively establish con—
`tact relationships or connections with other users. and to grant
`permissions for such other users to view personal in formation
`ofthe user. The system may also include features for enabling
`users to identi t‘y contacts oftheir respective contacts. In addi -
`tion. the system may automatically notify users of personal
`information updates made by their respective contacts.
`
`25 Claims, 14 Drawing Sheets
`
`
`FSEUDD FRIENDS OF FRIENDS
`REPORT FOR HEMHER A
`
`
`Your Friends of Friend:
`in Group A:
`
`PM
`
`Member C (via Member 8}
`
`Hamber E ilnks ta Hembor it
`Member A links In Member E
`with any level ul parmlsslons
`with Friends of Friends\permlssions
`\._.
`you
`“3'
`
`w
`
`585
`‘\
`Member 3 links to Member I:
`nlth any level of permtsulons
`
`537
`W
`Number c links in Member B
`with Friends of Fdonds\pormisstona
`
`,3
`
`Jr
`.r
`
`r
`l'
`Ilt
`l
`\
`\
`
`5:94
`
`
`
`LYFT 1017
`
`LYFT 1017
`
`1
`
`
`
`US 7,739,139 B2
`Page 2
`
`U.S. PATENT DOCUMENTS
`
`5.348.395 A
`5.948.040 A
`6.049396 A
`6.070.160 A
`6.092.088 A
`6.116.831 Bl
`6.269.369 Bl
`6.460.036 Bl
`6.714.916 Bl
`7.194.419 B2
`
`12:"1998 Edgaretal.
`9t'1999 Deiormeetal.
`402000 Siilonen et al.
`StZUGU Gear}!
`TIEUOU Takeda
`132001 Weinrcichelal.
`10200] Robertson eta].
`10t2002 Herz
`3t2004 Robertson eta].
`3t200'i Robertson eta].
`
`OTHER PUBLICATIONS
`
`Kaut'z. et' al (ReferralWeb: Combining Social Netwurks and Collabo-
`rating Filtering). Mar. 1997. Communication of thcACM. vol. 40 No.
`3. pp. ]-4.*
`“i997 Edition GS LORI! Otgmiizer/Erpiotittg Otgttttizert’Windon-n
`95 edition.“ pp. iii-vii and 8-1-8-6.
`“Appiieotions Hwtdbook Fw' the Palm 1'” “Organizer.” 3C om. pp.
`iii-v. and 1-12 (Apr. 1998).
`“Symontee ACT! User’s Gttide and Reference. Version 2. 01b:- Witt-
`dmvs." pp. ix—Xvi and 3—1 1—3-26.
`“inforttmtion about Lotus Noresfl'ont titeLottts Web Site (wwwLotus.
`com). “ pp. 1-13 (Apr. 1998).
`“Domino 4.6 Features Omwimv." Jul. 199?. 2 pages. wwwiotus.
`comidomino.
`“Yahoo! White Pages." Copyright 1994-1998. Yahool. httpL-‘Z-‘www.
`yahoocomi.
`
`“thoWhete. ." Copyright 1995-1998. Who-“Where? lnc.. httpdt
`mzwhowherecomi.
`R. Tamura. et al.. “Lotus Notes 4." pp. 39. 64-65. and 176 ( I996).
`Cardwell. "C:vberseene Pionet Keeps lbn in Town.“ Dec. 1996. Bos-
`ton Herald Boston.
`Day. “New Software Ti'tttrks Corporate Travel Finns.“ Jan. 1991.
`Denver Post (Denver. C0.US). V99 N153 sC p2. Dialog File 63
`Accession No. 0187621.
`Wetzel. "Mtniietpoiiy—owned venues-feet brunt ol‘eity budget cuts.”
`Aug. I991.Amusemenl Business. v103. n31. p3(3). Dialog File 148,
`Accession No. 05427255.
`“Should montqizetnrers it)» to estabiish rapport with their agents"
`other prinetptzis.” Mar. 1995. Agencyr Sales Magazine v25n3. pp.
`13—15.Dialog File 15. Accession No. 00988855.
`Smith. "COittpanies Meet End: Otnerot tiieAityiot't.” Jul. 1995. The
`Los Angcles Times. ISSN: 04583035.
`Gerety. "Whore Job is itAtn-n-ayI’; Meetings .43 a Subset of Fave}:
`Yes or No?.” Apr. 1992. Business Travel News. ISSN: 8250-3610
`Brisson. et 511.. “Lifeco Pitts Pre-fi'ip Control in Ti'ovel’ Monagers’
`Hands,” Mar. [991. Business Travel News. ISSN: 8250-36110.
`“PionetAt'ipions to Make :7 World offlifi'erenee in BttsyLives.” Nov.
`1996. PR Newswirc. pp. 11 13NEW025.
`“Fat! i’nternet Worid ”96 Exhibitor Previews.” Dec. 3. [996. Business
`Wire. p. 12030220. Dialog File 16. Accession No. 04716024.
`Answer and Second Amended Counterclaims of Defendant Amazon.
`com, Inc. in Cordance Corporation v. Amazon.com, Inc. (CA. No.
`06-491-MP'I‘).
`
`* cited by examiner
`
`2
`
`
`
`US. Patent
`
`Jun. 15, 2010
`
`Sheet 1 of 14
`
`US 7,739,139 B2
`
`Wad
`
`wad
`
`
`
`zofid‘EmOmZ44209:?—
`
`
`
`mm<>>tomH2m2u0<z<2
`
`
`
`zo_h<2w_omz_4<ZOMmmm
`
`
`
`mesEomHzm2m0<z<2
`
`Oz_._.<mm_n_o
`
`
`
`mm<3Eom25.96
`
`oz_._.<mm_n_o
`
`
`
`mmdgfiom35.9%
`
`
`
`awksmiooQfiIIQZdImozofigmxmogmum:
`
`SE
`
`«SQ
`
`\mm<0m>mx
`
`mmao:
`
`><4mm_o
`
`wagag\be
`
`4<mMIEmmm
`
`mmo_>mo
`
`3
`
`
`
`
`
`
`
`
`
`m04mmmpz_
`
`F2mzoM“Na
`4mum:mmqahLOmmmqakmomnFZmzo
`
`
`
`
`
`smhm>msmpm>m
`
`
`
`02:4mmmoozzqmmmo
`
`US 7,739,139 B2
`
`“N%v\ma¥¢mmN%\K
`
`U
`
`m
`
`m
`
`m
`
`n.mm\Max
`
`“gmmm<
`
`01mm>mmm
`
`
`
`:aoxfi&mv\
`
`
`
`mm>mmmmm>mmm
`
`03,wzz4mmmo5“xxozpqmwaommaxmm<apmom
`
`mm<apu0mzmaox
`0Qmfim555356NE
`
`
`
`
`
`hxmoapmzSzofidhmxmozrmam:BaxEgan—zoo
`
`4
`
`
`
`
`US. Patent
`
`Jun. 15, 2010
`
`Sheet 3 of 14
`
`US 7,739,139 B2
`
`\QNK
`
`//NQN
`
`
`
`szmmEmmmomzimomum:
`
`zo:.<§w_ol._z_mum:
`
`
`
`ommfio._.Oz.25mum246mQz<<mmfiullll|
`
`
`
`
`
`
`
`
`
`0mmfioHoz._.:m_mmm24.0mQz<<mmdqoslilllll
`
`mum240._._<Lilli
`
`
`
`mum240<mmfio\SzoIllull
`
`
`
`mumz<omzozalllll
`
`mumz<o<mmfio520Llll|u
`
`
`
`mum240.34....I.||l
`
`mum2404.3Tail
`
`3%.h§§%“QNLN
`
`mzoxmH.301
`
`
`
`mZOImxmoa
`
`
`
`mmmenE520$
`
`
`
`mmmmam<xmoz
`
`5E.mow
`
`$5155
`
`
`
`mzo_H<_.__.._.._<nSOmo
`
`
`
`mmwmooq422m
`
`5
`
`
`
`
`
`
`
`
`
`
`
`
`US. Patent
`
`Jun. 15, 2010
`
`Sheet 4 of 14
`
`US 7,739,139 B2
`
`mum:
`
`weigh;
`
`QMVN
`
`mm<mqh<a
`
`-QR“;
`
`
`
`tut/mum
`
`uh“;
`
`OWE
`
`mud...
`
`2¢moomm
`
`wzfin‘mmmo
`
`25.9%
`
`.wbw
`
`mm>mmmmm;
`
`mmqgfiom
`
`Emhm>m
`
`ozfidmwmo
`
`REM. sumo:
`
`mmmgommmm?
`
`umdahuOm
`
`oz;<mmmo
`
`25.95
`
`mquEOm
`
`mmMEOmmmm;
`
`:mhm»m
`
`ozfidmumo
`
`
`
`$5;on55:40
`
`BN0»
`
`mm;QED;
`
`mm;
`
`BEN
`
`m.35%
`
`hawk§$\
`
`6
`
`
`
`US. Patent
`
`Jun. 15, 2010
`
`Sheet 5 of 14
`
`US 7,739,139 B2
`
`“KM;wWEE.
`
`mmdmahqa
`
`Nb“;
`
`
`
`:moEdmOOmm
`
`m3;
`
`.83“;
`
`$3“;25m?
`
`mzfiqmmmo
`
`Fur“.
`
`mm>mmmmm;
`
`mmqifiom
`
`
`
`
`
`do:wo<pzou.mmmm
`
`by“NK28.95
`5.25;:E8
`
`
`mum:«Eda44004
`VMM VF“,
`
`numum;
`
`Uma
`
`mmmEOmmmm?
`
`mm<>_...._...._om
`
`3.3%
`
`mmzbmxouHijo
`
`
`
`«mm.nkmou
`
`mmanHOmz:
`
`ozfid‘mmmo
`
`mmqafiomw
`
`mmmEOmmmm?
`
`gubmym
`
`ozrrqmmmo
`
`mmacstom
`
`ozEEmmo
`
`Ewpm>m
`
`53m;
`
`NEH./as“:
`
`EmmOE
`
`QR“;
`
`mm?
`
`
`
`more;GEO?
`
`Sm“;
`
`Sam,
`
`mm>mmm
`
`3mm.
`
`7
`
`
`
`
`
`
`
`US. Patent
`
`Jun. 15, 2010
`
`Sheet 6 of 14
`
`US 7,739,139 132
`
`
`
`uaflcemmeLumhingehoustfi\erwV
`Boo?comma=50NxIQVV
`glam»:25«an?»
`
`
`
`
`
`
`
`otmEofizootmEEmzuH93:8.:02:32*EE
`
`“roammom
`
`
`
`BEBE““1thquz33QxthV
`
`925EThaw2328&
`
`
`
`RSVNIQVV
`
`muzohwau
`
`5“
`
`23:33:”.V383?
`
`
`GEE—2mmVImulhuVV
`a“?PNNIQVVoEoEom:hing“.
`
`
`
`atuEEmzonotuEBmzuA
`
`
`
`
`
`72¢:5&8“WIN“
`
`
`VIQNM.QEEBuaoatmEofizu
`.mIQNh..mlmmw.28221.33LmnEazwcoihigh.finegthdBoghwcocmWinona;
`
`
`
`
`nzcmfilfififiEEouomwcoiVlmhfi.
`
`
`
`
`
`
`
`
`
`h2m>ml4m><mh
`
`
`
`WIQNMNthmum.
`
`
`
`“N.““Gm.
`
`otmEEmauuatmEEmsu
`
`/M.VIQ\V
`
`VMIQNWH
`“drawn2afig
`Slam.23528205
`wm.—L”
`Eco—BogaBxlfifih
`
`
`“QENN
`
`350m
`
`amum
`
`NIQ%V
`
`V19“?
`
`MIQNV
`
`mrhmuv
`
`
`
`as.1Q%\.
`
`NNI33“.
`
`Vxlbw?
`
`EunEoumm
`h\lemon.
`
`
`
`mflmfi.mmrho
`
`maficofimmELom
`
`QVM.
`
`\NIQNV
`
`Luu>Eoi
`
`mango
`
`Lom>oh
`
`was:558
`(MK1&3“.
`
`EuoEoumm
`9mIQNV
`
`NIBWV
`
`MIQNV
`
`rtztmq
`
`ENE
`
`\IQNV
`
`.
`
`NJQNV
`
`otmEEmsu.
`
`
`.wIQNV
`
`E.:20H9.320
`wEuzmzoho
`
`«
`
`x.I38“.
`
`mzomo
`
`“an“?
`
`9395
`
`mnfinnflo
`
`7%:Ex;
`£099.03?
`auxIQ“?
`
`WIQQV
`
`u.IQQV
`
`NIfiQV%I39.»
`
`8
`
`
`
`
`
`
`
`
`
`
`US. Patent
`
`Jun. 15, 2010
`
`Sheet 7 of 14
`
`US 7,739,139 32
`
`535
`
`_\
`
`PSEUDO REGISTRATEON FORM
`
`560—2
`
`Name
`
`HomeAddress
`
`Home Phone
`
`Work Address
`
`Work Phone
`
`Birthday
`
`Your High School
`
`550-22?
`
`560—725
`
`Year of Enrollment E Gradua’rion Year
`
`Your CoHegeI
`
`550-4
`
`550—5
`
`56‘0""?
`
`560_/0
`
`56‘0“}?
`
`550— M
`
`560—f6’
`
`5567—24
`
`Graduafion Year El
`
`9
`
`
`
`US. Patent
`
`Jun. 15, 2010
`
`Sheet 8 of 14
`
`US 7,739,139 32
`
`.550
`
`,\
`
`PSEUDO GROUP LIST FORM
`
`Foiiowing are ’rhe o’rher members who went
`your coiiege o’r abou’r
`ihe some time.
`
`’ro
`
`
`
`Kffi’fl-l
`’rhe names of
`’ro
`Click on ’rhe boxes nex’r
`you’d like ’10 add 10 your Address Book.
`
`ihe peopie
`
`0—5
`
`550-5
`
`55044
`
`State University, 1982—1986
`550—10
`550—72
`/
`N
`W John Doe (Graduated 1935)
`
`I: Robert Johnson (Gruduaied 1986)
`
`1:] Jane Smiih (Graduated 1986)
`550-1?1
`
`FIG: 6’
`
`10
`
`10
`
`
`
`US. Patent
`
`Jun. 15, 2010
`
`Sheet 9 of 14
`
`US 7,739,139 32
`
`6'00
`
`PSEUDO PERMlSSlON FORM
`
`fifififl—z”
`Click on l'he boxes nex’r
`
`lo ’rhe Permission Levels l’hol
`
`you would like ’ro gron’r To your new contact
`
`600—5
`
`/_
`6‘00 7% Crossing Po’rhs Notificolion Permission
`/"500—c9
`
`
`
`ggp—yfl
`
`Personal
`
`Information
`
`E] Birthday Nolificoiion
`
`/_
`Friend of Friends Informollon
`
`(aw—M
`
`600—1’6‘i
`
`[76: 9
`
`11
`
`11
`
`
`
`US. Patent
`
`Jun. 15, 2010
`
`Sheet 10 of 14
`
`US 7,739,139 B2
`
`9N.“
`
`2::22.833:95:0022223535mt:mwm259:2:9.:
`
`%M%\
`
`
`
`*0>xznough
`
`%M%.\
`
`m_cozoELEEor:
`
`2::29.8SvwEEEoE
`
`«HQ
`
`
`
`92%42$2358
`
`2?83:53:;
`
`38m323m2
`
`Eoodw_@33%
`
`92${253358
`
`mmkénmnta
`
`EmtwxooocoImm
`
`Name.:LonEmoma
`
`
`
`2:;"223
`
`NINQJ/
`
`“:25
`
`VIVMfi
`/"x33
`
`mvlwhm
`J”323m
`
`/
`
`soak m._m_>u._
`
`
`nEOOmmmmmoaq083mm
`
`33mJoana.%N%
`
`MANN
`
`
`
`xOOmmmmzonzoosmmm
`
`Nd3:
`
`ammeHwflmfl
`
`238n:3
`
`
`
`2.30.353.
`
`$6
`
`12
`
`%\%\u\
`
`
`
`F._m>m._.mufimuhév_OOmmmmmaoq092mm;
`
`
`
`
`
`
`
`12
`
`
`
`
`US. Patent
`
`Jun. 15, 2010
`
`Sheet 11 MM
`
`US 7,739,139 32
`
`550—\
`
`PSEUDO MEMBER UPDATE
`
`Member Update fliffl-I
`December 7, 1998
`
`[650—4
`
`The following of your contacts have orienting birthdays:
`
`—
`—
`
`Avery Rogers (Dec. 11)
`Jane Bigelow (Dec. 14)
`
`_.
`£50 6
`
`Your contacts have registered the following address changes:
`—
`Tam Kohn
`
`/—6'5£7-¢5’
`
`New work address:
`1000 Wilson Boulevard
`
`Arlington, Va 22229
`
`630-)?
`
`New work phone:
`
`703—558—3312
`
`_
`
`}55'9 ’7
`
`/65§—/4
`The following new members have affiliated with the some groups as you:
`—
`Gary Clayton (State College, 1985)
`
`“—5504;
`
`The following members have linked to you and have requesle
`you reoiprocaie:
`—
`Jun Ohama
`
`Lee Rogers } 6.515%20
`
`6'50— In?
`
`that
`
`Anne Thlerry
`
`—
`
`—
`
`/ 550—22
`You have scheduled a trip to Phoenix on December 14. The following of
`your contacts live in Phoenix or will be in Phoenix on that date:
`--
`Andrew Kress
`
`Taylor Pierce }550—24
`
`According to Astrology,
`you today (Libras)
`w»
`Bryan Jamieson
`—
`
`55§_25
`
`‘lhe following at your coniacts are compatible with
`
`550-25
`
`['76: I]
`
`13
`
`13
`
`
`
`US. Patent
`
`Jun. 15, 2010
`
`Sheet 12 of 14
`
`US 7,739,139 B2
`
`3E239...no»:$52..:9:2:6:$3639:x85
`
`.9559630>2E;
`
`
`
`Rn.“SEQ...d>qEQ3.
`
`Winn“
`
`“£02.mam—9,9...
`
`0935;
`030205an_____sEoflcuu.50»we0.320222:.hrhm‘fi
`
`
`.03263:5;Ba;a;E:52:E252Immm
`km:I._.<n_Oz_memo0935;Mama“
`
`
`
`
`.mrhflwk“Bug:026E3E4
`
`£25:08Do32059,:05528;(QTQLQ
`
`
`SEE.633._H._.ENIQMQ
`Eu;yflmmD:32EEm2in:
`
`TS.{\"965
`
`VIBNM...\:5:you
`
`
`
`
`
`.3.$vam
`
`52.0.;as=5.0:32own—
`
`anon—:0DEE._H_
`
`NNENE
`
`5525g2:?
`
`“Booca36.263
`
`14
`
`14
`
`
`
`
`US. Patent
`
`J
`
`N2H“,
`
`m&
`
`Mf0
`
`US 7,739,139 B2
`
`«SEQ
`
`8sz..—motzEE093mm.»
`
`4mmmfimzm8Eonfim
`
`no.5Euncut;+0wncmESS,
`
`%\SEN
`
`o39:52
`
`.LmEm0:;L0Emmmmmkfima2.Vonz4is»:I,
`0453sz23::m53:82
`BmgwnEmz
` mcofiflctoa”633.\EU£3..0LEE;29E:mhonEuz.,
`mcEmmHELma/mncfliBmtg:5:3
`awni/mumm.
`”Po_m>m_\Eo3:2.\xm$380:2.mxc:4.33mex
`\b\%.Qxmcofiflctma
`
`\mfik
`
`mcofimeLmQ/wucflihomuse:5:;m.53sz23::oLmnEmE
`
`K“Na
`
`.._
`
`15
`
`
`
`
`
`
`
`
`US. Patent
`
`Jun. 15, 2010
`
`Sheet 14 of 14
`
`9US7
`
`739,139 B2
`
`Sm.
`
`
`
`3:99Baofiom
`
`EEflwmfi
`
`
`
`East;332%.65252.:263:32$50anE3£52234
`
`
`
`3:993:8.me.5EoEanu
`
`cozaELSEn2mg2meta;
`
`Emsuco:3:3303%Show
`
`
`
`.mLmEanoEmma.3
`
`
`
`mLmSanoEEG
`
`3.E5.63an0E360+3.2.33
`
`Eustom3:1
`
`Nam,
`
`SSW
`
`mfimfi.
`
`9Q,32:005mmmEm:
`
`39:30wkLam:-<5m:98
`
`LflquooBSQEoomamLaw:2StemvmuooEgoU2095:0
`
`m.m_Em:coEcztom
`
`uflova:E.53an0
`
`16
`
`
`
`
`
`coZoELBEUmmccco£75
`
`NNENE
`
`huh:mmEELE
`
`
`
`$2030$325
`
`VQNM.
`
`£5334E:B.m:sBSQEooE362SEES<BEano
`
`Emzu
`
`16
`
`
`
`
`
`
`
`l
`SOCIAL NETWORKING SYSTEM
`
`2
`user workstation 160 to access the files 148 under the median
`
`US ?,?39,l39 BZ
`
`RELATED AP PLICA’I‘IONS
`
`This application is a continuation of U .3. application Ser.
`No. 1 “022,089. filed Dec. 22, 2004, now U.S. Pat. No. 7,386,
`464 which is a division 0111.8. patent application Ser. No.
`101780.486.fi1ed Feb. 17. 2004, now U.S. Pat. No. 7.194.419
`which is a continuation of U.S. patent application Ser. No.
`091848.355. filed Jul. 7. 1999 (now U.S. Pat. No. 6.714.916).
`which is a continuation of U.S. application Ser. No. 08:062.
`997. Filed Nov. 2. 1997 (now U.S. Pat. No. 6.269.369).
`
`BACKGROUND OF THE INVENTION
`
`1. Field of the Invention
`
`The present invention relates generally to multi-user com-
`puter systeriis. such as contact management systems.
`that
`provide services for users to locate and share personal in for-
`mation with other users.
`2. Description of Related Art
`Several types ofprior art for managing contact information
`exist, including Personal Information Mmiagenient software
`applications. Groupware Applications. and Internet-based
`“White Pages" and e-mail services.
`Personal Information Management Software. As repre-
`sented generally in ["IG. 1, in a typical prior art Personal
`Information Management (PIM) software application (e.g._.
`Lotus Organizer. Microsoft Outlook, or U.S. Robotics Palm
`Pilot), 3 PIM software application 1 20, 124 that stores contact
`information in a database resides on a workstation or hand-
`
`held computer 100 having a central processing unit 102. a
`display 108. a keyboard andfor mouse 110. a primary memory
`104 (e.g.. random access memory) for program execution. a
`secondary memory 106 (e.g.._ a hard disc) for program stor—
`age. and peripheral devices 112. As is well known. programs.
`such as the PIM software 120. are executed in the RAM 104
`by the CPU 102 under control of the operating system soft-
`ware 122. 126.
`
`In the prior art. users themselves enter the contact infor-
`mation that they want to store in the PIM software. A variety
`oi‘methods exist for entering this contact information. It may
`be entered manually tisiiig the keyboard. imported from an
`existing file on their computer. or imported via a peripheral
`device such as a business card scanner. The defining charac-
`teristic of this class of prior art is that the input ofthe contact
`information is performed by the user of the sofiware and.
`when the in limitation changes.
`the user must modify the
`information himself What this class of prior art lacks is a
`means for information to be shared between multiple users
`and a means for a given user to ptist changes to his own
`information for the benefit of others.
`
`Groupware Applications. As generally represented in FIG.
`2. in a typical prior art Groupware application (e.g.. Lotus
`Notes), a userworkstation 160 accesses information stored on
`a central server computer 130 over a computer network 150.
`such as a Local Area Network or Intranet. The server system
`consists of a central processing unit 132. a primary memory
`134 (cg. random access memory) for program execution. a
`secondary storage device 136 (e.g.. a hard disc) for program
`storage. and a modem 138 or other device for connecting to
`the computer network. The user workstation 160 is the same
`as the user workstation 100 described in reference to FIG. 1
`with the addition of a riiodem 162 or other device for con—
`
`necting to the computer network. The file server or database
`contains data files 148 that can be accessed only by authorized
`users. The user uses client software 174. [76 running on the
`
`5
`
`10
`
`3t]
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`tion of server software 140. 144 running on the server 130.
`Typically. it] such a system a central system administrator
`organizes users into classes and the creator of a file 148
`determines what classes of users may view the file. The rules
`governing which individual users or classes of users have the
`authorization to view a particular file 148 may be stored as
`part of the file itself. Alternatively. these rules are based upon
`the hierarchical directory structure of the file server in which
`the file is stored. That is. a particular user may view files in
`one directory but not another.
`FIG. 3 represents a common deployment ofa contact man-
`agement system based on Groupware. Iziach user enters infor-
`mation 202 about himself and specifies a set of permissions
`204 that define what classes of users are able to view various
`
`pieces ofthe information 202. What this deployment of the
`prior art lacks is the abil ity to authorize viewing privileges on
`a user-by-uscr basis rather than on a class-by-class basis. For
`instance. a user wottld be able to grant access to his home
`phone number 206 to the Human Resources department ofliis
`employer (e.g.. Class A) while denying access to the same
`information to his co-workers (e.g.. Class C). The user would
`not be able to give access to his home phone number selec-
`tively to a first co-worker while denying it to a second co-
`worker if both co~workers were part ofthe same class ofusers
`as organized by the central system administrator. Further~
`more, such a system would lack a practical notification meth-
`odology. There would be no way for a user to specify “notify
`me when the first co-worker changes his information but not
`when the second co-worker changes his information."
`Internet—Based “White Pages" and E—Mail Directory Ser—
`vices. in a typical prior art” “white pages" or c-mail service,
`client computers and a server computer are connected via the
`World Wide Web as depicted in FIG. 4. A user subscribes to a
`White Pages or B-Mail service via a client computer 270
`operating a web browser 282 or other software application
`residing in memory 274 that allows it to display information
`downloaded from a server computer 230 over the World Wide
`Web 260. The server computer system accesses a database
`240 containing contact
`infomiation entered by registered
`users. The service enables users to view contact information
`
`entered by other users. The authorization scheme may allow
`all users to limit certain classes of users from viewing certain
`parts of their user record as represented in FIG. 3. However.
`there are no linkages between individual users and thus users
`cannot restrict the viewing oftheir information on a user-by—
`user basis. Furthermore. users cannot be notified when infor-
`
`mation for particular users has changed.
`
`SUMMARY
`
`A networked computer system provides various services
`for assisting users in locating, and establishing Contact rela-
`tionships with. other users. For example, in one embodiment.
`users can identify other users based on their aliiliations with
`particular schools or other organizations. The system also
`provides a mechanism for a user to selectively establish con-
`tact relationships or connections with other users. and to grant
`permissions for such other users to view personal information
`ofthe user. The system may also include features for enabling
`users to identify contacts oftheir respective contacts. In addi-
`
`17
`
`17
`
`
`
`US ?,?39,139 BZ
`
`3
`
`tion. the system may automatically notify users of personal
`information updates made by their respective contacts.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`The accompanying drawings, which are incorporated in
`and form a part of this specification. illustrate embodiments
`of the invention. wherein:
`FIG. 1 depicts a computer loaded with Personal Informa-
`tion Management software;
`FIG. 2 generally depicts the data schema ofa category of
`prior art known as groupware applications;
`FIG. 3 shoWs a common scheme for authorizing permis-
`sion to view information in the prior art:
`FIG. 4 depicts two computers interconnected via the Inter-
`net. one of which is a server connected to a database and the
`other of which represents a user's client workstation. both of
`which are configured according to the prior art:
`FIG. 5 depicts two computers interconnected via the litter-
`net. one ofwhich is a server connected to a database and the
`other of which represents a user‘s client workstation, both of
`which are configured according to the present invention:
`FIG. 6 represents an object model of the key tables in the
`relational database maintained on the server computer in the
`preferred embodiment of the present invention;
`FIG. 7 represents a pseudo graphical user interface in
`which a userenters information in specific data fields to create
`a personal data record:
`FIG. 8 represents a pseudo graphical user interface for
`listing other users with the same group alliliation as that
`specified by a first user;
`FIG. 9 represents a pseudo graphical user interface for
`specifying what type ofdata fields from a first user’s personal
`data record to which the first user wishes to grant a specific
`second user access:
`FIG. 10 represents a pseudo graphical user interface that
`displays the information stored in a user’s personal address
`book:
`FIG. 11 represents a pseudo graphical user interface that
`provides a first user with specific information that has
`changed about the other users to which the first user is linked:
`FIG. 12 represents a pseudo graphical user interface that
`allows a first user to enter travel information and find out
`which contacts have overlapping travel schedules
`FIG. 13 represents a pseudo graphical user interface that
`allows a first user to gather information about the contacts of
`his contacts: and
`FIG 14 is a data llow diagram ofan alternative embodi-
`ment of the present invention where a personal digital assis~
`tant is synchronized with a server database of user informa—
`tion.
`
`DETAILED DESCRIPTION OF PREFERRED
`EMBODIMENTS
`
`Reference will now be made in detail to the preferred
`embodiments of the invention, examples of which are illus—
`trated in the accompanying figures. While the invention will
`be described in conjunction with the preferred embodiments.
`it will be understood that they are not intended to limit the
`invention to those embodiments, On the contrary. the inven-
`tion is
`intended to cover alternatives, modifications and
`equivalents. which may be included within the spirit and
`scope of the invention as defined by the appended claims.
`As represented in FIG. 5= the preferred embodiment fol—
`Iowa; a standard lntemet architecture. in which client comput-
`ers 37!} and a server computer 330 are connected via the
`
`10
`
`3t]
`
`4t]
`
`45
`
`50
`
`55
`
`60
`
`65
`
`4
`World Wide Web 360 and modems 338, 378 or other corn»
`munications channels. A user accesses the server 360 via a
`
`client computer 370 operating a web browser 382 or other
`software application residing in memory 374 that allows it to
`display information downloaded front a server computer 330.
`The server computer system 330 runs server software 342,
`including the networkeomputer-based personal contact
`manager 343 of the present invention, which interacts with
`the client computers 370 and a user information database 340.
`In a commercial embodiment of the present invention. the
`personal contact manager 343 is the heart of a Web-based
`personal contact management service called PlanetAll. The
`database 340 contains contact information entered by regis-
`tered users. The personal contact manager 343 in some sitti—
`ations will notify a set of users of updates made to the datt —
`base 340 by another user to whom the notified set is related.
`The database 340 in is a relational database built from a set
`ofrelational tables 350. In the conventional manner. both the
`
`server 338 and the clients 370 include respective storage
`devices. such as hard disks 336 and 376 and operate under the
`control of operating systems 344. 384 executed in RAM 334.
`374 by the CPUs 332, 372. The server storage device 336
`stores program files 346 and the operating system 348. Simi-
`larly. the client storage devices 376 store the web browser
`software 386 and the operating systems 388. In an alternative
`configuration. in which the client is a personal information
`manager (PIM), such as the U .S. Robotics Palm Pilot. the disc
`376 can also include a local FIM database 390 and PIM
`software. which performs data management and synchroni—
`zation functions.
`FIG. 6 outlines the data structure ofthe relational database
`340 in the preferred embodiment, in which seven tables 350
`are employed to enable most of the functionality ofthe sys-
`tern:
`
`(l ) Customer Table 440:
`(2) Friend Table 460:
`(3) Group Table 400:
`(4) Affinity Table 420:
`( 5) Address Table 480;
`(6] Phone Table 500: and
`(7) Travel livent Table 520;
`The Customer Table 440 contains one record for each
`unique user. The key field in this table is Customcrll) 440-2.
`All information stored in the various database tables relating
`to a particular member is linked together by a unique [lumber
`in this field. Other important fields in this table include infor-
`mation used by users to login to the system (Usemame 440—6
`and Password 440—8), information which helps users identify
`each other (First Name 440-18. Last Name 440-12. and
`l'i-mail 440-20), information required to provide Birthday
`Notification (Birthday 440-16) and information required to
`provide Crossing Paths notification (Citle 440-14). l-Zach
`record in the Customer Table 440 is time-stamped via the
`RecordDate field 4404. Other fields 440-22 can also be
`included in the Customer Table 440 (and the other tables as
`well).
`The l-‘riend Table 460 relates users to each other. l'iach
`
`record in the table represents a relationship between one user.
`identified by CustomerlD 460-4. and another. identified by
`Friendll) 460-6, with a certain level of pemiissions 460-10.
`The user interface ofthe system provides a multitude of ways
`for users to view information about other users. and every one
`of these ways relies on a database query of the Friend Table
`460 to determine the list of other users whose information a
`
`particular user may see. Each record is time-stamped via the
`
`18
`
`18
`
`
`
`5
`
`6
`
`US ?,?39,139 BZ
`
`RecordDate field 460-8 so that users may be notified when
`their contacts‘ records change. l'iach record is uniquely iden-
`tified by a RelationlD 460-2.
`The Group Table 400 contains one record for each unique
`group with which users may affiliate. Each group is identified
`by a GmupName 400-4 and Group'l‘ype 400-6. Examples of
`these groups would be GroupName 400—4 “Massachusetts
`Institute of Technology" (GroupType' “University“) and
`GroupName
`480-4=“Sigma
`Chi"
`(Groupl‘ype=“Fratemity"). Each record has a time-stamp
`400-8 and a unique identifier 400-2.
`liaclt record of the Affinity Table 420 relates a user. iden-
`tified by Customer“) 429-4.
`lo a group,
`identified by
`GroupID 420—6. If a user affiliates with six groups. there
`would be six records in the Affinity Table 420. This table
`stores information about the time period ofa user‘s affiliation
`with a particular group in the FromYcar and 'l’oYear fields
`420-8, 420-18 so that the system may help users find their
`contemporaries. Each record is time-stamped 420-12 so that
`the system may report to users when other users join the
`group, has a unique identifier 420—2 and can include addi—
`tional fields 420—14.
`The Address Table 480 stores infomiation for any number
`and kind of addresses for a particular user. identified by
`Customerll.) 480-4. For instance. it'a user wants to make his
`home address. work address and summer home address avail-
`able to his contacts. there would be three records for that user
`in the Address Table 480, each being identified in part by an
`appropriate AddressType 480—8 (e.g.. home. work. summer
`home). l-iach record is time-stamped 480-16 so that the sys-
`tem can notify users when their contacts have added or modi-
`fied address information and has a unique identifier 480-2.
`Address
`information is conventional.
`including street
`Address 480-8. CityID 480-10. Postal code 48!}- I 2. and mili-
`tary Base 480—14 fields.
`The Phone Table 500 is directly analogous to the Address
`Table 480. but it stores telephone and fax number information
`instead of address information. Each record is identified by a
`unique l’lioneRemrdlD 500-2 and includes the Customerll)
`500-4 ofthe user whose phone information is contained in the
`record. a phone type 1]) 500-6 indicating. eg. whether the
`record is for a telephone or fax. the phone number 500-8 and
`a time—stamp 500—10.
`The Travel Event Table 520 stores infomtation about users’
`travel plans. This table is required to notify users when their
`travel plans intersect with the travel plans of their contacts. A
`record in the Travel Event Table 520 includes the (.‘ustornerlD
`520-4 ofthe user whose travel information is contained in the
`record. arrival and departure dates 5206, 520—8 and a C itle
`520—10 identifying the travel destination. Each record is
`uniquely identified by a Travel_EventID 520-2 and is time-
`stamped with a RecordDate 520-14.
`In the preferred embodiment. a multitude of other tables
`540 are used to enable a variety ofuser services. The Permis-
`sion Type Table 542 contains one record for each of the
`varieties of perntission levels the system allows members to
`assign to their contacts in the Friend Table 460. In the pre-
`ferred embodiment. as illustrated in FIG. 9, permission infor-
`mation is grouped into five categories forthe purpose of user
`interface simplicity (crossing paths notification permission
`600-6. personal information 600-8. work information 600-
`10. birthday notification 600-12. and friends of friends infor-
`mation 600—14]. However. the Permission Type table 542
`could just as easily be structured to allow members to grant
`and deny access to information on a field by field basis.
`The City ’l‘able 550 stores latitude and longitude informa-
`tion for two million cities to enable the system to notify users
`
`5
`
`10
`
`3t]
`
`35
`
`4E]
`
`45
`
`50
`
`60
`
`65
`
`when their contacts travel within a defined geographical
`radius. The Zodiac Table 552 allows the system to associate
`birthdays with signs ofthe Zodiac and thereby notify which of
`their contacts have compatible astrological signs on a particu-
`lar day. The AddressType. Phone'fype and GroupType tables
`544. 546. 548 define the types of address. phone and group
`that can be defined in the respective Address. Group and
`Phone tables 480. 400. 500. The advantage ofthis normalized
`relational database architecture is that it permits scaling and
`speed far in excess ofany embodiment of the prior art.
`FIGS. 7 through 12 display pseudo software graphical user
`interfaces [Gt IIs). In the preferred embodiment. the web
`server software 342 on the servercomputer 330 displays these
`GUIs via the computer communications interface 360 on the
`user interface 380 ofthe user workstation computer 370. The
`database and communications operations necessary to per-
`form the described functions are controlled by the personal
`contact manager 343, which employs where necessary the
`services of the web server soltware 342. For example, the
`personal contact manager 343 updates the database tables 350
`when a user submits a new home address and then determines
`
`whether any of that user’s contacts need to be notified of the
`change. lfso. the personal contact manager 343 will issue the
`notifications via the web server software 342. It should be
`
`assumed. unless a statement to the contrary is made. that all of
`the operations described herein which are aspects o f the
`present invention are embodied by the personal contact rnan-
`ager 343.
`Referring now to FIG. 7. a pseudo GUI S60 is shown that
`allows members to enter information about themselves in
`
`order to create a personal data record. Users can enter infor-
`mation in this GUI in various data fields. In the preferred
`embodiment,
`these fields
`include: Name 560-2. Home
`Address 560-4. Home Phone 560-6. Work Address 560-8.
`Work Phone 560—10, Birthday 560—12. High School 560—14,
`Year of High School Enrollment 560-16. High School Gradu—
`ation