United States Patent
`
`[19]
`
`Theimer et al.
`
`[11] Patent Number:
`
`5,493,692
`
`[45] Date of Patent:
`
`Feb. 20, 1996
`
`||I||l |||||||| Ill ||||| |||I| ||||l Illll lllll ||||| Illll ||l|| |||||| Ill ||||| llll
`USO0S493692A
`
`[54]
`
`175]
`
`SELECTIVE DELIVERY OF ELECTRONIC
`MESSAGES IN A MULTIPLE COMPUTER
`SYSTEM BASED ON CONTEXT AND
`ENVIRONMENT OF A USER
`
`Inventors: Marvin M. Theimer, Mountain View;
`Michael J. Spreitzer, Tracy; Mark D.
`Weiser, Palc Alto; Richard J.
`Goldstein, San Francisco; Douglas B.
`Terry, San Carlos; William N. Schilit,
`Palo Alto; Roy Want, Mountain View,
`all of Calif.
`
`[73]
`
`Assignce: Xerox Corporation, Stamford, Conn.
`
`[21]
`
`App]. No.: 162,419
`
`[22]
`
`Filed:
`
`Dec. 3, 1993
`
`1511
`
`[521
`
`[58]
`
`[561
`
`U.S. Cl.
`
`Int. Cl.5
`
`H04L 9132; G06F 7104;
`GOSB 5122
`455126.1; 38013; 380123;
`379138; 379157; 3401825 .31; 340132549
`Field of Search .............................. .. 4551261; 38013,
`380123; 340182531, 825.49, 825.5; 379138,
`56, 57
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`5,363,425
`
`1111994 Mufti ct 8.1.
`
`3401325119 X
`
`FOREIGN PATENT DOCUMENTS
`
`2230365
`
`1011990 United Kingdom .
`
`OTHER PUBLICATIONS
`
`Friedly, J. The Oflice 01' The 21st Century. Pale Alto
`Weekly. May 6, 1992. pp. 20-24.
`Kleiner, A. The Ultimate Control Chip The Programable
`World. Popular Science. May 1992. pp. 90—95.
`Sehilit, B. N.; Adams, N.; Gold, R.; Tso, M. M.; Want, R.
`The Parctab Mobile Computing System. PARC Papers at
`WWOS-IV, 1993 IEEE and Xerox. pp. 1-6.
`Weiscr, M. Some Computer Science Issues In Ubiquitous
`Computing. Communications of the ACM. Jul. 1993, vol.
`36, No. 7. p. 84.
`
`Primary Excminer—Gi1beno Barron, Jr.
`Attorney, Agent. or Ftrm——R. Christine Jacobs; Tracy L.
`Hurt
`
`[571
`
`ABSTRACT
`
`The present invention describes a method for selectively
`delivering electronic messages to an identified user or users
`in a system of mobile and fixed devices, including multiple
`display devices and multiple users, based on dis context of
`the system and the environment of the identified user.
`Electronic messages intended for an identified user or users
`may be given a level of privacy and a level priority, and
`contextual attributes for its delivery may be specified. The
`system perceives contextual attributes for the recipient user
`or users, including display devices in close proximity to the
`identified users, and determines a display property for said
`electronic message based on the contextual attributes, the
`user profile properties of each user, and the level of privacy
`and level of priority of the electronic message. The display
`property may designate immediate delivery on a particular
`display device, a notification on a particular display device,
`or storage of the message until the contextual attributes of
`the recipient user is consistent with the specified contextual
`attributes of the electronic message.
`
`8 Claims, 17 Drawing Sheets
`
`379156 X
`.. 340182549 X
`343111213
`34-01312
`.. ... 340123
`342142
`.. 340182554
`3641900
`..... 455139
`3591118
`3421450
`3641436
`.. 370185.?’
`.... .. 3701351
`340182531 X
`340132531 X
`
`.....
`
`.
`
`
`
`3,506,791
`3,739,329
`4,217,583
`4,275,335
`4,303,904
`4,912,471
`4,952,928
`5,027,314
`5,068,916
`5,099,346
`5,119,104
`5,122,959
`5,159,592
`5,181,200
`5,202,929
`5,218,344
`
`411970 Halaby
`611973 Lester ..
`B11930 Fteeny. Jr
`611981 White ..
`. . . . . . . . .
`1211981 Chase}:
`311990 Tybttrski et al
`B11990 Carroll et al
`611991 Linwood ct al
`1111991 Harrison et al.
`311992 Leeet a1.
`611992 Heller
`611992 Nathanson ct
`1011992 Perkins
`111993 Harrison
`411993 Lemelson .
`611993 Ricltetts
`
`I'M
`
`1'08
`
` 106
`
`
`110
`
`‘102
`
`U2
`
`Usemgent
`
`Person Specific Information
`
`Fem rial Policies
`
`@“\
`
`
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:20)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 1
`
`

`
`U.S. Patent
`
`Feb. 20, 1996
`
`Sheet 1 of 17
`
`5,493,692
`
`N1-
`
`13
`
`11
`
`11
`
`11
`
`Fig.1
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:21)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 2
`
`

`
`U.S. Patent
`
`Feb. 20, 1996
`
`Sheet 2 of 17
`
`5,493,692
`
`74
`
`
`
`
`DeviceAgentc 4-\
`
`
`
`34
`
`Badge Service
`
`I’
`
`80
`
`’”
`
`90
`
`UserAgentA
`
`CC ,
`
`Name Service
`
`Location Service
`
`
`
`Service
`Termina|AgentD 4- ...... --
`
`Input Monitor
`
`
`
`94
`
`Scoreboard
`
`75
`
`FIG. 2
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:22)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 3
`
`

`
`U.S. Patent
`
`Feb. 20, 1995
`
`Sheet 3 of 17
`
`5,493,692
`
`102
`
`112
`
`7
`
`104
`
`106
`
`
`
`
` UserAgent
`Person Specific Information
`
`Personal Policies
`
`
`
`110
`
`108
`
`FIG. 3
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 4
`
`
`
`

`
`U.S. Patent
`
`Feb. 20, 1995
`
`Sheet 4 of 17
`
`5,493,692
`
`I20
`
`Find And Read UserProfile
`
`
`
`
`
`Export RPC interface
`
`Register With Services
`For Callbacks
`
`
`
`130
`
`
`
`
`
`Execute Request
`
`138
`
`
`
` More Object
`
`Information?
`
`
`Contact And Retrieve
`Available Information
`From Object Agent
`
`
`
`
`
`Evaluate Policy
`Rules Against
`Current State
`
`
`
`Performed?
`
`Action To Be
`
` Time-Based
`Actions?
`
`
`
`
`
`
`
`FIG. 4
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:24)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 5
`
`126
`
`
`RPC Request
`Request
`From Identified
`Allowed?
`
`Client?
`
`
`
`
`
`
`
`
`128
`
`’32
`
`N
`~
`
`Deny
`Request
`
`

`
`U.S. Patent
`
`Feb. 20, 1996
`
`Sheet 5 of 17
`
`5,493,692
`
`DeviceAgent
`
`Device Profile
`
`Current State
`
`FIG. 5
`
`E3
`
`Termina|Agent
`
`Device Profiles
`
`172
`
`I74
`
`
`
`
`Current State of Devices
`
`176
`
`FIG. 6
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:25)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 6
`
`

`
`U.S. Patent
`
`Feb. 20, 1996
`
`Sheet 6 of 17
`
`5,493,692
`
`180
`
`Find And Read UserProfile
`
`
`
`I82
`
`Export RPC interface
`
`
`
`
`
`
`Register With Location
`Services or UserAgent
`
`184
`
`I86
`
`188
`
`*9“
`
`Y
`
`Execute
`Request
`
`
`
`RPC Request
`Request
`From tglentlfued
`Allowed?
`
`Chent?
`
`
`
`
`
`194
`
`N
`
`192
`
`Deny Request
`
`I96
`
` Housekeeping?
`
`Tirne~Based
`Actions?
`
`FIG. 7
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:26)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 7
`
`

`
`U.S. Patent
`
`Feb. 20, 1996
`
`Sheet 7 of 17
`
`5,493,692
`
`Name Service
`
`
`
`
`
`212
`
`214
`
`Registrations
`
`Callbacks
`
`FIG. 8
`
`E
`
`Location Service
`
`Registrations
`
`Location Information About Stationary Objects
`with No Managing Agents
`
`Location Specific Information
`
`Topological Information
`
`Other location and Conversion Information
`
`Callbacks
`
`FIG. 9
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:27)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 8
`
`

