United States
`(19)
`(12) Patent Application Publication (10) Pub. No.: US 2009/0300525 A1
`(43) Pub. Date:
`Dec. 3, 2009
`JOLLIFF et al.
`
`US 20090300525A1
`
`(54)
`
`METHOD AND SYSTEM FOR
`AUTOMATICALLY UPDATING AVATAR TO
`INDICATE USER’S STATUS
`
`(21) App1.No.:
`
`12/127,349
`
`(22) Filed:
`
`May 27, 2008
`
`(76)
`
`Inventors:
`
`Maria Elena Romera JOLLIFF,
`Vista, CA (US); Samuel Jacob
`HORODEZKY, San Diego, CA
`(US); Tia CHUNG, San Diego, CA
`(US); Kameron KERGER, San
`Diego, CA (US); Gregory James
`BROWN, PoWay, CA (US); Todd
`Jeffrey J OHNSGARD, Alpine, CA
`(US); Joseph Jyh-Huei HUANG,
`San Diego, CA (US); Ankur
`JALOTA, San Diego, CA (US);
`Devender YAMAKAWA, San
`Diego, CA (US); Jadine Naomi
`YEE, San Diego, CA (US); Scott
`Alan LEAZENBY, San Diego, CA
`(US); Chad Andrew WILLKIE,
`San Diego, CA (US)
`
`Correspondence Address:
`QUALCOMM INCORPORATED
`5775 MOREHOUSE DR.
`SAN DIEGO, CA 92121 (US)
`
`Publication Classi?cation
`
`(51)
`
`Int. Cl.
`G06F 3/048
`
`(2006.01)
`
`(52) US. Cl. ...................................................... .. 715/764
`
`(57)
`
`ABSTRACT
`
`A cellular or Wireless mobile device includes a one or more
`sensors and a processor con?gured With software to receive
`data from the one or more sensors, calendar data and device
`settings, compare sensor, calendar, device settings data, and
`an authorization level of a requesting user to avatar selection
`criteria, and select an avatar based upon the comparison. By
`correlating sensor data, calendar data and device settings to a
`user’s current status, the avatar selection criteria enables a
`processor to automatically select an avatar that re?ects the
`user’s current status. Others then can be informed of the user’s
`current status by accessing the user’s avatar.
`
`261
`W
`
`202
`
`204
`
`1
`
`Google Inc., Nest Labs, Inc., and Dropcam, Inc.
`GOOG 1005
`IPR of US Pat. No. 8,315,618
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 1 0f 35
`
`US 2009/0300525 A1
`
`20‘?
`
`202
`
`203
`
`204
`
`2
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 2 0f 35
`
`US 2009/0300525 A1
`
`N;
`
`6;
`
`N GE
`
`we
`
`3
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 3 0f 35
`
`US 2009/0300525 A1
`
`394
`
`as
`
`389
`
`.3911‘
`
`M m -»~
`
`Noise
`.352
`
`Temp
`33-
`
`Breath
`Qié
`
`'
`
`GPS
`£53
`
`Camera
`
`Acce?er
`
`WW5
`3.56
`
`"
`
`SRWTX
`3&1
`
`HS. 3
`
`4
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 4 0f 35
`
`US 2009/0300525 A1
`
`40'!
`I {3051 Sensms
`
`Shack Salem-a1"
`
`4-0-3 7 1 Check Settings
`
`
`
`494. ' ‘
`
`I
`
`
`
`
`
`DetermineAvatar to- Dispiay @8125! cm Sensor‘Uaia,
`
`
`
`E '
`
`Calendar‘, anti
`Sattings
`
`i
`
`Dismay Avatar
`
`5
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 5 0f 35
`
`US 2009/0300525 A1
`
`Mehiie Dev-ice
`
`Samar
`
`Poi-E Sea-users
`
`4021
`
`Chesk
`Calendar
`
`420
`Receive
`Seiecied? f
`Avatar
`
`Chsck Settings
`
`insert avatar I430
`into webpage
`
`Receive
`Request
`
`Transmit
`Avatar
`
`Access
`Webpage
`
`r441
`Display Avata r1
`
`3......
`
`mwwnnw
`awmquwwn
`
`2:1
`, @ i 33
`
`
`
`‘warns: “ 8 8
`
`Store received
`data in
`Parameter
`Tame
`
`45 A C.) r)
`
`?valuate
`Parameter
`Taie
`
`411. 1 Safest Avatar
`to Dispiay
`
`415 1 Transmit
`Selected
`Avatar
`
`6
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 6 0f 35
`
`US 2009/0300525 A1
`
`mcowmcmm
`hmamammma»
`322g
`5E3.
`
`@202
`
`mun-w
`
`n39
`
`£93 £5
`
`ENE OZ
`
`“raw
`
`E95
`
`muomv
`
`?QE w Emmi,
`
`7
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 7 0f 35
`
`US 2009/0300525 A1
`
`
`
`
`
`
`
`b?mwé ac?m?m kmnm??g hwwzmmmm .mEmh 33¢ Em? 3E2 mmw.
`
`
`
`
`
`
`
`
`
`
`
`M60 ‘Em hum mEFwwP E3 awning m m 0 25m “Em 52m ‘$500 5mg
`
`
`
`
`
`
`
`
`
`xwmhmmmmou, .55 25 @5 mn on E022 m. w. @ Emmm ‘haw ?ocmmmteu {33w
`
`
`
`mEmmhmoucm 25 E6 m?mmzmuuow mh , Eoucm; m m‘ a Emmm ‘Em mnwm?mhmuunw“ r} mww
`
`
`
`
`
`
`
`wwahmxm n32 ‘Em Egg, mWE “Em Emnm n3? EEG A56 3 mg
`
`
`
`
`
`i ,, ; , x ., . ., . . .. EEG . ,,
`
`
`
`
`
`
`
`
`
`
`
`nméw ‘Em \Em EmméaoQ w W. which.” Eaucm.» Pm. a. ?mm 25m $9.: @ MEox i: m 5
`
`
`
`
`
`
`
`
`
`wémmsm Em? 0mm“ gwngou 3w Elm» Eowc? & Nd imam mg? ?E a 62mm 3+ 5
`
`
`
`
`
`
`
`
`
`
`
`mgqgogw use“ mam “mam mama“ uwwotmu .m mso Emtm an an.“ c9: on Mimi 1) ME
`
`
`
`
`
`
`
`
`
`
`
`
`
`x824. an own“ égcmou ‘6w 5.3 Emuc? .m wvm Baum nnamiv $5 0 “3E6 i; Q Wm
`
`
`
`
`
`
`
`
`
`
`
`
`
`mcwcgm n32 ‘5m gum we? .uwwocwu .m Tm. Emam ham 5E wn iuw? .iwvw
`
`
`
`
`
`
`
`
`
`
`
`
`
`mcwmm use“ mam 3m 3. on Eomc? m m o vrmm an 3A ‘ uc?s?wmm {3mg
`
`
`
`
`
`
`
`
`
`95 . Emma \Em ‘?aw PEN 803$ hm N6 imm Qua? 5% o 7
`223$ 3% ‘Em @Qw aim mw? EDEQ @ N -0 as? a358, ,4: Km
`
`
`
`
`
`
`
`@225 n32 ‘Em @m mu 2 Eowc? m N m ham gown @nwrm} i. Nmw
`
`
`
`
`
`
`
`
`
`. a 5 V .. . i .. i w 7 ‘ umwmmzh E55 (1 6mm
`
`
`
`
`
`
`
`
`
`‘ V‘ \ i i 1 .,..; a ‘ EE.,N,.W ,
`
`
`
`.. i i , i . :QEQ . . .
`
`
`
`i y a . . _ q,‘ . . zaEa
`
`
`
`: i . i , . k ,, A. i5?
`
`
`
`‘ ‘i i i . Y, , i 1. ‘ E5 o
`
`gm
`
`8
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 8 0f 35
`
`US 2009/0300525 A1
`
`Maser-swans
`avatar far
`caiibratimn
`
`Uaer initiates
`aaiibration
`
`‘Record sensn'r
`data and
`settings
`
`614
`J".
`
`End naiibra?sn
`
`Anaiyze
`se nsm" data
`
`Store anaiyzed
`sensor data
`and settings in‘
`criteria tabie
`
`6%
`
`V
`Transmit
`criteria tame to
`server
`
`622 f
`
`FEG. 6c
`
`9
`
`

`

`Patent Applicati on Publication
`
`Dec. 3, 2009 Sheet 9 0f 35
`
`US 2009/0300525 A1
`
`M is Device
`
`Poi! Sensors
`
`Check
`Caiendar
`
`Receive
`SEBilECtEt?
`Avatar
`
`JAZU
`
`Check Settings
`
`insert avatar
`ientn webpage
`
`439 f
`
`f431
`
`I
`
`l
`
`4-40
`f
`
`Access
`
`' "
`
`Webpage
`
`I432
`
`_,
`
`r441
`
`gigpl‘ay Avatar
`
`Receive
`Request
`
`Ti'ansméi
`Avatar
`
`Store received
`data in
`Para-meter
`
`Compare
`Parameter Table
`
`Select Avatar
`"to Display
`
`Transmit
`Seiecied
`Avatar
`
`10
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 10 0f 35
`
`US 2009/0300525 A1
`
`Séiver
`
`Ping i‘vio-biie
`Device
`
`Devi‘gg
`
`Receive
`'
`#29
`Selected I
`Avatar
`
`insert avatar 1’438
`into webp-age
`
`‘P63 Sense-rs
`
`402 ,1 Check
`Calendar
`
`40% Check Settings
`
`Store received
`4091
`data in
`Parameter
`Table
`
`Campa re
`F’arameter
`Tale
`
`Receive
`Request
`
`412k Seieci Avafa;
`to Disgay
`
`Transmit f4
`
`~ 32,
`
`r440
`Access
`Webpage
`
`{"441
`Dis Ea Avatar
`
`Transmit‘
`Selected
`Avatar
`
`11
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 11 0f 35
`
`US 2009/0300525 A1
`
`.
`
`3
`
`431W; Receive
`Request
`
`g?i'jil?
`
`443..
`
`1 Access
`Webpage
`
`40
`
`h“ Poi? Sensors
`
`"
`
`‘4621
`
`Check,
`Calendar
`
`4031
`
`11
`4551
`» pligetiggiw
`
`N
`
`_‘
`
`Receive
`. 42g
`Se?ected f
`Avatar
`
`Check gettings
`
`insert avatar I433
`
`_
`Store received
`$091‘
`datajin
`Paramater
`Tabte
`
`.
`
`41 ‘
`1
`?ampare
`611 Parameter
`
`'
`
`Table
`
`4321; SeiectA‘vaiar
`to Display
`
`4151 Transmit
`
`Selected
`Avatar
`
`We Webpag?
`
`_y
`Transmit
`
`Avatar
`
`_
`
`_
`
`>
`
`' msplay Ava’iw
`
`r 4M
`
`FIG. 9
`
`12
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 12 0f 35
`
`US 2009/0300525 A1
`
`I
`
`Device
`
`4011
`
`---
`
`Pol! Sensors
`
`4021
`
`Check
`Calendar
`
`49
`
`31 Check Settings
`
`_
`
`4091 Store‘receiveti
`daiain
`§4PQWQQ€
`E
`5
`Parameter
`:Qeiay:
`Tame
`: 450
`%
`2
`a
`
`Transmit
`J
`parameter
`........
`*
`4W1 Tabie
`
`<
`
`-
`
`_
`
`-
`
`i
`
`P223388; {41?
`Tabie
`
`l
`Compare I41 8
`Parameter
`We
`4,
`
`SeiestAvaiar fmg
`to Dispialy
`
`Ensert avatar f43n
`into webpage
`
`431-1
`
`%
`Recawe
`Request
`
`I“
`'
`
`44
`Ox ACGQSS
`Webpage
`
`FEGv 1O
`
`432 i
`
`V
`
`V
`
`V ,.
`
`“L y?lligjt
`‘
`‘
`
`~ Disp-lay Avatar’
`
`13
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 13 0f 35
`
`US 2009/0300525 A1
`
`Mo ii Device
`-
`491'L
`W P01’! Sensors i;
`
`4921
`
`Check,
`?aigndar
`
`!
`
`7
`
`‘
`
`4Q’
`
`31 Check Settings
`$
`4891 Stare received
`f" “"3;
`data in
`3'
`‘Parameter
`g
`:Deiayi
`Tame
`3 450 2
`I
`> ----- >~
`
`,7
`
`3
`
`m 6
`Transmit
`1 Parameter
`Table
`
`'
`
`EFEGQ 31,5;
`
`Reguesting '
`
`'
`
`'
`
`Qék'i?g
`
`.
`
`Pifgig; f“?
`Table
`l
`413
`Compare
`Parameter f
`Tame
`
`SeieciAvat'ar f mg
`to Dismay
`
`%
`
`insert avatar I438
`into webpage
`
`%
`R ,
`
`ecewe
`R-ecquest
`
`I431
`
`-
`' '5
`
`r440
`
`A
`
`ccess
`Webpage
`
`r441
`“
`%
`T Q
`‘
`I432
`"Em" mm? Gispiay Avatar
`vatar
`
`14
`
`

`

`Patent Application Publication
`
`. 3, 2009 Sheet 14 0f 35
`
`US 2009/0300525 A1
`
`Mebil Devi-ca
`
`P01! Sensors
`
`Check
`Caiendar
`
`Check $a-ttings
`
`‘Store received
`_ data in
`Parameier
`Table
`
`41% Transmit
`Parameter
`Table
`
`Reg‘ uesting '
`
`1'
`
`.
`
`‘ 9mg Mubiie
`Device
`
`f4 55
`
`Ce; mpare
`Parameter
`
`Select: Avatar
`to Dismay
`
`énsertavatar
`" into webpage
`
`Receive
`Request
`
`Transmit
`Avatar
`
`Access
`Web page
`
`fili-i
`Dispiay Avatar
`
`15
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 15 0f 35
`
`US 2009/0300525 A1
`
`Mile Device
`
`Sewer
`
`4311 Receive
`Request
`
`7
`
`Access
`Webpags
`
`401 I
`
`1 Foil ‘Sensom
`
`.
`
`i
`
`I‘
`
`pi'fggegggg?e f4
`
`--
`
`,
`
`~ 55
`
`4021
`
`.-
`Check
`Calendar
`
`.
`
`~~ ~.
`
`41 y
`Reaeive
`Parameter I
`Table
`
`40: .
`31- Check Settings
`
`418
`(36mm
`Parameter f ‘
`Table
`
`14-O§~§—~k Store Data in
`Parameter
`
`Eeiect Avatar
`to, Bis-may
`
`‘379
`
`Table
`
`_
`
`Trasmit
`M
`61 Parameter
`'Tabte
`
`insert Avatar f430
`into Webpaga
`I
`
`5
`
`.... ,,
`
`,i
`
`{"441
`
`Wansmit
`
`Avatar
`
`.
`
`PEG; '13
`
`r
`
`.
`
`~ Dismay Avatar
`
`>
`
`16
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 16 0f 35
`
`US 2009/0300525 A1
`
`Reg uesting '
`
`" "
`
`‘ Device
`
`5311‘ send emaiii or
`SMS message ‘in use:
`
`Receive Ava-tar File
`
`Dispiay Avatar
`
`Pol‘! Sensms
`
`Check Caiendar
`
`‘Check Settings
`
`in Param?ter Ta'bie
`
`VCnmpare aramete-r
`‘Table
`
`Dispiay
`
`can, email, 8M8
`
`Avatar file
`
`FEG‘ 14a
`
`17
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 17 0f 35
`
`US 2009/0300525 A1
`
`M0 ii? Davina
`
`pun Sensurs
`
`Gheck, Caienciar
`
`Reguesting " "
`
`?evise
`
`5
`
`Gail, send emaii or
`SMS message is user
`
`Check Settings
`
`SUG?L
`
`TReceive Seiested
`Avatar identi?er
`
`Stare received
`data in Parameter
`
`’
`
`>
`
`‘ Tabie
`
`(Zapata
`Parameter Tame.
`
`Selectvatartu
`Qispiay
`
`4511 “iiRecéiv Phcnei
`Data caii, emaiiy
`SS
`
`5041 Transmit séiéiited“
`Avaiar identi?er
`
`595%L Receive Request __ _
`
`farSeiect'ed Avatar fiie;
`
`..._
`.."iar File m1
`Avatar identifier in Eocai “ft-:1
`
`__
`
`__ “
`
`memgyy? I
`
`..
`
`.
`
`.
`
`508
`Q Request
`i Seiected I
`Avatar fiie
`
`-
`
`463
`Rsceive
`Seiecied I Yes
`Avatar ?ier
`
`4621 Transmit‘ Seiecteci
`Awaits; ?le
`
`4411
`-
`
`I
`,
`.i
`Display Avatar
`
`18
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 18 0f 35
`
`US 2009/0300525 A1
`
`Reguestigg
`Device
`
`Pull Sen'sers
`
`21 Check Calendar
`
`
`
`40 NU
`
`
`
`i Check gattings
`
`‘10% Stare reciveddata
`_ in Farameter Tabie
`
`@101 Compare '
`Tabla?
`
`41 1:1 Selact vaiar m
`Display
`
`sail, emaik', 8M8
`
`_ Call, send emaii ersms
`message to user
`
`l
`
`l l‘ ‘X
`
`.......................................................
`
`Damn-‘lead Avatar File
`
`Fig '5 53
`
`Display Avatar
`
`19
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 19 0f 35
`
`US 2009/0300525 A1
`
`Moiie Device
`
`Pol! Sensors
`
`Check Calendar
`
`Check Settings
`
`“Slime recived data
`in Parameter Table
`
`. .
`
`
`
`u. astin * Devilcg
`
`4601 Cat], send emai! or sms
`message to user
`
`.?eceive 8eiected
`Avatar identi?er
`
`_
`
`
`
`atar Fiie iD‘d Avatar identifier in
`
`Reqmest
`Seiected
`Avatar file 5
`
`- 5G8 I
`
`Receive
`Selected
`Avatar ?le
`
`Dispiay Avaiar
`
`4101 Campers}. arametef
`Tabie
`
`4111 Select vatai'r to
`
`4611
`
`can. email., 8M5
`
`misra nsmit Selec’ted
`Avatas' idenii?er
`
`
`
`n?eceive ?equest for Selected Avatar?ie ‘
`
`Avatar ?ie
`
`20
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 20 0f 35
`
`US 2009/0300525 A1
`
`Mghiia Device
`
`
`4‘5 .
`
`402
`
`
`
`"""
`IIIII
`Ga“, send emaii or sms
`
`: messae in user
`cattemaELSMS
`
`
`
`
`
`
`:
`
`,,
`
`,
`,,,,,,
`Ciheck Caievndar
`
`403
`
`................................:................................
`Check Settings
`
`
`
`
`
`........................
`
`41 “i
`
`...........WWII?)
`
`4 ,3 F
`
`462
`
`
`............................ ......... x.
`Traniggfiiéiciw ..................................................................
`Receive Avatar File
`5:
`
`
`
`HQ. 1528
`
`Dis-play Avatar
`
`21
`
`21
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 21 of 35
`
`US 2009/0300525 A1
`
`
`
`Moifiiie Device
`
`‘
`
`‘ ReceiVe PhaneIData :
`
`caLI emaii SMS
`
`. FarameterTabIe
`
`
`
`Stare received data in
`
`
`
`? Compare Parameter
`Table
`
`5
`
`i
`
`._ 3. eat Avatar It)
`
`
`
`Gail, send emaii or arm
`messae is user
`‘
`
`
`
`
`
`
`
`
`Receive Selected
`
`
`Avatar identifier
`
`
`
`
`
`.. --fivatar FiIe ED {:1
`
`
`Avatar identifierin iecaI _ _"__-...
`
`
`
`508
`
`Request
`SeIected.
`
`Aivatarr fiie :
`
`.
`
`‘
`
`Disk—:1 -
`
`ransmat e ecie
`
`Avatar Identifier
`
`Receive f
`
`SeIected
`
`* Avatar fife i
`
`é: Receive Reguesifov
`Seieci‘ed Avatar file
`
`Transmzt Setectea
`
`Avatar file
`
`PEG. 1533
`
`22
`
`22
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 22 0f 35
`
`US 2009/0300525 A1
`
` Reg uestihg ‘
`
`'4
`
`'ngéce
`
`........................ Calh send emai'ierSMS
`messae to user
`
`
`
`
`
`'
`
`
`
`..........
`
`"
`
`4*. 0,1
`
`...............................
`................. ............
`Poll. Samara
`
`
`
`403
`
`416'
`
`5
`
`Table
`
`Transmitparameter
`
`.............................
`
`HQ. 17
`
`23
`
`
`
`23
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 23 0f 35
`
`US 2009/0300525 A1
`
`40:
`
`,§
`
`Pol! Sensors
`
`Check Saiendar
`Check Authorizaticn Lave}
`
`402‘?
`
`403
`
`5m ,
`
`7,
`_
`i
`,
`C heck Settings
`
`55
`
`404
`
`
`
`’1‘........
`5 Dispiay basedan
`Sensur Data,
`Calendar, Settings,
`5»
`5
`and Authorization
`
`,flkeye¥.HMH “m3:
`
`.....
`
`5
`
`
`
`Disp§ay Avatar
`
`24
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 24 of 35
`
`US 2009/0300525 A1
`
`33¢:qumwuutafiaa,
`
`8»
`
`wzfimfim
`
`5%.“me.
`332mm
`
`33%33.0
`
`,xoma.
`
`mmwman”
`
`isw
`
`25
`
`25
`
`

`

