111111
`
`1111111111111111111111111111111111111111111111111111111111111
`US008499046B2
`
`(12) United States Patent
`Zheng
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 8,499,046 B2
`Jul. 30, 2013
`
`(54) METHOD AND SYSTEM FOR UPDATING
`BUSINESS CARDS
`Joe Zheng. Cupertino, CA (US)
`Inventor:
`(76)
`( *) Notice:
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 142 days.
`(21) Appl. No.: 12/436,138
`(22) Filed:
`May 6, 2009
`Prior Publication Data
`(65)
`
`Jan. 24.2013
`US 2013/0022284 A I
`Related U.S. Application Oata
`
`(63)
`
`(51)
`
`(52)
`
`(58)
`
`(2006.01)
`(2012.01)
`(2006.01)
`
`Continuation-in-part of appl ication No. 12/246,507,
`filed on Oct. 7, 2008.
`Int. Cl.
`G06F 15116
`G06Q 10110
`H04L 12158
`U.S. CI.
`CPC ............ G06Q 101107 (2013.01); H04L 121585
`(2013.01)
`USPC ........... 709/206; 709/205; 709/207; 709/222;
`709/229; 709/217; 709/218; 709/219; 709/223;
`709/225; 709/226; 709/245; 709/246;
`707/817.005; 707/817.044; 707/ 10: 707/104;
`707/200; 382/101; 382/112; 382/181; 382/182;
`382/183; 382!188; 382/218; 382/219; 382/220;
`382/221 ; 382/229; 382/305; 382/306; 382/309;
`382/310; 382/3 1 I ; 3821312; 382/313; 382/3 17;
`382/318; 382/3 19; 382/321 ; 705/ 14: 705/26;
`705/27
`
`Field of Classification Search
`USPC .................... 707/ 10, 104, 200; 709/222,229,
`709/205, 206, 207, 217, 218, 219, 223, 245,
`709/246; 705/14, 26, 27; 382/ 101. 112,
`181- 183,188, 220, 221 , 229, 305. 306,
`309- 3 13, 317- 3 19.321
`See application file for complete search history.
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`10/ 1984 Reynolds et al. ............. 396/ 111
`4,474.446 A •
`5.329,400 A •
`7/ 1994 Miyano ......................... 359/673
`5,5 19,540 A •
`5/ 1996 Suzuki .......................... 359/77 1
`6,002,798 A •
`12/1999 Palmeret at. ................. 382/ 176
`6,324,298 81 ..
`11/2001 O'Dell et at. ................. 382/ 149
`9/2002 Mcinerny ..................... 382/3 Ll
`6.453,079 Bl"
`6.542,927 82.
`4/2003 Rhoads .... ...... .......... ..... 709/217
`6,741,724 81 •
`5/2004 Bmcc et al. ................... 382/101
`6.826,548 82.
`I J/2004 Hungerpiller el al ......... 705/40 I
`4/2005 Gropper ................................ 1/ 1
`6,883,000 8 I •
`6,947,57 1 8 I •
`9/2005 Rhoads et at. ................ 382/ 100
`12/2005 Bullet al. ............................. II 1
`6,976,032 81 ..
`1/2006 Loric et al ..................... 382/290
`6.993,205 B I "
`7.000.828 82.
`2/2006 Jones ............................ 235/379
`7,035,427 82.
`4/2006 Rhoads ......................... 382/ 100
`7.092,870 8 1.
`8/2006 Chen et at. .. ................ ...... 704/9
`(Continued)
`
`Primary Examiner - Saket K Daftt1ar
`(74) Attorney. Agent, or Firm-Joe Zheng; Wuxi Sino-IP
`Agency, Ltd.
`
`(57)
`
`ABSTRACT
`
`TechJ1iques for capturing images ofbusiness cards, uploading
`the images to a designated computing device for processing
`and recognition are disclosed. A mechanism is provided to
`update extracted data from the images when there are any
`changes. Depending on implementation, there are a munber
`of ways to capture images ofbusioess cards (e.g., via a phone
`camera, a PC camera, or a scanning device). A transmission
`means is provided to transport the images to the designated
`computing device for centralized management of integrated
`contact infom1ation for individual users. As a result, a user
`may access his/her updatable integrated contact infom1ation
`database anywhere anytime from a chosen device.
`
`17 Claims, 10 Drawing Sheets
`
`110
`
`John Smith
`Manager, XYZ Corporation
`John.smilh@xyz.com
`johnsmilh@yahoo.com
`(wor1<) (650)966-1234
`(Private) (408)777-1234
`MS. Computer Science
`Stanford Unrvers~y, 1998
`
`J.Smilh
`jotwmlh@yahoo.co
`
`102
`
`20~;:::;" .
`0'1
`-r-,-
`!
`/ -
`,...1 Data network
`l
`(e.g., Internet or
`
`30
`
`" r [Y12
`
`'\
`
`o!~'~-7~"
`
`10
`
`Page 1
`
`RMI EXHIBIT 2039
`CBM2014-00116
`
`

`

`US 8,499,046 B2
`Page2
`
`U.S. PATENT DOCUMENTS
`7,164.413 B2*
`112007 Davis et al .................... 345/ 163
`7,421.155 B2 *
`9/2008 King et al. .................... 382/312
`5/2010 Aug1ostine ..................... 7071713
`7,725,456 B2"'
`5120 II Chambers el al .......... 455/414.1
`7,94 1,125 B2"
`5120 l I Henry el al. ................. 358/ 1.1 5
`7,944,573 B2"
`7,986,843 B2"
`7/20 I I Chaudhury et al. .......... 382/229
`8, 1 08,240 B2 "
`1/20 12 Gropper ....................... 70517. 18
`6/2012 Ziklik ........................... 4551415
`8,195,137 B2 *
`8/2012 Huang .......................... 382/181
`8,244,037 B2"'
`11/2004 Gladnick et al ................. 348/79
`2004/0223053 AI"'
`3/2005 Chambers el al .......... 4551556. 1
`2005/0064898 A I "
`512005 Slotkin et al. ................. 235/380
`2005/0 103838 AI"
`6/2005 Level al ....................... 4551566
`2005/0143 136 AI"
`ll/2005 Gropper .......................... 705/ 14
`2005/0251448 AI"'
`2005/0289182 AI*
`12/2005 Pandian et al. ............ 707/ 104.1
`3/2006 King et al. ........................ 707/3
`2006/0047639 AI"'
`3/2006 King et al. . ................... 3821312
`2006/0050996 AI"'
`2006/0053097 A I "
`3/2006 King el al. ........................ 707/3
`2006/0072822 A I "
`4/2006 Hatzav et al. ................. 382/ 18 1
`412006 King el al. .................... 382/229
`2006/0078207 A I "
`5/2006 Lev ............................... 382/ 182
`2006/0098874 AI "'
`2006/0122983 AI*
`6/2006 King et al. ........................ 707/3
`6/2006 King et al. .. ... ... ... ... .... ... . 710/72
`2006/0136629 AI"'
`2006/0 156052 AI"
`7/2006 Bodnar el al. .................... 714/2
`
`2006/0230004 A1 *
`2006/0294094 A1 *
`2007/0229889 AI*
`2007/0294366 A1 •
`2007/0300142 AI*
`2008101264 15 A 1*
`20081013797 1 A 1 •
`200810162603 A1 *
`200810267221 A1 *
`200810292137 AI*
`2008103 13 172 A I •
`2009/0017765 AI*
`2009/00 593 I 0 A 1 •
`2009/0077658 A1 *
`2009/0132590 A1 •
`2009/0157732 A1 *
`2009/0171910 A I *
`2009/0280786 A 1 •
`2010/0010873 A1 •
`2010/0042523 AI *
`2010/0082491 A1*
`20 I 0/02784 53 A I •
`20 12/007908 1 A I •
`* cited by examiner
`
`10/2006
`12/2006
`10/2007
`12/2007
`12/2007
`5/2008
`6/2008
`7/2008
`10/2008
`ll/2008
`12/2008
`1/2009
`3/2009
`3/2009
`5/2009
`6/2009
`7/2009
`11/2009
`l/2010
`212010
`4/2010
`11/20 LO
`3/2012
`
`Handley . .. ... ... .... ... ... ... ... . 706/ 12
`King et al. ........................ 707/6
`Henry et al. ................. 358/ l.l5
`Ozzie et al. . ... ....... ... ... .. 709/217
`King et al. .................... 715/500
`Chaudhury el al. ....... 707/ 104.1
`King el al. .................... 382/229
`Garg et al. .. ... .... ... ... ... .. 707/204
`Ozzie et al. ................... 370/ 503
`Rhoads ......................... 382/100
`King et al. ........................ 707/5
`Lev .............................. 455/66. 1
`Hemy el al. .................. 358/403
`King et al. ...................... 726/21
`Huang ....................... 707/ 104.1
`Hao et al. ...................... 707/ 102
`Srukeshik ......................... 707/3
`Ziklik ........................... 4551415
`Moreau ........................... 705/ 10
`Heruy et al. . .. .... ... . .. .. . ... . 70 5/34
`Rosenblatt et al. . ............ 705/65
`King ............................. 382/32 1
`Pru·ks et al. . ... .... ... ... ... .. 709/220
`
`Page 2
`
`

`

`U.S. Patent
`tnetaP3U
`
`Jul. 30, 2013
`
`m.mw
`Sheet 1 of 10
`
`US 8,499,046 B2
`US 8,499,046 82
`
`am3:12
`
`.93¢m£920:Ema_\
`5.2.8L3f56525
`
`besém:
`
`<5.OE
`
`.,l.\m.S/r\{\{
`
`on
`
`a\B.m.a
`
`Page 3
`
`Page 3
`
`
`

`

`110
`
`John Smith
`Manager, XYZ Corporation
`John.smith@xyz.com
`johnsmith@yahoo. com
`(work) (650)966-1234
`(Private) (408)777-1234
`MS, Computer Science
`Stanford University, 1998
`
`112
`
`John Smith
`Manager, XYZ Corp
`John.smith@xyz.com
`
`J.Smith
`johnsmith@yahoo.co
`
`Server 20
`
`John Smith
`(408)777-1234
`
`Outlook
`(email application)
`
`Yahoo
`(Webmail)
`
`Work
`Cellular phone
`
`Family
`Cellular phone
`
`102
`
`104
`
`106
`
`108
`
`FIG. 18
`
`~
`~
`
`~
`rJ1 .
`"""" n> = """"
`
`~ = -!.H p
`
`N
`0
`~
`!.H
`
`rJ)
`::r
`('D
`('D
`......
`N
`Q .....,
`
`~
`0
`
`d
`(J)
`QO
`):..
`\C
`\C
`Q
`""'" 0\
`o:;
`N
`
`Page 4
`
`

`

`US 8,499,046 B2
`US 8,499,046 82
`
`0“.0E
`
`H839mm.
`
`of8&2;9.55~60
`
`0
`(")
`T"""
`
`}
`
`\
`
`I
`
`~ <1>
`ro u
`.om
`ro't:
`......
`<1>
`ro ......
`0
`.S
`
`(l) c
`0> c w
`0::: u
`0
`
`I
`\
`-.;t
`3:.
`N
`T"""
`
`t2288SEE.a5:855).
`
`c
`0
`:;::;
`(l)
`ro u
`u ro
`~'t:
`' - (l)
`<1>--> .S
`I
`
`\
`
`<0
`N
`T"""
`
`'-
`<1>
`~
`<1>
`(f)
`
`I
`(
`
`<1>
`~
`'U
`0
`E
`c
`E
`'U <
`
`U.S. Patent
`eta01
`emU
`
`mom?
`
`0
`N
`T"""
`
`'-
`(l)
`:t::
`~
`.0
`<1>
`0>
`ro
`E -
`I
`
`\
`
`N
`N
`T"""
`
`Page 5
`
`02
`Jul. 30, 2013
`
`hS
`Sheet 3 of 10
`
` w
`
`
`
`)
`(
`\
`
`c
`0
`:;::; ro u
`0 z
`
`It=
`:;::;
`
`m.meNNFMcozmocnozEtnamama;
`
`Page 5
`
`

`

`Start
`
`200
`
`206
`
`Convert all received records in a standard time
`
`208
`
`Perform merging
`process
`
`212
`
`FIG. 2A
`
`~
`~
`
`~
`rJ1 .
`"""" n> = """"
`
`~ = -(.H p
`
`N
`0
`~
`(.H
`
`rJ)
`::r
`
`('D
`('D
`
`..... .,.
`Q ....,
`~
`0
`
`d
`(J)
`QO
`):..
`\C
`\C
`Q
`""'" 0\
`o:;
`N
`
`Page 6
`
`

`

`220
`~
`
`222
`
`)
`
`Map~~:g .
`
`)
`
`Entry
`Format 1
`
`Entry
`Format2
`
`• • •
`
`Entry
`Format N
`
`Terminal
`devices
`
`224
`
`Display entry
`Last name
`First Name
`Email address
`Office number
`Home number
`Mobile number
`Title
`Company name
`Product area
`etc ...
`
`226
`
`Hidden data
`(manager name)
`,
`·---------------------·
`Server
`
`228
`
`FIG. 28
`
`~
`~
`
`~
`rJ1 .
`"""" n> = """"
`
`~ = -!.H p
`
`N
`0
`~
`!.H
`
`('D
`('D
`
`rJ)
`::r
`.....
`t.ll
`Q ....,
`~
`0
`
`d
`(J)
`QO
`):..
`\C
`\C
`Q
`""'" 0\
`o:;
`N
`
`Page 7
`
`

`

`Start
`
`250
`
`256
`
`Notify/invite giver to
`establish a link with
`the user
`
`268
`
`Extract data from
`image(s)
`
`designated
`account
`
`264
`
`266
`
`FIG. 2C
`
`~
`~
`
`~
`rJ1 .
`"""" n> = """"
`
`~ = -(.H p
`
`N
`0
`~
`(.H
`
`('D
`('D
`
`rJ)
`::r
`.....
`0\
`Q ....,
`~
`0
`
`d
`(J)
`QO
`):..
`\C
`\C
`Q
`""'" 0\
`o:;
`N
`
`Page 8
`
`

`

`272
`
`/274
`I
`
`270
`
`Microsoft Corporation
`
`John Smith
`Software Engineer
`
`One Microsoft Way
`Redmond WA 98052-7329
`
`john@ microsoft. com
`Desk: (425)123-4567
`Mobile®425)111-1111
`
`I View actual card}- 276
`
`Summary
`
`Experienced software engineer with over 1 0 years of experience in C/C++.
`
`Working Experience
`
`278
`
`Current
`
`Past
`
`~
`rJ1
`•
`~
`~
`~
`
`~ = ~
`
`""" = -(..H
`9
`N c ......
`
`(..H
`
`rJ) =(cid:173)~
`~ ....
`
`-...1
`
`0 _, -c
`
`FIG. 20
`
`c
`
`('J)
`QO
`
`~ -...c
`-...c
`Q ,.
`0\ cc
`
`N
`
`Page 9
`
`

`

`U.S. Patent
`U.S. Patent
`
`Jul. 30, 2013
`Jul. 30, 2013
`
`Sheet 8 of 10
`Sheet 8 of 10
`
`US 8,499,046 B2
`US 8,499,046 82
`
`N ......
`
`(Y)
`
`/
`
`£5Ear 05
`
`3m
`,...)
`·-------C
`
`I
`I
`I
`I
`I
`I
`
`
`
`...............JumaouL
`
`y..u....:..,».5.».n....5.(Jul...
`
`-
`
`~-_1
`
`I
`I
`I
`I
`I
`I
`
`:
`:
`:
`
`I
`
`I
`
`...-:
`~:
`g o
`u5~ m
`,
`I _c >= CX)
`: ~ {f)l ";-
`~ E r.~:~ «>
`:
`u (/) (<:.t ~ :
`co
`!::.:: ~ '
`1:3£ H (Y)
`I
`0
`.· ... ,N :
`0
`U-, .9~ 0 I
`I
`I
`'---------- ~
`
`
`
`MM..0E
`
`~
`
`«6.0E
`
`<D
`<D
`
`1.() .,.
`mmmvmmr
`N ......
`
`('t)
`
`Von
`
`~
`~ ~
`~~
`
`0
`0
`(Y)
`
`/ ..
`
`N
`mom
`0
`(Y)
`
`Page 10
`
`Page 10
`
`
`

`

`U.S. Patent
`U.S. Patent
`
`Jul. 30, 2013
`Jul. 30, 2013
`
`Sheet 9 0f 10
`Sheet 9 of 10
`
`US 8,499,046 B2
`US 8,499,046 32
`
`FIG.30
`
`FIG.30
`
`
`
`~ ~~-------------
`1
`
`~---
`
`(')
`
`Page 11
`
`Page 11
`
`

`

`U.S. Patent
`US. Patent
`
`Jul. 30, 2013
`Jul. 30, 2013
`
`Sheet 10 of 10
`Sheet 10 of 10
`
`US 8,499,046 B2
`US 8,499,046 32
`
`FIG.3E
`
`Q)
`
`0> co
`E
`
`$.—
`L-.
`.92:!
`(:2.
`E
`
`E 8
`
`Q) -~ a..
`8 -(I)
`
`I
`
`'5o
`0
`I
`
`330
`
`332
`
`Page12
`
`Page 12
`
`

`

`US 8,499,046 B2
`
`1
`METBOD AND SYSTEM FOR UPDATING
`BUSINESS CARDS
`
`CROSS-REFERENCE TO RELATED
`APPLICATION
`
`1bis is a continuation-in-part of co-pending U.S. applica(cid:173)
`tion Ser. No. 12/246,507, entitled "Method and system for
`maintaining contact information" and filed Oct. 7, 2008.
`
`BACKGROUND OF THE INVENTION
`
`s
`
`2
`sought. Compared to the mm1berofpeople that need to man(cid:173)
`age their business cards, however, only a limlted number of
`users are using business card scanners to manage their busi-
`ness cards electronically.
`lt has beeu observed that it takes some time (e.g., 10-20
`seconds) to scan a card, process an image of the card, and
`recognize the characters in the image, often with some errors.
`A user sometimes has to correct the errors before the data is
`saved in the electronic address book. Further the electronic
`10 address book is only locally accessed unless U1e user trans(cid:173)
`ports the electronic address book to a portable device. Nev(cid:173)
`ertheless, the majority of the electronic address book quickly
`becomes obsolete when persons (a.k.a., givers) of the busi(cid:173)
`ness cards have changed their jobs, phone numbers or email
`15 addresses.
`Some portable devices inl'roduced recently include a cam(cid:173)
`era and a software module. A user can take a snapshot of a
`business card using the camera. The image of the card is then
`processed in a portable device. Being a portable device and o f
`20 low cost, the computing power (horsepower) in the portable
`device is often very limlted. As a result, it takes a longer time
`to process such an image in the portable device. Moreover,
`should a portable device be lost, the user may have lost his/her
`entire electronic address book. Likewise, U1e majority of the
`25 address book becomes obsolete over time.
`There is thus a great need for mechanisms that help pro(cid:173)
`fessionals, business people and others manage their received
`business cards more efficiently and keep their address books
`updated all the times.
`
`J. Field of the Invention
`'D1e present invention generally relates to the area of data
`communication. In particular, the present invention relates to
`method and system for capmring an image of a type of media
`carrying information that a user is desirous to acquire and
`updating the information when there is an update.
`2. Description of the Related Art
`A business card carries not only contact iufom1ation but
`also represents an image of business. Exchanging business
`cards thus becomes a meeting protocol between two people
`when the two meet for the first time. As such there are
`approximately 15 billions business cards exchanged hands
`each year, but about 95% of these cards end up in trash cans.
`One of the reasons that so many business cards are thrown
`away is that these busilless cards are hard to manage and
`impossible to update.
`ln fact, as time goes by, many people end up with a lot of
`collected business cards from numerous occasions. However, 30
`managing these paper-based or banner-like physical business
`cards is indeed not an easy task. Habitually, many people just
`add collected business cards on a pile, sometimes the pile
`becomes so lugh or so big that the bottom part of the pile has
`to be thrown away. unknowingly throwing away important 35
`contact infonnation that may be useful from time to time.
`There are paper versions of business card organizers with a
`few pages, each of the pages including an array of plastic
`transparent pouches that allow users to insert one business
`card in each of the plastic pouches. A business card organizer 40
`provides a way similar to a book for a user to look for a
`particular card. However, soon after a business card organizer
`makes it difficult to orgarlite received business cards. Wllen(cid:173)
`ever a new card is received, those cards already inserted in the
`plastic pouches would have to be shlfted if the user desires to 45
`keep ali the cards in anorder.lnreality, newly received cards
`are o'fien stacked on other cards that are already in tbe plastic
`pouches, resultiug in a disorganized business card organizer
`with many of them being obsolete over times. Worse, a user
`has no way to decide whlch ones shall be discarded.
`An advanced way to manage collected business cards is to
`use business card scanners. Like sheet-fed scanners, a busi(cid:173)
`ness card scanner is a smaller version, particularly designed
`to scan business cards. Typically, a software package is
`installed in a host computing device (e.g .. a PC or PDA). The 55
`software package may include a driver for scanuing/receiving
`image, an OCR (Optical Character Recognition) engine and
`an electronic business card orgaruzer. When a card is scanned,
`the image of the card is transported from the scanner by a
`cable (e.g, .. a USB cable) to the host computing device execut- 60
`ing the software, to extract data from the image by the OCR
`engine and to enter the extracted data into what is commonly
`called an electronic address book. As more business cards are
`scanned in, the electronic address book is gradltally popu(cid:173)
`lated. The electronic address book may provide a sorting 65
`ftmction and/or a searching function for a user to quickly
`locate contact infom1ation of a particular person being
`
`SUMMARY OF THE INVENTION
`
`This section is for the ptrrpose of summarizing some
`aspects o f the present invention and to briefly introduce some
`preferred embodiments. Simplifications or omissions in thls
`section as well as in the abstract or the title of thls disclosure
`may be made to avoid obscuring the purpose of tlus section
`and the abstrdct/title. Such simplifications or omissions are
`not intended to limit the scope of the present invention.
`The present invention is generally related to techniques for
`captming images of business cards, uploading the images to a
`designated computing device for processing and recognition,
`providing a mechanism to update extracted data from the
`images when U1ere are changes. Depending on implementa(cid:173)
`tion, there are a number of ways to capture images of business
`cards. A transmission means is provided to transport the
`images to the designated computing device for centralized
`management of integrated contact information for individual
`users. As a result, a user may access his/her updatable inte-
`50 grated contact information database anywhere anytime from
`a chosen device.
`According to one aspect of the present invention, synchro-
`nizing personal contact information with or from di1Terent
`sources is disclosed. Each oft he sources. such as email appli(cid:173)
`cations, cell phones or PDA, provides a fractional part of the
`personal contact informatiou. 'D1rough a website (i.e., a
`server or system), all fractional personal contact infonnation
`is consolidated, synchronized, processed or updated. ln
`return, any of the resources may be synchronized to get a copy
`of the latest version of the contact information. According to
`one aspect of tbe present inveution, contacts in a list by a
`registered user are also registered with tl1e server. Any oftl1e
`contacts may update their respective contact information that
`can be timely reflected in the list. As a result, the registered
`user always has a latest version of the contact information for
`some or all of his/her contacts without even knowing some
`have already been changed or updated.
`
`Page 13
`
`

`

`US 8,499,046 B2
`
`4
`ing the following detailed description of an embodiment
`thereof, taken in conjunction with the attached drawings.
`
`BRIEF DESCRIPTION OF THE ORA WINGS
`
`5
`
`3
`According to another aspect of the present invention, vari(cid:173)
`otls techniques for capt11ring images of business cards and
`transporting the images to the server are disclosed. An image
`capturing device or mechanism is designed or enabled to
`capture an image of a business card, the image is then trans-
`ported via wireless or wired means to tbe server for process(cid:173)
`ing.ln other words, computing functions necessary to extract
`data from the images are now centralized and executed in a
`server that is typically bas much more computing power than
`a standalone personal device (e.g., a PDA, a PC or a mobile 10
`phone).
`According to yet another aspect of the invention, a verifi(cid:173)
`cation interface is provided to route a result from the central(cid:173)
`ized computing or recognition to a stage for verification. 15
`Depending on implementation, the verification may be con(cid:173)
`ducted with or with human intervention to ensure that the
`result is as accurate as possible before the result is finally
`released to a designated account.
`111e present invention may be implemented in different 20
`forms, as a method and a system. Depending on implemen(cid:173)
`tation, the present invention may be implemented in modules
`some of which are executed in a server device, a computer or
`a portable device. According to one embodiment, to make a
`server or a cluster of servers coufigured to perform the func(cid:173)
`tions contemplated in the present invention more efficiently,
`each account is set to a linrited number of business cards that
`can be processed in a predefined period or additional charge
`may be requested. Should blurred images be uploaded by a
`user, such a blurred image is retained in an account to allow 30
`the user to review it or be aware of the failure to enter elec(cid:173)
`tronically the corresponding business card in the accotult.
`According to another embodiment, the present invention is
`a method for managing contact information, the method com(cid:173)
`prises: receiving an image of a business card from a device 35
`associated with a user that bas received the business card from
`a giver of the business card; processing the image for optical
`cha.racter recognition (OCR) in au OCR engine; entering
`extracted data from the OCR engine as a record into an
`account of the user so that later the user synchronizes a chosen 40
`device with the account to update a local address book in the
`chosen device, wherein the local address book has the record;
`and notifying the giver that the business card has been entered
`electron.ically by the user, wherein the giver is invited to
`establish an account so that the giver is able to manage the 45
`record to keep the user updated of any change to the record.
`According to another embodiment, the present invention is
`a system for managiug contact information, the system com(cid:173)
`prises: a server managing at least an account of a first user;
`and a first device used by the first user to take an image of a 50
`business card received from a second user, the device trans(cid:173)
`porting the image to the server, wherein the server is config(cid:173)
`ured to process the image for optical character recognition
`after a parameter accompanying the image is verified with the
`account of the first user. a result from the optical character 55
`recognition is entered into tl1e accom11 of the first user, and
`meanwhile the server is configured to send a notification to
`the second user indicating the business card has been elec(cid:173)
`tronically entered in the server. The system further comprises
`a second device, used by the first user. having a local address 60
`book, the second device being caused to synchronize with the
`account of the first user at the server, wherein the local address
`includes the record derived from the image of the business
`card.
`There are numerous benefits, feamres, and advantages in 65
`the present invention. These obj~'Cts, features, ru1d advatllages
`of the present invention will become apparent upon exam in-
`
`TI1ese and other features. aspects, and advantages of the
`present invention will become better understood with regard
`to the following description, appended claims, ru1d accompa(cid:173)
`nying drawings where:
`FIG. IA shows a system configuration in which the present
`invention may be practiced in accordance with one embodi(cid:173)
`ment thereof;
`FlG.lB shows a server synchronizing with four exemplary
`email tools or devices (co11ectively referred to as devices);
`FIG. lC shows an exemplary fimctional block diagram or
`a serverthatmay correspouds to the serverofFIG.lA or FIG.
`18;
`FIG. 2A shows a flowchart or process of consolidating
`fractional contact data from different sources;
`FIG. 28 shows a situation iu which an address fonnat is
`different from that in a server, in which case all data in an
`entry from a device is transported to the server while some or
`all of the transported is editable or updated by a user;
`FJG. 2C shows a ftowchart or process of a server functional
`25 block diagram in accordauce with one embodiment of the
`present invention;
`FIG. 20 shows an exemplary layout of a user account
`maintained on a server and accessible from a chosen device;
`FJG. 3A shows a computer display with a camera for cap(cid:173)
`turing an image of a media (e.g., a business card);
`FIG. 38 shows another embodiment in which a screen
`capturing module is provided to allow a user to capture an
`area of interest
`FJG. 3C shows a configuration of using a cel1phone as an
`image capturing device;
`FIG. 3D shows that a micro-lens can be additionally added
`onto the phone camera of a cellphone when a business card is
`placed within an arm distance before tbe phone camera;
`FJG. 38 shows a ftowchart or process of receiving a short
`message (SM) and posting such an MS as a private journal or
`public posting;
`FIG. 3C shows an exemplary carpool offer to be matched
`with a carpool request either by a contact or by a system;
`FJG. 30 shows a ftowchart or process of matching a car(cid:173)
`pool offer and a carpool request; and
`FIG. 3E shows a configuration of using a scanner (e.g.,
`business card scanner, 1-D scatu1er or 2-D imager) operating
`with a host computer.
`
`DETAILED DESCRIPTION OF THE PREFERRED
`EMBODIMENTS
`
`In the followiug description, munerous specific details are
`set forth in order to provide a thorough understanding of the
`present invention. However. it will become obvious to those
`skilled in the art that the present invention may be practiced
`without these specific details. The description and represen(cid:173)
`tation herein are the conu110n means used by those experi(cid:173)
`enced or skilled in the art to most effectively convey the
`substance of their work to others skilled in the art. ln other
`instances, well-known methods, procedures, components,
`and circuitry have not been described in detail to avoid unnec(cid:173)
`essarily obscuring aspects of the present invention.
`Reference herein to "one embodiment" or "an embodi(cid:173)
`ment" means that a particular feature, stmcture, or character(cid:173)
`istic described in C01u1ection with the embodiment can be
`included iu at least one embodiment of the invention. TI1e
`
`Page 14
`
`