`
`US. Patent
`
`Feb. 20, 1996
`
`Sheet 8 of 17
`
`5,493,692
`
`Export RFC Address
`To Name Service
`
`240
`
`
`
`242
`
`246
`
`Y
`
`
`-
`-
`Registration
`Request?
`
`
`
`
`
`Register Tuples
`For_ Specified Statio nary
`0b}ects Without Agents
`
`
`
`254
`
`
`
`43
`
`N
`
`
`
`
`
`
`lid
`.
`ya
`Registration?
`
`
`
`Y
`
`Update Location
`Information
`
`
`Callbacks
`
`Affected?
`
`
`
`
`"
`
`266
`
`N
`
`250
`
`256
`
`
`
`Callback
`Request?
`
`N
`
`Y
`
`268
`
`
`
`
`DO
`
`
`
`
`
`Appropriate
`' egistere 1
`Callbacks
`Owners
`Still Alive?
`
`
`
`
`
`Perform
`Indicated
`Action
`
`
`
`
`
`Garbage
`Collect Dead
`Registrations
`
`274
`
`FIG. 10
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:28)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 9
`
`

`
`U.S. Patent
`
`Feb. 20, 1996
`
`Sheet 9 of 17
`
`5,493,692
`
`Export RPC Address
`
`To Name Service
`
`
`
`
`
`' PC REqI..lE5
`From ldentifie -
`Client?
`
`
`
`Sighting
`Information?
`
`
`
`Update
`Badge
`Locauon
`Information
`
`
` Callback
`Request?
`
` Do
`Appropriate
`Callbacks
`
`Garbage
`Collect Dead
`Registrations
`
` Garbage
`Collect Dead
`Registrations
`
`
`
`Appropriate
`Callbacks
`
`
`
`Do Query
`And Return
`Resun
`
`FIG. 11
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:20)(cid:19)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 10
`
`

`
`U.S. Patent
`
`Feb. 20, 1996
`
`Sheet 10 of 17
`
`5,493,692
`
`Export RPC Address
`To Name Service
`
`310
`
` Update
`
`‘PC Req”9§
`User
`
`From I_dent)ifie -
`Location
`c""3‘”t-
`Information
`
`
`
`
`
`
`
`
`D0
`Appropriate
`
`Re Ester
`
`Callbacks
`Ca back
`
` 330
`Query?
`Registrations
`
`Location
`
` Do Query
`And Return
`
`Result
`
`
`
`Garbage
`Collect Dead
`
`FIG. 12
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:20)(cid:20)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 11
`
`

`
`U.S. Patent
`
`Feb. 20, 1996
`
`Sheet 11 of 17
`
`5,493,692
`
`346
`
`348
`
`350
`
`
`
`Obtain Relevant Contextual And
`Environmental Information
`
`Evaluate Action Based On
`Environment And Context
`
`
`
`Determine Action To Be Performed
`
`Perform Action Or Alternate
`Action(s) As Appropriate
`Based On Contextual Evaluation
`
`FIG. 13
`
`Determine Location Of
`Object Of Interest
`
`352
`
`354
`
`
`
`Obtain Relevant Para meters
`Of Objects Related
`To Objects Of Interest
`
`358
`
`356
`Obtain Relevant Information
`About Other Objects At Or Near The
`Location Of The Object Of Interest
`
`FIG. 14
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:20)(cid:21)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 12
`
`

`
`U.S. Patent
`
`Feb. 20, 1996
`
`Sheet 12 of 17
`
`5,493,692
`
`360
`Identify
`
`Machine
`
`Event
`
`For Event
`
`
`Centextual Attributes
`_ Consistent With Determined
`Contextual Attributes?
`
`364
`
`
`
`368
`
`Change In
`
`System State
`
`
`Activate Event
`
`FIG. 15
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:20)(cid:22)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 13
`
`
`
`
`
`
`Identify Necessary
`Contextual Attributes
`
`