`Patent Application Publication
`
`Dec.
`
`3, 2009 Sheet 25 0f 35
`
`US 2009/0300525 A1
`
`,m
`
`
`
`
`“ESQcomwmfififisfl$893KEnema”?$0530.88333¢
`
`
`
`.umo“3.38009;meEmam.mm.on8038.mwasEmtmmummv”88Q”BEG.
`
`
`
`
`Immuxmmglmwn.WEotzm...mmic...8w,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
`
`
`
`.Hwofigg,mmanta?€onsz_mm
`
`
`
`33mg2QOPMoh...
`
`mom
`
`26
`
`....A...
`
`88
`
`
`
`km.,xaEQ6on.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`HmufigmuhmYm.._.....:8.888.?yam;.
`
`mg.6?“
`
`26
`
`
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 26 0f 35
`
`US 2009/0300525 A1
`
`Userseiecls
`
`‘
`
`61E}
`
`..
`_........... 55:
`i
`5
`
`
`avatar far
`caii‘bration
`
`:
`
`“ 313
`
`
`
`
`
` , 615
`
`
` User initiates
`
`calibration
`
`Record sen-so
`data and
`:
`
`Settings
`
`
`
`
`Set
`
`Requesting
`User
`Autharization
`
`j
`
`Levei
`
`.................
`
`
`
`
`
`
`;
`sensm“ daia
`nd settings in
`
`
`criteria tabie
`
`
`m5
`
`620
`
`, 61B
` Anaiyze
`
`5’
`sews-or data
`
`-:.:5j;n.-
`
`
`
`‘ 622
`5
`Transmit
`criteria table to -
`
`server
`i
`:
`
`
`
` 5
`
`HQ ’19::
`
`27
`
`27
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 27 0f 35
`
`US 2009/0300525 A1
`
`
` Egg uesting '
`
`'
`
`Device
`
`
` 417
`Parameter
`
`Receive
`
` Access
`
`Webpage
`
`Check
`Authmization
`
`
`
`table
`
`3,,
`
`.. ..
`
`' Ste re renewed.
`:
`{iata in
`
`Parameter
`
`
`
`
`
`
`Transmit
`Patameter
`Tabie
`
`.....................
`
`g
`
`Store
`Authorization
`Le-v‘ai to
`Parameter
`
`‘ 592
`
`5
`
`~
`
`Seiecmvatar
`
`. 411
`
`ta Dispiay
`
`43
`
`HG 23
`
`432
`
`insert avatw
`into Wabpage-
`
`Dlspiay Avatar
`
`Transmit
`Avatar
`
`28
`
`28
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 28 of 35
`
`US 2009/0300525 A1
`
`
`
` Reguesfin‘g''
`
`Qavice
`
`
` Receive
`Parameter
`
`41?
`
`Table
`
`Receive
`Request
`
`...................
`
`_
`
`.1
`
`40.1
`
`.........................................
`
`
`
`.3tore received
`:
`(3333 in
`
`:
`
`Parameter
`
`
`
`
`arameters“~
`
`
`
`
`
`
`418‘
`
`
`
`Tiansmit
`Parameter
`
`
`Tame
`
`' Data
`
`.01
`.............:2
`
`V
`Send. 7
`Authgfizafion
`
`‘
`
`Authorization
`
`Lave!
`
`:
`
`5
`
`5132
`
`‘
`
`Store
`Authorizatian
`Lave! 320
`Parameter
`
`;
`
`,.
`
`table
`
`SeiectAvatar ;. 4H
`to Display
`
`insert avaiar
`mm webpage
`
`, 430
`
`................... 5 432
`
`a..........................................
`
`
`
`29
`
`29
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 29 0f 35
`
`US 2009/0300525 A1
`
`
`Méiygie [Davies
`
`Requesting '
`Device
`
`Check,
`Caienclar
`
`>
`
`.
`
`
`Receive
`
`417
`
`Ta me
`
`
`Check
`‘ Auiharization
`
`
`;
`
`
`
`
`Parameter
`
`Store received
`
`:
`
`data in
`Parameter
`
`:
`
`Table
`
`41;
`
`Transmit
`
`552-
`
`5
`
`5
`
`%
`
`Stare
`Autharization
`Lev-e: t0
`Parameter
`
`table
`
`41 ?
`
`fl
`_
`.
`FEG- 22
`
`4-30
`
`432
`
`insert avatar
` into-webpage
`
`4’
`Transmit
`
`:
`
`44’!
`
`i ...................
`
`......................'...................
`.,
`v
`-
`DaspiayAvatar
`
`30
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 30 0f 35
`
`US 2009/0300525 A1
`
`
`
`Receive
`Request
`
`44g I
`..............
`
`--
`
`......................................,-
`ABBESS
`Webpage
`
`Authorization
`
`5
`
`Data
`
`431
`
`:
`1
`3f
`
`f
`
`Ping Mobile
`: Device w;
`Authorization
`have!
`
`‘
`
`.
`7
`456
`
`.
`3
`
`-
`
`Raceive
`Selected
`
`5-
`
`-420
`
`insert avatar
`into Webpage
`
`"30
`
` data in
`Parameter
`Table
`
`
`
`E........
`........
`
` ‘
`'5
`i
`Avatar
`
`
`
`
`
`.. Dismay Avatar:
`i5
`-
`.
`
`Tabie
`
`,. 32
`
`F356; 23}
`
`_
`Select Avatar
`to Dispiay
`
`Transmit
`Seiected
`
`Avatar
`
`,,
`
`..
`
`...... . .....
`
`31
`
`4:132
`
`410 I
`
`,
`41.2.
`
`415
`
`31
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 31 0f 35
`
`US 2009/0300525 A1
`
`
`
`Reguesting ’
`Device
`
`'
`
`
`, Chefik Calendar 403
`
`De ay-g
`
`'uua .- nun
`
`Check Settings
`
`
`,
`Storé. received data :
`
`in: ParameterTabie :
`
`.......................
`451 Receive PhonelData
`
`cali email, 8M8
`
`
`
`433 -
`
`.
`
`Cammi
`
`
`8M8 messa e to user
`
`
`
` Level
`
`Send Authorization
`
`Data
`
`5132:
`
`'
`
`5
`
`Stare Authenzataon
`Leveito Parametur
`
`tame
`
`411 ‘
`
`SelectAvatartD : Disia
`
`432
`
`
`
`Avatar fiie
`
`"""
`
`Receive Avatar Fiie
`
`
`
`Display Avatar
`
`32
`
`32
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 32 0f 35
`
`US 2009/0300525 A1
`
`
`
`Devicg
`
`CallfieIfcfiemaiIDr
`
`
`8M8 messae to user
`
`
`i
`.................................. .3:
`I
`samd AUtthZfltian
`
`
`51:1ng 40 ........................... ............................
`.2
`Data
`
`2450:
`Check Settings
`7
`s ..............................................................3
` Store Ieceived data
`Avatar identifier
`
`
`a
`
`Receive Selected '
`
`
`‘
`
`In Parameter Tabke
`
`I Recewe PIIDnefData. :
`.jCaII emaa 31115
`
`597 ”Check Authorization? ________
`N0
`5
`5
`Level
`
`5
`
`
`
`= “vat“ We IP’d‘
`
`__ _' AvataI IdenI‘ifier In
`
`Irma! memory? .. --
`
`_
`
`__
`
`V.
`
`Request
`SeIecIed
`
`vatarfiie
`
`Receive
`Selected
`
`'
`
`I
`Yes
`
`Store Autfiorization
`
`
`
`I
`LeveI to Parameter
`
`
`
`table
`
`
`
` Avatar file
`SelectedAvatar flit?
`
`SeIect Avatar to
`
`_ DIS:Ia
`
`534
`
`Tfansmlt 831931te
`Avataridentifier
`
`5
`
`535 I IReceiva Requestfor .
`
`_
`
`462 '
`
`Iansmst Seiecied
`
`
`Avatar II I9
`
`I .......................................................i
`
`441 I
`
`
`..............................i
`..................
`Dismay Mata!“
`
`33
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 33 0f 35
`
`US 2009/0300525 A1
`
`
`
`453‘
`
`
`
`3 Receive Phoneiflata
`can amaii SMS
`
`.
`
`
`
`Bevice
`
`................................. Iflaik send emaii or SM
`messae to user
`
`
`
`
`
`Z
`
`
`
`Sand Amihoriz‘afimn
`
`Data
`
`50‘!
`
`'
`
`Check Autharization
`
`Level
`.,
`
`
`I
`
`
`
`Check Calendai
`
`
`
`
`
`Eheck Settings
`
`4‘3
`
`
`
`
`Z..................‘3 Table I
`
`
`
`410-
`
`"""
`
`
`
`
`41 ,fi
`
`41'»
`
`.........................
`
`
`Disla »
`
`
`
`
`ransmltSeI/ected V'
`Avatar file
`
`
` Recéive Avatar Fife
`
`34
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 34 0f 35
`
`US 2009/0300525 A1
`
`
`
`Receivephonemata
`
`
`
`
`Z
`
`caII emaiI SIV‘IS
`
`Z
`
`
`
`Check AtharIzaticsn;
`. LeveI
`..
`.
`Z
`
`
`PDII Sensors I
`
`Z
`
`
`
`Store recewed da‘IaIn
`
`PaI'ameter TabIe '
`
`
`
`
`41-9
`
`Z
`
`'''''
`
`
`
`
`
`
`SeIeCI PIvatar to
`
`DisIa
`Z
`TransmIISeIected
`Avatar Identifier
`
`i
`
`__
`
`5
`
`5
`
`erut for
`Z SéIgcted Pavatar‘fiie
`
`IranSmII Seliected
`
`
`'I‘aIIIe
`
`
`I
`
`VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVI .‘Cali send emaii or arms
`messa'e teaser
`
`
`
`
`
`Send Authmmatiofl
`
`I
`
`Data,
`
`Racewe Seiected
`Avatar IdenIifiar
`
`
`
`; so?
`gI vatar FIIe ID’d II
`,.
`
`
`AvaIaI‘ Identifierm Penal
`V.
`
`
`-
`--
`memory?
`_.
`..
`Z
`'
`
`
`
`Request
`SeIecIed
`
`‘
`
`Avatar IIIe
`
`:
`
`......
`
`Receiéve
`‘Seiected
`Avatar We
`
`i
`
`'
`
`.
`Yes
`
`DIspiay AvaIar
`
`FIG, 25b
`
`...................................................................
`
`35
`
`35
`
`

`

`Patent Application Publication
`
`Dec. 3, 2009 Sheet 35 0f 35
`
`US 2009/0300525 A1
`
` MObéie Device
`
`Device
`
`461
`
`
`
`V
`5 Ca“, send email Dr
`5
`3M3 messae is user-
`
`
`
`
`[Ha ..
`
`§
`
`'
`
`40"!
`
`,
`
`482
`
`493% g
`
`409
`
`
`Tame
`
`
`
`er Table
`_ Mamet
`
`
`
`
`‘
`
`'
`
`.3
`
`
`
`Dismay Avatar
`
`36
`
`36
`
`

`

`US 2009/0300525 A1
`
`Dec. 3, 2009
`
`METHOD AND SYSTEM FOR
`AUTOMATICALLY UPDATING AVATAR TO
`INDICATE USER’S STATUS
`
`FIELD OF THE INVENTION
`
`[0001] The present invention relates generally to providing
`a current indication of a user’s status or activity Via a com-
`puter generated avatar.
`
`BACKGROUND
`
`In the computing sense, an avatar is a virtual repre-
`[0002]
`sentation of a computer user. The term “avatar” can also refer
`to the personality connected with a screen name, or handle, of
`an Internet user. Avatars are often used to represent the real
`world user in the virtual world of computing. Avatars can be
`three-dimensional models used in virtual reality applications
`and computer games. Avatars can also be a two-dimensional
`icon (picture) used in Internet forums and other online com-
`munities, instant messaging, gaming and non-gaming appli-
`cations. Avatars may be animated or static.
`[0003] The term avatar dates at least as far back as 1985,
`when it was used as the name for the player character in a
`series of computer games. Recently, the usage of avatars has
`spread in popularity and avatars are now often used in Internet
`forums. Avatars on Internet forums serve the purpose of rep-
`resenting users and their actions, personalizing their contri-
`butions to the forum, and may represent different parts oftheir
`persona, beliefs, interests or social status in the forum.
`[0004] The traditional avatar system used on most Internet
`forums is a small (96x96 to 100x100 pixels, for example)
`square-shaped area close to the user’s forum post, where the
`avatar is placed. Some forums allow the user to upload an
`avatar image that may have been designed by the user or
`acquired from elsewhere. Other forums allow the user to
`select an avatar from a preset list or use an auto-discovery
`algorithm to extract one from the user’s homepage.
`[0005]
`In the instant messaging (IM) context, avatars,
`sometimes referred to as buddy icons, are usually small
`images. For example, IM icons are 48x48 pixels, although
`many icons can be found online that typically measure any-
`where from 50x50 pixels to 100x100 pixels in size. A wide
`variety ofthese imaged avatars can be found on web sites and
`popular eGroups such as Yahoo! Groups. The latest use of
`avatars in instant messaging is dominated by dynamic ava-
`tars. The user chooses an avatar that represents him while
`chatting and, through the use of text to speech technology,
`enables the avatar to talk the text being used at the chat
`window. Another form of use for this kind of avatar is for
`
`video chats/calls. Some services, such as Skype (through
`some external plug-ins) allow users to use talking avatars
`during video calls, replacing the image from the user’s cam-
`era with an animated, talking avatar.
`
`SUMMARY
`
`[0006] Various embodiment systems and methods are dis-
`closed which automatically update a user’s virtual world ava-
`tar to provide a more accurate representation of the user’s
`current real world status or activity. Embodiments may
`receive information from a variety of sensors located either
`within the user’s mobile device or within close proximity to
`the mobile device to provide some parameters of the user’s
`real world environment. The variety of sensors may include,
`but are not limited to a location sensor (e.g., GPS coordi-
`
`nates), a microphone for sensing ambient noise, a camera or
`light sensor for sensing ambient light, accelerometers, tem-
`perature sensor, and bio-physiological sensors such as a
`breathalyzer, heart rate monitor, pulse sensor, EEG, ECG,
`EKG, and/or blood pressure sensor. In addition, embodi-
`ments may utilize a user’s calendar data as well as mobile
`device settings to generate an updated virtual representation
`via an avatar of the user’s real world status or activity. Alter-
`native embodiments may age the user’s avatar over time so
`that a user’s avatar grows older, more mature as the user grows
`older, more mature. Various embodiments automatically
`update or change the user’s avatar as the user goes about
`his/her daily activities. Other embodiments update or change
`the user’s avatar when a request to view the avatar is made.
`The user’s avatar may be viewed in a singular location, such
`as a webpage. Alternative embodiments may allow a user’s
`avatar to be downloaded to any requesting party. Still other
`embodiments may pro-actively inform selected parties of a
`user’s current real world status or activity by sending an
`avatar.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0007] The accompanying drawings, which are incorpo-
`rated herein and constitute part ofthis specification, illustrate
`exemplary embodiments of the invention, and, together with
`the general description given above and the detailed descrip-
`tion given below, serve to explain features of the invention.
`[0008]
`FIG. 1 illustrates exemplary avatars suitable for use
`with the various embodiments.
`
`FIG. 2 is system block diagram of a system suitable
`[0009]
`for use with the various embodiments.
`
`FIG. 3 is a system block diagram ofa mobile device
`[0010]
`suitable for use with the various embodiments.
`
`FIG. 4 is a process flow diagram of an embodiment
`[0011]
`method suitable for implementation on the system.
`[0012]
`FIG. 5 is a process flow diagram of a specific
`embodiment method suitable for implementation on a mobile
`handset.
`
`FIG. 6a is an example parameter data table suitable
`[0013]
`for storing a variety of sensor data, user calendar data, and
`mobile device settings indicating the current status of the
`user.
`
`FIG. 6b is an illustrative avatar selection logic table
`[0014]
`which indicates an avatar to display based on various param-
`eters.
`
`FIG. 60 is a process flow diagram of an embodiment
`[0015]
`method for calibrating an avatar selection logic table.
`[0016]
`FIG. 7 is a process flow diagram of an embodiment
`method suitable for implementation on a mobile handset
`which conserves battery and processor time.
`[0017]
`FIG. 8 is a process flow diagram of an embodiment
`method suitable for implementation on a mobile handset
`which responds to a server request.
`[0018]
`FIG. 9 is a process flow diagram of an embodiment
`method suitable for implementation on a mobile handset
`which responds to a second user request.
`[0019]
`FIG. 10 is a process flow diagram of another
`embodiment method wherein avatar selection is offloaded to
`a server.
`
`FIG. 11 is a process flow diagram of another
`[0020]
`embodiment method wherein avatar selection is offloaded to
`
`a server which conserves battery and processor time.
`[0021]
`FIG. 12 is a process flow diagram of another
`embodiment method wherein avatar selection is offloaded to
`
`37
`
`37
`
`

`

`US 2009/0300525 A1
`
`Dec. 3, 2009
`
`a server which conserves battery and processor time by
`responding to a server request.
`[0022]
`FIG. 13 is a process flow diagram of another
`embodiment method wherein avatar selection is offloaded to
`
`a server which conserves battery and processor time by
`responding to a second user request.
`[0023]
`FIG. 14a is a process flow diagram of another
`embodiment method suitable for displaying an avatar directly
`on the requesting device.
`[0024]
`FIG. 14b is a process flow diagram of another
`embodiment method suitable for displaying a new or updated
`avatar directly on the requesting device
`[0025]
`FIG. 15a is a process flow diagram of another
`embodiment method suitable for displaying an avatar directly
`on the requesting device which conserves battery and proces-
`sor time.
`
`FIG. 15b is a process flow diagram of another
`[0026]
`embodiment method suitable for displaying a new or updated
`avatar directly on the requesting device which conserves bat-
`tery and processor time.
`[0027]
`FIG. 16a is a process flow diagram of another
`embodiment method suitable for displaying an avatar directly
`on the requesting device which conserves battery and pro-
`cessing time by responding to a second user request.
`[0028]
`FIG. 16b is a process flow diagram of another
`embodiment method suitable for displaying a new or updated
`avatar directly on the requesting device which conserves bat-
`tery and processing time by responding to a second user
`request.
`FIG. 17 is a process flow diagram of another
`[0029]
`embodiment method suitable for displaying an avatar directly
`on the requesting device wherein avatar selection is offloaded
`to the requesting user’s device.
`[0030]
`FIG. 18 is a process flow diagram of an alternative
`embodiment method suitable for implementation on the sys-
`tem.
`
`FIG. 19a is an example parameter data table suitable
`[0031]
`for storing a variety of sensor data, user calendar data, mobile
`device settings and authorization level of a user requesting an
`avatar.
`
`FIG. 19b is an illustrative avatar selection logic table
`[0032]
`which indicates an avatar to display based on various param-
`eters including the authorization level of the requesting user.
`[0033]
`FIG. 190 is a process flow diagram of an embodi-
`ment method for calibrating an avatar selection logic table
`including the authorization level of the requesting user.
`[0034]
`FIG. 20 is a process flow diagram of an embodiment
`method for selecting an avatar for display based upon an
`avatar selection logic table including the authorization level
`of the requesting user.
`[0035]
`FIG. 21 is a process flow diagram of another
`embodiment method for selecting an avatar for display based
`upon an avatar selection logic table including the authoriza-
`tion level of the requesting user.
`[0036]
`FIG. 22 is a process flow diagram of another
`embodiment method for selecting an avatar for display based
`upon an avatar selection logic table including the authoriza-
`tion level of the requesting user.
`[0037]
`FIG. 23 is a process flow diagram of another
`embodiment method for selecting an avatar for display based
`upon an avatar selection logic table including the authoriza-
`tion level of the requesting user.
`[0038]
`FIG. 24a is a process flow diagram of another
`embodiment method suitable for displaying an avatar
`
`selected based upon sensor and setting data and the authori-
`zation level ofa second user directly on the requesting device.
`[0039]
`FIG. 24b is a process flow diagram of another
`embodiment method suitable for displaying a new or updated
`avatar selected based upon sensor and setting data and the
`authorization level of a second user directly on the requesting
`device.
`
`FIG. 25a is a process flow diagram of another
`[0040]
`embodiment method suitable for displaying an avatar
`selected based upon sensor and setting data and the authori-
`zation level ofa second user directly on the requesting device.
`[0041]
`FIG. 25b is a process flow diagram of another
`embodiment method suitable for displaying a new or updated
`avatar selected based upon sensor and setting data and the
`authorization level of a second user directly on the requesting
`device.
`
`FIG. 26 is a process flow diagram of another
`[0042]
`embodiment method suitable for displaying an avatar directly
`on the requesting device based upon sensor and settings data
`and the second user’s authorization level.
`
`DETAILED DESCRIPTION
`
`[0043] The various embodiments will be described in detail
`with reference to the accompanying drawings. Wherever pos-
`sible, the same reference numbers will be used throughout the
`drawings to refer to the same or like parts. References made to
`particular examples and implementations are for illustrative
`purposes, and are not intended to limit the scope of the inven-
`tion or the claims.
`
`[0044] As used herein, the term mobile device may refer to
`any one or all of cellular telephones, personal data assistants
`(PDA’s), palm-top computers,
`laptop computers, wireless
`electronic mail receivers (e.g., the Blackberry® and Treo®
`devices), multimedia Internet enabled cellular telephones
`(e.g., the iPhone® ), and similar personal electronic devices
`which include a programmable processor and memory. In a
`preferred embodiment, the mobile device is a cellular handset
`that can communicate via a cellular telephone network (e. g.,
`a cellphone). However, cellular telephone communication
`capability is not necessary in all embodiments. Moreover,
`wireless data communication may be achieved by the mobile
`device connecting to a wireless data network (e.g., a WiFi
`network) instead of a cellular telephone network.
`[0045] As used herein, the term “server” refers to any of a
`variety of commercially available computer systems config-
`ured to operate in a client-server architecture. In particular,
`the term “server” refers to network servers, particularly Inter-
`net accessible servers, which typically include a processor,
`memory (e. g., hard disk memory), and network interface
`circuitry configured to connect the server processor to the
`network, such as the Internet.
`[0046] As used herein, the term “theme” refers to the col-
`lection of user-configur