`

`US 8,499,046 B2
`
`5
`
`5
`appearances of the phrase "in one embodiment" in various
`places in the specification are not necessarily ali referring to
`the same embodiment, nor are separate or alternative embodi(cid:173)
`ments mutually exclusive of other embodiments. Further, the
`order of blocks in process Rowcharts or diagrams represent-
`iug one or more embodiments of the invention do not inher(cid:173)
`ently indicate any particular order nor imply any limitations
`in the invention.
`Embodituents of the present invention are discussed herein
`with reference to FlGS.lA-3E. However, those skilled in the 10
`art will readily appreciate that the detailed description given
`herein with respect to these figures is for explanatory pur(cid:173)
`poses as the invention extends beyond these limited embodi(cid:173)
`ments.
`FlG. 1A shows a system configuration in which the present 15
`invention may be practiced in accordance with one embodi(cid:173)
`ment thereof. In addition to other services that could be pro(cid:173)
`vided, a server 20 is configured to mru1age synchronized
`contact infonnation lists for a ll registered users. As used
`herein. a list includes one or more contact infonnation 20
`records, each of the records used in the present invention is
`more than just an entry in an address book. As will be further
`described below, a contact information record includes a pro(cid:173)
`file of a contact and a private note (e.g., to reminder to a user
`when/where/how the contact becomes known to the user) in 25
`addition to an entry commonly seen in an address book. Jn
`general, an entry in an address book includes a nrune (e.g.,
`first and last name), affiliation(s) and title(s), email address(s)
`and phone/fax m1mber(s). However, unless specifically
`stated, a contact information list and an address book may be 30
`used interchangeably herein for description purposes.
`A database 30 is provided to support the server 20 to host a
`plurality of synchronized contact infonuation lists and other
`related data. A registered user normally has a list of contacts
`(a.k.a., a circle of contacts). some or all of the contacts may 35
`also be registered users with the server 20. A record is created
`for each of the contacts. According to one embodiment. with
`proper configuration, one user updates some o.fllis/her own
`record (e.g., a profile or contact infonnatiou). those list him/
`her as a contact will automatically receive the update with or 40
`without the knowledge that this contact has updated some of
`his/her data.
`Depending on implementation, the database30 may be part
`of the server 20, distributed among diiTerent computing
`devices or remotely located from the server 20. Terminal 45
`devices 10, 12, and 14 representing a plurality of devices that
`may communicate with the server 20. An example of these
`terminal devices includes, but may not be limited to, a cellular
`phone, a PDA (personal data assistant), a PMP (Personal
`media player), and a computer. all having network capability. 50
`A user with any of these terminal devices may communicate
`with the server 20 to capture or obtain images of business
`cards and upload the images to the server 20 . .It should be
`noted that a business card or business cards are used through(cid:173)
`out this description herein, those skilled in the art understand 55
`that other media (e.g., a webpage, a newspaper page) contain(cid:173)
`ing contact iuformation or iufonnation a user desires to enter
`into his/her account shall also be included.
`The user may synchronize, manage, update or download an
`updated address book maintained on the server 20 specifi- 60
`cally for the user to a cbosen device (e.g., a PC nmning
`Outlook or Yahoo email, or a PDA). The server 20 is config(cid:173)
`ured to comnumicate with devices being used by a registered
`user to synchronize respective address books residing locally.
`For example. as shown in FIG. 1B, a registered user may use 65
`Microsoft Outlook 102 (i.e., an email application) to receive
`work related emails, a Webmail 104 (e.g., Yahoo email) to
`
`6
`receive personally related emails, a company provided cellu(cid:173)
`lar phone 106 for work-related calls, and a private cellular
`phone 108 for calls with family members or friends. Through
`an account 110 registered with the server 20, the user may
`cause each ofthcseemail tools and devices 102, 104, 106 and
`108, collectively referred to as devices or sources, to be syn(cid:173)
`chronized with the server 20.
`The account 110 includes contact information contributed
`respectively from these devices 102, 104, 106 and 108. For
`exaJ11ple, the registered user may have used any of these
`devices 102, 104, 106 and l 08 to couummicate with a contact
`nruned "John Smith". As a result, each of the devices 102,
`104, 106 and 108 keeps fractional contact information ofJohn
`Smith. For example, Outlook 102 keeps some of a profile of
`"John Smith" as John Smith may have entered some infor(cid:173)
`mation in his email setting. The profile may include his title,
`company name, company address, his company email
`address, phone and fax numbers. The Webmail 104 has his
`private email address as the registered user may have
`exchanged emails with John Smith on matters other than the
`work. Likewise, the cellular phone 106 is often used to speak
`with John Smith about the work, hence remembering his
`work cell phone number, and the cellular phone 108 receives
`sometimes calls from John Smith on his home phone. lu other
`words, each of the devices I 02, 104. 106 and 108 maintains
`fractional contact information about John Smith.
`As will be further described below, each ofthedevices 102,
`104, 106 and 108 may be configured to syncllfOiliZe with the
`server 20, uploading respective local address books having
`fractional contact information to the server 20, where the
`server 20 consolidates or process the received fractional con(cid:173)
`tact information to form a complete entry 112 with user
`entered data (e.g., a short profile) in an address book for the
`registered user. Such an address book may be synchronized to
`be remrned to any of these devices 102, 104. 106 and 108 to
`supplement the original local fractional contact information
`or downloaded to a new or another device being used by the
`registered.
`It should be noted that if one of these devices 102, 104, 106
`and 108 acquires full con