`
`U.S. Patent
`
`Feb. 20, 1996
`
`Sheet 13 of 17
`
`5,493,692
`
` 400
` Message
`
`
`
`Message
`Recipient
`Identified
`
`
`
`Contextual Attributes
`For Delivery Determined
`
`Obtained
`
` 406
`System State
`
`Change in
`
`
`
`Contextual Attributes
`Consistent With_Determine.d_
`Contextual Attributes?
`
` _
`
`Deliver Message
`To Appropriate Device
`
`408
`
`
`
`FIG. 16
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:20)(cid:23)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 14
`
`

`
`U.S. Patent
`
`Feb. 20, 1996
`
`Sheet 14 of 17
`
`5,493,692
`
`To Be
`Delivered
`
` Message
`
` Find UserAgent
`
` Send RPC Request
`(Each) User Agent
`
`Of (Each)
`Intended Recipient
`
`with Message To
`
`422
`
`424
`
`436
`
`
`
`
`
` I eiiverable
`Context?
`
`
`
`Change Of
`Context
`
`
`
`Find Context Of Intended Recipient
`Including Available Device(s)
`And Device Profiie(s) At Location
`Of Intended Recipient
`
`
`
`Based On
`
`Don't Deliver
`Message
`
`Deliver Message
`To Appropriate Device
`
`FIG. 17
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:20)(cid:24)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 15
`
`

`
`U.S. Patent
`
`Feb. 20, 1996
`
`Sheet 15 of 17
`
`5,493,692
`
`504
`
`
`
`
`Receive
`Ownership
`Request
`
`
`
`502
`
`
`
`Cu rrentiy Owned
`By An other?
`
`Determine Contextual Attributes
`Of The System
`
`
`
`508
`
`
`
`Evaluate Owner Ship Request
`Based On Device Profile, Context
`
`
`
`510
`
`
`Ownersflfia Ring hts
`
`Enable A re riate
`
`
`
`FIG. 18
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:20)(cid:25)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 16
`
`

`
`U.S. Patent
`
`Feb. 20, 1996
`
`Sheet 16 of 17
`
`5,493,692
`
`520
`
`
`Perform Qnly
`Appropriate
`Una uthenticated
`Fu nctions
`
`
`
` ls User Authenticated?
`
`Retrieve
`User Profile
`
`Configure Device
`As Appropriate
`Based On
`User Profile
`
`
`
`
`
`FIG. 19
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:20)(cid:26)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 17
`
`

`
`U.S. Patent
`
`Feb. 20, 1996
`
`Sheet 17 of 17
`
`5,493,692
`
` User Logout?
`
`364
`
`Logoff User
`
`FIG.20
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:20)(cid:27)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 18
`
`

`
`1
`SELECTIVE DELIVERY OF ELECTRONIC
`MESSAGES IN A MULTIPLE COMPUTER
`SYSTEM BASED ON CONTEXT AND
`ENVIRONMENT OF A USER
`
`5,493 ,692
`
`2
`
`CROSS REFERENCE TO OTHER
`APPLICATIONS
`
`The subject matter of the present invention is related to
`the subject matter of concurrently filed, commonly assigned
`US. patent applications having the following serial numbers
`and titles: Scr. No. 08t‘l61,968 “SELECTION, CONTROL
`AND OWNERSIHP OF PARTICULAR DEVICES IN A
`MULTIPLE COMPUTER SYSTEM BASED ON CON-
`TEXT AND ENVIRONMENT IN PROXIMITY TO A
`USER OR DEVICE," Ser. No. 08r‘l6l,730 “SPECIFYING
`AND ESTABLISHING COMMUNICATION DATA
`PATHS BETWEEN PARTICULAR MEDIA DEVICES IN
`MUI..TIPLE MEDIA DEVICE COMPUTING SYSTEMS
`BASED ON COl\’TEXT OFA USER OR USERS," and Ser.
`No. 08.-"l62,522, “PERSONAL PRIVACY FOR MOBILE
`USERS IN DISTRIBUTED COMPUTING ENVIRON-
`MENTS THAT SUPPORT LOCATION SENSITIVE
`
`APPLICATIONS,” each of which are hereby incorporated
`by reference herein.
`
`FIELD OF THE INVENTION
`
`The present invention relates to control by a user of
`particular devices and activities in a multiple computer
`system based upon the current location and surrounding
`environment, including computing devices, of the user.
`More specifically, the invention relates to techniques for
`selectively delivering electronic messages to an identified
`user via particular computer devices based on context and
`environment in proximity to the user.
`
`BACKGROUND OF THE INVENTION
`
`The introduction of computer networks and personal
`computing has forever changed users’ expectations of what
`computer systems can accomplish.
`Individual users no
`longer expect to travel to a particular location to have their
`processing needs met. Instead, individuals expect to have
`suflicient computing power sitting on their desk to get the
`job done; or, at
`least, to have their personal computers
`networked to suficient resources remote from their location
`
`to accomplish tl‘1e task.
`Attempts have been made to improve the “t1ser—fricndli~
`ness" of such personal computers, including the develop-
`ment of “window" systems to give users the illusion of
`working from their desktop electronically. This metaphor
`suffers, however, from the size limitation of the usual
`monitor screen for personal computers—no one would ever
`think of using an actual desktop only nine inches high by
`eleven inches wide. Personal computers remain static
`objects commanding the attention of users.
`The notion of a computing environment in which com-
`puters themselves disappear into the background was raised
`by Marl: Weiser, “The Computer for the 21st Century,"
`Sciemtfic American, September 1991. Two issues of crucial
`importance to transmission and display of information in
`such a “ubiquitous" computing environment are location and
`number of devices.
`
`10
`
`20
`
`25
`
`3|}
`
`35
`
`4!}
`
`50
`
`60
`
`65
`
`Weiser postulates a world in which there are many com-
`puting and computer-controlled devices surrounding each
`user all
`the time. In one example of such a system, he
`describes devices ranging from small computational devices
`called “’I‘abs”—.-inch-scale computers which are networked
`via wireless linl<s—to yard-scale displays that may be used
`as electronic blackboards called “Board," that may cover the
`entire wall of a room.
`
`Users may also wear “Active Badges,” credit-card-sized
`devices that emit an infrared identification signal that can be
`sensed by receivers placed in each room of a building,
`thereby allowing detection of where each user is currently
`located. Active Badges can also be attached to other moving
`objects, such as portable printers and copiers.
`Also discussed by Weiser at page 99 are “Pads.” scrap~
`paper-like, notebook-sized computers that have no individu—
`alized identity or ownership. Wciscr postulates that in the
`future there will be many Tabs and Pads per person, just as
`today there are many paper notebooks and stick-on notes per
`person. Consequently, users will interact with many dillcrent
`devices, both serially and in parallel, during the course of
`their daily lives.
`“Guest" Tabs or Badges, and “scrap" Pads are devices not
`owned by any particular user. Instead, they are availabie——~
`perhaps at the entrance to a building in the case of guest
`Badges, or in meeting rooms in the case of Tabs and
`Pads—for use by whoever picks them up. Picking up an
`Active Badge might involve checking it out from building
`security so that its association with a particular user can be
`registered with the system.
`In the environment described in Weiser, specific actions
`may be taken by computers based on knowledge of location.
`For example, a Board may be configured as a public
`information bulletin board, its display information attuned to
`the people reading it. Room audio amplification or lighting
`may be controlled according to the desires of the people
`using Tabs or Pads in the room at that moment. Remote
`actions may be triggered by a user's presence at a location,
`such as a login procedure started when a user enters his or
`her ofiice.
`
`Jock Friedly, in “The Ofiice of the 21st Century," Polo
`Alto Weekly, May 6, 1992, further describes a ubiquitous
`computing environment including Tabs and Active Badges
`which broadcast signals that may be tracked throughout the
`computing envirournetit. Badges indicate where a person is
`so that phone calls, for example, may be forwarded to a
`user’s location.
`
`In a ubiquitous computing environment such as described
`by Weiser, users may further desire different automatic
`actions to be made by the system based on the context
`surrounding them. Some actions should only take place
`under controlled conditions. The environment or context of
`a user may aiiect operations the user might wish nearby
`computing systems to perform. For example, a user in a
`private meeting may not wish to have phone calls forwarded
`to that location. A message that is private may be displayed
`on a user’s private Pad, but probably not on a public Board.
`Similarly, a particular computing device may respond to
`users in different ways depending on the environment and
`context. For example, if one user walks into an unoccupied
`room, each computing device in that room may temporarily
`assign some measure of ownership control of itself or its
`resources to that user. When a second user enters the same
`room some, all, or none of the computing devices may allow
`the second user ownership rights, depending on the context
`and environment.
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:21)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:20)(cid:28)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1002 - Page 19
`
`

`
`5,493 ,692
`
`3
`As described in Weiser. a user may be able to migrate any
`window that may appear on a workstation screen onto aTab,
`Pad or Board. This allows users ongoing use of difierent U0
`devices tointeract with their electronic data and applica-
`tions. Which devices will be used will depend on the
`circumstances of the user. In addition. more than one device
`might be used to interact with the system at the same time.
`For example, a user might keep several Pads on his or her
`desk, and migrate “sccondary" applications. such as system
`status monitors, from a workstation screen onto those Pads.
`This would free up the workstation screen for use by
`“primary” applications, such as word processors and spread
`Sheets. Just as today people spread out papers across their
`entire desks, so too might the user of tomorrow spread out
`work onto multiple electronic screens, be they Tabs. Pads,
`Boards, or workstations.
`When a user goes to a meeting in another room, the user
`may take along one of those screens, or may choose to
`migrate the contents of one or more screens onto the U0
`devices available in the meeting room, such as a Board, or
`one of several scrap Pads in the room.
`Such a ubiquitous environment should enable users to
`make better use of their time and space. For example, some
`methods users employ to remind themselves of events-
`notes, pagers. beeping wristwatches, electronic calendars—-
`cannot support automatic message delivery to a remote
`system, and cannot issue special messages tailored to the
`physical location and environment of the particular user.
`Although there may be several ways to support a “ubiq-
`uitous computing" environment to accommodate the entire
`range of mobility required for ubiquitous computers, a
`preferred implementation is a network that allows “wireless”
`communication with mobile devices. To date, many "wire-
`less“ networks have already been designed—the most
`notable, perhaps. being the cellular telephone network.
`Wireless network systems are generally concerned with the
`physical layer of the network, and more specifically, with
`methods of transferring the commurtication support for a
`mobile unit from one base station to another. These issues
`may be classified as problems in “communication continu-
`ity.” Communication continuity is concerned primarily with
`mechanisms for providing a continuous pathway for data
`between two or more units. at least one such unit being
`mobile, and for reestablishing a data pathway in the event of
`an unwanted disruption. By contrast, “processing continu-
`ity" relates to maintaining a current and proper processing
`context between two units.
`
`A system for maintaining communication and processing
`continuity between a mobile processing unit and remotely
`resident applications is described in coassigned, copending
`patent application 08r'l00,655 entitled A METHOD AND
`SYSTEM FOR MAINTAINING PROCESSING CONTI-
`NUITY T0 MOBILE COMPUTERS IN A WIRELESS
`NETWORK, filed Aug. 30. 1993 by Want et al., incorpo-
`rated herein by reference. The system includes a network
`backbone, at least one stationary processor coupled to the
`backbone, and at least one transceiver coupled to the back-
`bone. The transceivers are configured to communicate with
`the mobile unit through a wireless medium. Mobile units
`intermittently communicate with applications. The system
`employs a process that is dedicated to handling all commu-
`nications between its associated mobile unit and applica-
`tions. This proeess is responsible for the scheduling of
`communications sessions with the mobile unit.
`
`One aspect of the present invention is the ability to
`provide a system in which actions of Ihc system are initiated
`
`20
`
`30
`
`40
`
`45
`
`50
`
`55
`
`60
`
`4
`
`or triggered based on the context {for example, the location
`of the user or other users, the time of day) and the environ-
`ment (for example, the user’s location, nearby computing
`devices available) in proximity to the user.
`Another aspect of the present invention provides a system
`in which the delivery of electronic messages to a particular
`user or users may be selective, depending upon the context
`or state of the user or users. Furthermore, appropriate
`computing devices for particular actions, such as delivery of
`electroriie messages, are selected based on the environment
`in proximity to the user in relation to the properties of the
`message.
`In order to carry out these and other related functions, the
`system may have knowledge not only of users, machines,
`and computing devices, but of the context and environment
`that the users and devices are operating in. The system may
`know, for example, the physical location of a user, what
`computing devices are available at that location, what other
`users may be in close proximity to the user. The system may
`further provide processing continuity over a range of loca-
`tions. For particular operations, the system may be able to
`discern predefined control variables, and may be sensitive to
`the context of cerlain actions.
`
`SUMMARY OF THE INVENTION
`
`The invention describes a method for selectively deliver-
`ing electronic messages to an identified user in a system of
`mobile and fixed devices, including multiple display devices
`and multiple users, where the identity and location of each
`device, display device, and user may be known to the
`system, based on the context of the system and the envi-
`ronrnenl of the identified user. An electronic message,
`intended for an identified user, is obtained. and a level of
`privacy and a level priority for the electronic message is
`determined. The profile properties for the identified user are
`obtained. The system perceives contextual attributes for the
`identified user, including display devices in close proximity
`to the identified user, and determines a display property for
`said electronic message based on the contextual attributes,
`the user profile properties, and the level of privacy and level
`of priority of the electronic message.
`The following description, the drawings and the claims
`further set forth these and other objects, features and advan-
`tages of the invention.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`FIG. I shows an ofliicc environment configured to support
`a "ubiquitous computing” system.
`FIG. 2 shows a high level diagram of the system archi-
`tecture of the system elements and communications paths
`between the system, users and devices used to determi