throbber

`
`
`
`
`
`
`US 7,181,497 B1
`(10) Patent No.:
`(12) Unlted States Patent
`
`
`
`
`
`
`
`
`
`Appelman et a].
`(45) Date of Patent:
`*Feb. 20, 2007
`
`
`
`
`
`USOO7181497B1
`
`
`
`(54) MESSAGING APPLICATION USER
`
`
`
`
`INTERFACE FOR AUTO-COMPLETING
`
`
`
`ADDRESS TEXT AND MODIFYING THE
`
`
`
`
`
`AUTO_COMPLETION BEHAVIOR
`
`
`
`
`
`(75)
`
`
`
`
`
`
`Inventors: Barry Appelman, Great Falls, VA
`
`
`
`
`Andrew L' WICk’ Falrfax’ VA
`.
`.
`,
`,
`
`
`
`
`
`
`
`
`
`
`(73) Asslgnee’ Amerlca Onhne’ Inc" Dunes’ VA (Us)
`
`
`
`
`( * ) NOtiC33
`
`
`
`
`
`
`
`
`
`SUbjeCt.t0 any diSCIaimers. the term Of this
`
`
`
`
`patent IS 6Xtended 01‘ adjuSted under 35
`
`
`
`
`U.S.C. 154(b) by 729 days.
`
`
`
`
`This patent is subject to a terminal dis-
`
`claimer.
`
`
`
`(21) A 1 N 10/348 004
`pp .
`o.:
`,
`
`
`
`
`
`
`
`
`......... .. 365/189.01
`4/1999 Miller etal.
`5,896,321 A *
`
`
`
`
`
`
`............... .. 715/780
`3/2001 Atlas et al.
`6,208,339 B1*
`
`
`
`
`
`
`
`8/2001 De Vorchik et a1.
`6,279,016 B1
`
`
`
`
`
`
`4/2002 Hachamovitch et al.
`6,377,965 B1
`
`
`
`
`
`6,480,885 B1* 11/2002 Olivier ..................... .. 709/207
`
`
`
`
`
`
`
`OTHER PUBLICATIONS
`
`
`
`
`
`Thompson, “How to enable ‘AutoComplete’
`feature”, Google
`Group compiunixishellhtm, Dec. 23, 1998].*
`
`
`
`
`
`
`
`Pioch, Nicholas. A Short IRC Primer [online], Jan. 1997. [retrieved
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`on Mar. 14, 2002] Retrieved from the Internet: <URL: http://www.
`irchelp. 0rg/irchelp/ircprimer.html>.
`
`
`
`
`
`
`
`
`
`Polito, Julie. “Track your key contacts; Multiactive Maximizer 5.0
`
`
`
`
`
`
`
`
`vs. Polaris Packrat Pro 6.1” PC Computing, Oct. 1, 1998 p. 120
`
`(abstract).
`
`
`
`
`
`
`
`
`(Continued)
`
`
`
`
`
`
`
`
`Primary Examiner7Wen-Tai Lin
`
`
`
`
`
`(74) Attorney, Agent, or FirmiFish & Richardson P.C.
`ABSTRACT
`(57)
`
`
`Jan. 22, 2003
`
`
`
`
`
`
`
`
`
`
`A messaging application user interface has an input element
`
`
`
`
`
`
`
`
`
`
`
`
`for receiving electronic messages and an output element for
`Related US. Application Data
`
`
`
`
`
`
`
`diSplayin§i eleCtrOIgic melssages' ghe messaging applicagon
`(63) Continuation of application No 09/404 757 filed on
`user inter ace can e imp emente so as to maintain a su set
`’
`’
`’
`
`
`
`
`
`
`
`
`Sep. 24, 1999, now Pat. No. 6,539,421.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`of the plurality of potential message recipients, the subset
`
`
`
`
`
`
`
`
`Int Cl
`being determined using a predetermined criterion. The mes-
`
`
`
`
`
`
`
`
`
`(2006 01)
`G01;F 5/16
`saging application user interface also can be implemented so
`
`
`
`
`
`
`
`
`
`
`(200601)
`G06F 3/00
`as to auto-complete a partially entered address based on the
`
`
`
`
`
`subset of potential message recipients. A set of user-select-
`(52) US. Cl.
`..................... .. 709/206; 709/207; 715/780
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`able signals that modify auto-completion behavior also can
`(58) Field of Classification Search ................... .. None
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`be used with the messaging application user interface. The
`
`
`
`
`
`
`
`See application file for complete search history.
`
`
`
`
`
`
`
`
`messaging application user interface can be used in an
`
`
`
`
`
`
`
`
`
`instant messaging system to allow a user to send instant
`References Cited
`
`
`
`
`
`
`
`messages to and exchange comments with a plurality of
`
`
`
`
`
`
`
`
`other users without having to switch among several instant
`
`
`message Wlndows'
`
`(22)
`
`
`
`Filed:
`
`
`
`
`
`
`
`(51)
`
`
`
`(56)
`
`
`
`
`
`
`
`
`US PATENT DOCUMENTS
`
`
`
`9/1998 Miller
`5,805,911 A
`5,832,497 A
`11/1998 Taylor
`
`
`
`5,845,300 A
`12/1998 Comer et al.
`
`
`
`
`
`
`
`
`35 Claims, 21 Drawing Sheets
`
`
`
`
`
`
`404
`
`
`
`408
`
`406
`
`
`
`
`
`
`
`
`
`
`
`
`LAST-ADDRVESS SIGNAL
`
`
`
`RECEIVE PARTIALADDRESS
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`USE LAST ADDRESS AS
`CURRENT ADDRESS
`
`
`
`
`USE SECONDTOIAST ADDRESS
`AS CURRENT ADDRESS
`
`
`
`
`
`PERFORM MOST-RECENT-
`SEARCH OF ADDRESS LIST
`
`
`
`
`
`USE MOST RECENT MATCH
`AS CURRENT ADDRESS
`
`
`
`
`N0 AUTOCOMPLETE;
`RECEIVE ADDRESS
`
`
`
`NO AUTOCOMPLETE;
`RECEIVE ADDRESS
`
`
`
`AUTOCOMPLETE WITH
`MATCHINGADDRESS
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Patent Owner Exhibit 2001, Page 1
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`
`
`
`
`Patent Owner Exhibit 2001, Page 1
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`
`
`US 7,181,497 B1
`Page 2
`
`
`OTHER PUBLICATIONS
`
`
`Elkins, M.: “The Mutt E-Mail Client, version 1.0pre2”, Internet
`
`
`
`
`
`
`
`
`
`Document,
`[Online], Sep.
`1, 1999, pp. 1-84, XP002245042,
`
`
`
`
`
`
`
`
`Retrieved from the Internet: URL:ftp://ftp.n1uug.n1/pub/mai1/mutt/
`
`
`
`
`
`historic/mutt-l.Opre2.tar.gz [retrieved on Jun. 17, 2003].
`
`
`
`
`
`
`Anonymous: “Readme of archive for TNT 1.7”, Internet Document,
`
`
`
`
`
`
`
`
`[Online], Dec. 4, 1998, pp. 1-4, XP002245043, Retrieved from the
`
`
`
`
`
`
`
`
`
`Internet: URL :http ://WWW.mit.edu/afs/athena/system/pmaxiu 14/
`
`
`
`srvd.74/usr/sipb/src/tnt/tnt-1.7.tar.gz [retrieved on Jun. 17, 2003]
`
`
`
`
`
`
`
`the Whole document.
`
`
`
`Stephenson, P.: “Auser’s Guide to the Z-Shell”, Internet Document,
`
`
`
`
`
`
`
`[Online}, Jun. 2, 1999, pp. 1-335, XP002245044, Retrieved from
`
`
`
`
`
`
`
`
`Internet:
`URL:http://zsh.sunsite.dldGuide/zshguidepdf
`the
`
`
`
`[retrieved on Jun. 17, 2003].
`
`
`
`
`
`Internet
`Anonymous: “AOL Instant Messenger, User’s Guide”,
`
`
`
`
`
`
`
`Document,
`[Online], Feb. 25, 1998, pp. 1-23, XP002245045,
`
`
`
`
`
`
`
`
`Retrieved from the Internet: URL:http://WWW.aim.aol.com/beta/
`
`
`
`
`
`uguide/indexhtml [retrieved on Jun. 6, 2003] the Whole document.
`
`
`
`
`
`
`
`Anonymous: “Netscape Page info for http://www.aim.aol.com/beta/
`
`
`
`
`
`
`uguide/indexhtml”,
`Internet Document,
`Feb.
`25,
`1998,
`
`
`
`
`
`
`XP002245046, [retrieved on Jun. 17, 2003].
`
`
`
`
`
`Anonymous: “Mutt News”, Internet Document, [Online], pp. 1-2,
`
`
`
`
`
`
`
`XP002245047, Retrieved from the Internet: URL:http://Www.mutt.
`
`
`
`
`
`org/newshtml [retrieved on Jun. 17, 2003].
`
`
`
`
`
`Anonymous: “FTP Page”, Internet Document, [Online], Dec. 4,
`
`
`
`
`
`
`
`1998, p. 1, XP002245048, Retrieved from the Internet: URL:http://
`
`
`
`
`
`
`
`www.mit.edu/afs/athena/system/pmaxiu14/srvd.74/usr/sipb/src/
`
`
`tnt/.html [retrieved on Jun. 17, 2003].
`
`
`
`
`
`
`
`
`* cited by examiner
`
`
`
`
`Patent Owner Exhibit 2001, Page 2
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 2
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`
`U.S. Patent
`
`
`
`
`
`Feb. 20, 2007
`
`
`
`
`
`Sheet 1 of 21
`
`
`
`US 7,181,497 B1
`
`107
`
`
`
`DISPLAY
`
`
`
`100
`
`
`
`105
`
`
`
`103
`
`
`
`
`ID
`
`
`
`OPERATING
`
`SYSTEM
`
`
`
`APPLICATION
`
`PROGRAM
`
`
`
`PROGRAM
`
`APPLICATION
`
`
`
`
`
`1 27
`
`
`
`
`
`
`FIG. 1
`
`(PRIOR ART)
`
`
`
`Patent Owner Exhibit 2001, Page 3
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 3
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`
`U.S. Patent
`
`
`
`
`
`Feb. 20, 2007
`
`
`
`
`Sheet 2 of 21
`
`
`
`US 7,181,497 B1
`
`
`200
`
`EC:
`ND:
`‘<
`0“
`1—19
`LL19:
`0‘v
`
`z
`2
`E
`(D
`E—z
`a
`A
`u
`
`
`
`a:
`LU
`
`>ZL
`
`L]
`U)
`
`
`
`E:
`C1
`O
`2
`
`5
`G
`O
`Z
`
`
`
`'
`
`<23
`i?
`a
`E—
`E
`h—i
`d
`
`z
`9
`E
`U)
`i-
`E
`A
`u
`
`N
`a
`
`
`
`N
`a
`
`
`
`Q
`a”
`
`
`
`Patent Owner Exhibit 2001, Page 4
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 4
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`
`U.S. Patent
`
`
`
`Feb. 20, 2007
`
`Sheet 3 of 21
`
`
`
`US 7,181,497 B1
`
`
`
`c3
`
`
`
`(52A<ZOFZm>ZOU
`
`fl m.UE
`
`e
`
`Emcmmu
`
`
`98mm23.,:3.2m
`I#5
`
`.B>of9wowi:839wasHd:meEtoED"8.25m:
`
`
`mEmE522E&2:8m30%Evso:"DEE—Em_mg
`
`
`
`sees“33::
`
`
`
`28%2%
`
`mogmEm>u>@M
`
`Patent Owner Exhibit 2001, Page 5
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`
`
`
`
`magmas.E32.I22mm”.M
`
`Patent Owner Exhibit 2001, Page 5
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`
`U.S. Patent
`
`
`
`
`
`Feb. 20, 2007
`
`
`
`
`Sheet 4 of 21
`
`
`
`US 7,181,497 B1
`
`
`CONVENTIONAL ART
`
`
`
`140
`
`
`
`
`
`
`
`
`
`35‘ PhilliszC's Buddy List Window
`
`
`
`Eile Eeople Favogites
`
`
`
`
`
`Cha‘l’
`Now!
`
`143
`
`
`
`7
`
`
`
`VIEHEEE?§_.(9E)...§
`
`
`v AOL (215)
`
`Ericbosco —— 141
`
`Flatt ——————— 142
`
`
`
`v Family (0/2)
`
`
`7 Co-Workers (3/5)
`
`F Rsnafu
`
`jimgromada — 144
`
`
`
`
`
`
`
`
`
`
`
`
`
`A
`
`
`Today!
`
`
`FIG. 4
`
`Patent Owner Exhibit 2001, Page 6
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 6
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`U.S. Patent
`
`0,2b.eF
`
`2f
`
`S
`
`1B794.}1m
`
`£252q<ZOFZm>ZOo82
`
`UQa
`7,moem539
`.m9c.25%.oc<MogmE3908%Scamoo<moo_mEm>l>mwe®w«MEMEEQoan
`
`
`
`
`
`$9654SEN;mammEowEofimaomm:9»“6m9E.$9654mc_ca>>m_%2oee980m26:»tum9m
`
`
`
`
`
`33onE92...«mmwcomccgEMkmmmmmws.ESmEI«mmEQEMA
`
`
`
`
`
`BEES“25w2:9ow9ES;so»ow.22«63"35509.
`
`mtfim25%2:meow5550:6€m3:om:=c.€
`
`an:E"Eamon:
`
`
`
`n:.23:38:22
`
`MIl
`
`.5a;:8“gm3852:
`
`Patent Owner Exhibit 2001, Page 7
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 7
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`
`U.S. Patent
`
`
`
`
`
`
`
`m
`
`
`
`12f06w.hS
`
`
`
`1.}7
`
`100
`
`1B
`
`
`
`
`
`
`7.w,0CananM:
`mmm23.2.0:20323;
`
`mcmmmm,DJm:8»5509.Am
`
`
`
`
`20:39cm9:3320%onSE.»NEEEAEAH
`
`2228ow8>32:0»8m,EOHvmmEOQNH
`
`SE.2a:2:msgfiqum
`
`28m
`
`n
`
`EmESEES/AH
`
`
`
`@225Naéagé
`
`Patent Owner Exhibit 2001, Page 8
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 8
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`U.S. Patent
`
`Feb. 20, 2007
`
`Sheet 7 of 21
`
`US 7,181
`
`497 B1
`
`,b.UE
`
`m0<mmm2
`
`V<Amma
`
`m0<wmm2
`
`><Amma
`
`m©<mwm2
`
`mZmomm
`
`Smum:292
`
`ataxia
`
`m0<mmm2
`
`mamomm
`
`m0<mmm2
`
`WQOm
`
`92mm
`
`m0<mmm2
`
`Badman—
`
`m0<mmEa
`
`Patent Owner Exhibit 2001, Page 9
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 9
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`
`U.S. Patent
`
`
`
`
`
`Feb. 20, 2007
`
`
`
`
`Sheet 8 of 21
`
`
`
`US 7,181,497 B1
`
`
`
`90
`
`
`
`AUTO-COMPLETE
`
`
`
`
`
`
`FIG. 8
`
`Patent Owner Exhibit 2001, Page 10
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`2
`
`9
`
`94
`
`96
`
`MAINTAIN GROUP OF
`
`
`
`
`POTENTIAL RECIPIENTS
`
`MAINTAIN SUBSET OF
`
`
`
`
`GROUP OF POTENTIAL
`
`RECIPIENTS
`
`USING SUB SET
`
`Patent Owner Exhibit 2001, Page 10
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`
`U.S. Patent
`
`
`
`
`
`Feb. 20, 2007
`
`
`
`
`Sheet 9 of 21
`
`
`
`US 7,181,497 B1
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`FIG. 9
`
`Patent Owner Exhibit 2001, Page 11
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 11
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`U.S. Patent
`
`Feb. 20, 2007
`
`Sheet 10 0f 21
`
`US 7,181,497 B1
`
`wofi
`
`vow
`
`
`
`
`
`mmmmmnzAshyzmmamomm
`
`
`
`mmmman<FEED
`
`
`
`
`
`m<8559‘.55mm:#268mmmmna
`
`N.
`
`
`
`mmmmnn:Hmfiéhdzoummmm:
`
`
`
`mmmxnnzEganm<
`
`
`
`.EZmommémOEEMOmdmm
`
`$0.22
`
`
`
`mmmmnaHZmMEDUm<
`
`“whmqmzooosgwOZ
`
`mZmUm—M
`
`
`
`mmmmnn:mamomd
`
`$.53
`
`OZEOHE
`
`szomm502Mm: .55mmmMQQ<momomfimm
`MmhmqmzouopbxxOZ mmmmnew
`qumEOUOHD<
` mmmmnnz
`
`.54.—
`
`Patent Owner Exhibit 2001, Page 12
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 12
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`
`
`
`
`
`

`

`
`U.S. Patent
`
`
`
`
`
`Feb. 20, 2007
`
`
`
`
`
`Sheet 11 of 21
`
`
`
`US 7,181,497 B1
`
`
`
`
`
`RECEIVE MESSAGE BODY
`
`
`
`
`
`SEND INSTANT MESSAGE
`
`
`
`UPDATE ADDRESS LIST
`
`
`
`
`
`
`
`
`FIG. 11
`
`Patent Owner Exhibit 2001, Page 13
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 13
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`
`U.S. Patent
`
`
`
`
`
`Feb. 20, 2007
`
`
`
`
`Sheet 12 of 21
`
`
`
`US 7,181,497 B1
`
`618
`
`
`
`620
`
`
`
`{J
`
`
`
`
`Hello, Mary.
`H1, JD.
`
`
`
`
`
`
`
`
`T> 07:34:57 mroe1934:
`lf€[07:35:09”mroe1934:|
`
`
`
`
`626
`
`622
`
`624
`— Conversations
`
`
`
`
`FIG. 12
`
`
`
`
`
`630
`
`
`
`Patent Owner Exhibit 2001, Page 14
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 14
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`
`U.S. Patent
`
`
`
`
`
`Feb. 20, 2007
`
`
`
`
`Sheet 13 0f 21
`
`
`
`US 7,181,497 B1
`
`
`BUI — Conversations
`
`
`
`
`
`600
`(.J
`
`
`
`
`
`
`
`
`
`
`
`
`
`' BUI — Conversations
`
`
`
`636
`
`
`
`632
`
`
`
`roe193
`
`
`e110, Mary
`
`
`
`@911
`
`
`
`612
`
`
`
`634
`
`
`
`638
`
`
`
`
`FIG. 15
`
`Patent Owner Exhibit 2001, Page 15
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 15
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`
`U.S. Patent
`
`
`
`
`
`Feb. 20, 2007
`
`
`
`
`Sheet 14 0f 21
`
`
`
`US 7,181,497 B1
`
`642
`
`
`
`644
`
`
`
`638
`
`
`
`
`600
`
`/—/
`
`640
`
`> 13:20:05 mroel934:
`
`
`
`
`Hello, Mary
`lHi, Johnl
`E<1|13220:27|mr0e1934:|
`
`
`
`
`
`
`648
`650
`652 g 654
`
`
`646
`
`
`
`
`
`
`
`
`
`
`
`
`BUI — Conversations
`
`
`
`
`
`
`T > 13:20:05 mroel934:
`
`
`
`F > 13:20:27 mroel934:
`
`
`Hello, Mary.
`
`
`Hi, John
`
`
`
`
`
`656
`
`
`
`
`How are you?
`
`
`
`
`
`$31
`
`
`
`662
`
`
`
`
`FIG. 17
`
`Patent Owner Exhibit 2001, Page 16
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 16
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`
`U.S. Patent
`
`
`
`
`
`Feb. 20, 2007
`
`
`
`
`Sheet 15 of 21
`
`
`
`US 7,181,497 B1
`
`
`
`668
`
`
`
`
`
`
`
`
`
`
`
`
`
`662
`
`
`Hello, Mary.
`
`
`
`
`
`
`0:27 mroe 934:
`
`
`
`
`T > 13:21:12 mroel934:
`How are you?
`
`
`
`
`
`I'm sick. I can't play
`F > 13:21:39 mroel934:
`
`
`in tomgfit's game K
`
`
`
`676 R
`674
`670
`
`
`
`612
`
`
`
`
`
`
`
`Hi, John
`
`
`
`
`
`
`
`
`678
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`682
`
`610
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`BUI - Conversations
`
`
`
`T > 13:20:05 mroel934:
`
`
`
`F > 13:20:27 mroe1934:
`
`
`
`T > 13:21:12 mroel934:
`
`
`
`F > 13:21:39 mroe1934:
`
`
`
`in tonight's game
`
`
`
`
`
`
`Hello, Mary.
`
`
`Hi, John
`
`
`How are you?
`
`
`
`I'm sick. I can't play
`
`
`
`
`
`
`
`
`mjohnson1934
`
`
`
`
`
`
`
`ey, M], are you free tonight?
`
`
`
`
`
`
`
`
`684
`
`
`
`688
`
`
`
`FIG. 19
`
`604
`
`
`
`Patent Owner Exhibit 2001, Page 17
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 17
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`
`U.S. Patent
`
`
`
`
`
`Feb. 20, 2007
`
`
`
`
`Sheet 16 of 21
`
`
`
`US 7,181,497 B1
`
`
`
`
`BUI — Conversations
`
`
`
`
`
`
`
`Hello, Mary.
`T > 13:20:05 mIoe1934:
`
`
`
`
`
`Hi, John
`F > 13:20:27 mme1934:
`
`
`
`
`
`How are you?
`T > 13:21:12 mroel934:
`
`
`
`
`
`> 13:21:39 mroe193416941'm sick. 1 can't play
`
`
`
`
`
`13.151
`
`
`
`
`
`
`
`
`T > 13:23:14 mjohnson1934:
`Hey1 M], are
`
`
`
`
`
`{4696
`you free tonight?
`
`F >13:23:32 mjohnsonl934:
`{Yes}
`
`
`704
`
`
`EU! — Conversations
`
`
`
`
`
`
`T > 13:20:05 11110131934:
`
`
`
`F > 13:20:27 mroe1934:
`
`
`
`T > 13:21: 12 mrocl934:
`
`
`
`P > 13:21:39 mroe1934:
`
`
`in tonight's game,
`
`
`
`T > 13:23:14 mjohnson1934:
`
`
`
`you free tonight?
`
`
`
`F > 13:23:32 mjohnson1934:
`
`
`
`
`Hello, Mary.
`
`
`Hi, John
`
`
`How are you?
`
`
`
`I'm sick. 1 can't play
`
`
`
`
`
`
`
`Hey, M], are
`
`
`
`Yes.
`
`
`
`
`
`
`
`
`
`
`FIG. 21
`
`Patent Owner Exhibit 2001, Page 18
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 18
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`
`U.S. Patent
`
`
`
`
`
`Feb. 20, 2007
`
`
`
`
`Sheet 17 0f 21
`
`
`
`US 7,181,497 B1
`
`
`
`
`BUI — Conversations
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`T > 13:20:05 mroe1934:
`
`
`
`
`F > 13:20:27 mroel934:
`
`
`
`T> 13:21:12 mroel934:
`
`
`
`F > 13:21 :39 1111061934:
`
`
`
`in tonight's game.
`
`
`T > 13:23:14 mjohnson1934:
`
`
`
`you free tonight?
`
`
`
`F > 13:23:32 mjohnson1934:
`
`
`
`
`Hello, Mary.
`
`
`Hi, John
`
`
`How are you?
`
`
`
`I'm sick. 1 can't play
`
`
`
`
`
`
`
`Hey, M], are
`
`
`
`
`
`
`
`Yes.
`
`
`
`710
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`BUI — Conversations
` T > 13:20:05 mroe1934:
`
`
`
`
`
`Hello, Mary.
`
`
`
`
`
`
`F > 13:20:27 mroe1934:
`Hi, John
`
`
`
`
`
`T> 13:21:12 1111061934:
`How are you?
`
`
`
`
`
`
`
`F > 13:21 :39 mroel934:
`I'm sick. I can't play
`
`
`
`
`in tonight's game.
`
`
`
`T > 13:23:14 mjohnson1934:
`
`
`
`you free tonight?-
`
`
`
`
`
`Yes.
`F > 13:23:32 mjohnson1934:
`
`
`
`
`
`
`
`
`Hey, M], are
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` 706
`
`
`712
`
`
`
`
`
`
`mjohnson193 I Do you want to play tonight?
`
`612
`
`
`
`
`
`
`
`710
`
`
`
`714
`
`
`
`
`FIG. 23
`
`Patent Owner Exhibit 2001, Page 19
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 19
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`
`U.S. Patent
`
`
`
`
`
`Feb. 20, 2007
`
`
`
`
`Sheet 18 0f 21
`
`
`
`US 7,181,497 B1
`
`
`BUI - Conversations
`
`
`
`
`
`Howareyou?
`
`
`
`
`I'm sick. I can't play in tonight's
`
`Q13
`
`
`
`
`Hey, M], are you free
`
`
`
`
`
`
`
`
`
`
`T> 13:21:12 mroe1934:
`
`
`
`F > 13:21 :39 mroe1934:
`
`game.
`
`
`
`T > 13:23:14 mjohnson1934:
`
`tonight?
`Yes.
`
`
`
`
`
`F > 13:23:32 mjohnson1934:
`
`
`
`
`
`T >13125z3 mjohnson1934:
`Do you want to play
`716
`E
`720
`i—'—_T—I
`
`
`
`
`
`718
`flail3:25:38llmjohnson1934:|
`[Surei
`714
`
`
`
`
`
`
`
`724
`726
`722
`
`730
`612
`
`728
`
`
`FIG. 24
`
`
`BUI — Conversations
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`T> 13:21:12 mroe1934:
`
`
`F > 13:21:39 mroel934:
`
`game.
`
`
`T > 13:23:14 mjohnson1934:
`
`tonight?
`
`
`F > 13:23:32 mjohnson1934:
`
`
`T > 13:25:30 mjohnson1934:
`
`tonight?
`
`
`
`F > 13:25:38 mjohnson1934:
`
`
`
`
`
`
`How are you?
`
`
`
`
`I'm sick. I can't play in tonight‘s
`
`
`
`
`
`
`
`
`
`Hey, M3, are you free
`
`
`
`
`
`
`
`
`
`Yes.
`
`
`Do you want to play
`
`
`
`Sure.
`
`
`
`
`
`
`
`
`736
`
`
`
`
`FIG. 25
`
`Patent Owner Exhibit 2001, Page 20
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 20
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`
`U.S. Patent
`
`
`
`
`
`Feb. 20, 2007
`
`
`
`
`Sheet 19 0f 21
`
`
`
`US 7,181,497 B1
`
`
`BUI — Conversations
`
`
`
`5
`
`600
`
`
`
`
`
`game.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`T > 13:21:12 mroe1934:
`
`
`
`F > 13:21:39 mroe1934:
`
`
`
`
`T > 13:23:14 mjohnson1934:
`
`tonight?
`
`
`F > 13:23:32 mjohnson1934:
`
`
`T > 13:25:30 mjohnson1934:
`
`tonight?
`
`
`
`F > 13:25:38 mjohnson1934:
`
`738
`
`
`
`How are you?
`
`
`
`
`I'm sick. I can't play in tonight's
`
`
`
`
`
`
`
`
`
`Hey, M], are you free
`
`
`
`
`
`
`
`
`
`Yes.
`
`
`Do you want to play
`
`
`
`Sure.
`
`
`
`
`
`612
`
`rsmith1934 MJ is going to lay tonight.
`
`
`
`
`
`
`
`
`
`736
`
`
`
`
`740
`
`FIG. 26
`
`
`
`600
`
`
`
`
`
`BUI — Conversations
`
`
`
`T > 13:23:14 mjohnson1934:
`
`
`
`
`
`
`
`
`Hey, M], are you free
`
`
`
`
`
`
`
`T > 13:27:]
`
`lF >El13228:24IEs,mith
`
`
`
`750
`
`752
`
`754
`
`
`
`
`
`
`Yes.
`F > 13:23:32 mjohnson1934:
`
`
`
`
`Do you want to play
`T > 13:25:30 mjohnson1934:
`
`'
`746
`:
`:38 mjohnsfléfl:
`Sure.
`
`
`
`
`
`
`rsmith1934:
`M] is going to play tonigh
`1934:
`
`|
`lOkay.I
`
`
`
`740
`C
`
`
`
`
`
`
`1.
`
`
`
`756
`
`
`
`
`
`
`
`
`
`
`
`760
`
`Patth Owner Exhibit 2001, Page 21
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 21
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`
`U.S. Patent
`
`
`
`
`
`Feb. 20, 2007
`
`
`
`
`Sheet 20 of 21
`
`
`
`US 7,181,497 B1
`
`600
`
`
`
`
`
`
`
`
`
`
`Hey, M], are you free
`
`
`
`
`
`
`
`
`BUI — Conversations
`
`
`
`
`T > 13:23: 14 mjohnson1934:
`
`tonight?
`
`
`
`F > 13:23:32 mjohnson1934:
`
`
`
`
`T > 13:25:30 mjohnson1934:
`
`tonight?
`
`
`
`F > 13:25:38 mjohnsonl934:
`
`
`
`T > 13:27:17 mroe1934:
`
`
`
`F > 13:28:24 rsmith1934:
`
`612
`
`
`
`
`
`
`
`
`
`
`Yes.
`
`
`Do you want to play
`
`
`
`
`Sure.
`
`
`
`MI is going to play tonight.
`
`Okay.
`
`
`
`§1_
`
`
`
`
`
`
`762
`758
`
`
`
`
`.. MLbethereat6215.
`
`
`
`
`
`
`fl
`
`
`
`760
`
`
`
`764
`
`
`
`FIG. 28
`
`
`
`
`
`
`
`
`
`
`BUI — Conversations
`
`tonight?
`
`
`
`F >13:25:3_8 mjohnson1934
`
`
`
`
`766 I
`
`.
`
`
`
`
`
`770
`
`5
`
`
`Sure.
`M] is going to play tonight.
`
`
`
`
`Okay.
`
`
`M], be there t
`
`
`
`
`
`
`
`
`
`:
`
`
`'
`T>13z28z5
`
`
`[772
`6:15.
`
`[3%,]313206lfljohnson1934zl
`
`
`
`
`774
`778
`
`
`776
`
`782
`
`
`
`
`
`
`Okay, 1'11 see you then.
`
`
`
`
`
`
`
`Patent Owner Exhibit 2001, Page 22
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`
`
`784
`
`Patent Owner Exhibit 2001, Page 22
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`
`U.S. Patent
`
`
`
`
`
`Feb. 20, 2007
`
`
`
`
`Sheet 21 0f 21
`
`
`
`US 7,181,497 B1
`
`600
`
`
`
`
`
`
`BUI — Conversations
`
`tonight?
`
`
`
`
`
`F > 13:25:38 mjohnson1934:
`
`
`
`
`
`
`T > 13:27:17 rsmithl934: MI is going to play tonight:
`
`
`
`
`
`F > 13:28:24 rsmith1934:
`Okay.
`
`
`
`T > 13:30:54 mjohnson1934:
`
`
`
`
`F > 13:32:06 mjohnson1934:
`
`Sure:
`
`
`
`
`
`
`M], be there at 6115
`
`
`
`
`
`Okay, I'll see you then.
`792
`
`
`FIG. 30
`
`
`
`
`EU! — Conversations
`
`
`
`
`
`
`
`
`
`T > 13:27:17 rsmithl934:
`
`
`
`
`F > 13:28:24 rsmith1934:
`
`
`T > 13:30:54 mjohnson1934:
`
`6:15.
`
`
`
`F > 13:32:06 mjohnson1934:
`IT >!l13:34:48"mjohnson19341
`
`
`
`
`
`790
`
`794
`
`
`
`
`M] is going to play tonight:
`
`Okay:
`
`
`MJ, be there at
`
`
`
`
`
`
`
`Okay, I'll see you then.
`We are going to meet t 6:15.
`
`
`
`
`
`
`
`
`Patent Owner Exhibit 2001, Page 23
`Google Inc. V. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 23
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`1
`
`MESSAGING APPLICATION USER
`
`
`
`INTERFACE FOR AUTO-COMPLETING
`
`
`
`ADDRESS TEXT AND MODIFYING THE
`
`
`
`
`
`AUTO-COMPLETION BEHAVIOR
`
`
`
`
`CROSS REFERENCE TO RELATED
`
`
`APPLICATIONS
`
`
`
`
`
`
`
`
`
`This application is a continuation of US. application Ser.
`No. 09/404,757, filed Sep. 24, 1999, now US. Pat. No.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`6,539,421 and titled “Messaging Application User Inter-
`
`
`
`
`
`face”, which is incorporated herewith by reference.
`TECHNICAL FIELD
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`This application relates to a messaging application (e.g.,
`
`
`
`
`
`
`
`
`e-mail, instant messaging, chat rooms, etc.) user interface.
`BACKGROUND
`
`
`
`10
`
`
`
`15
`
`
`
`20
`
`
`
`25
`
`
`
`30
`
`
`
`35
`
`
`
`40
`
`45
`
`
`
`
`
`50
`
`
`
`55
`
`
`
`60
`
`
`
`65
`
`
`
`
`
`
`
`
`
`
`The computer system 100 illustrates in FIG. 1 represents
`
`
`
`
`
`
`
`
`
`a typical hardware setup for executing software that allows
`
`
`
`
`
`
`
`
`a user to perform tasks such as communicating with other
`
`
`
`
`
`
`
`computer users, accessing various computer resources, and
`
`
`
`
`
`
`viewing, creating, or otherwise manipulating electronic con-
`
`
`
`
`
`
`
`
`tentithat is, any combination of text,
`images, movies,
`music or other sounds, animations, 3D Virtual worlds, and
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`links to other objects. The system includes various input/
`
`
`
`
`
`
`
`
`output (I/O) devices (mouse 103, keyboard 105, display
`
`
`
`
`
`
`
`
`107) and a general purpose computer 100 having a central
`
`
`
`
`
`
`
`
`
`
`processor unit (CPU) 121, an I/O unit 117 and a memory 109
`
`
`
`
`
`
`
`
`that stores data and various programs such as an operating
`
`
`
`
`
`
`
`
`
`system 111, and one or more application programs 113. The
`
`
`
`
`
`
`
`
`computer system 100 also typically includes some sort of
`communications card or device 123 (e.g., a modem or
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`network adapter) for exchanging data with a network 127
`
`
`
`
`
`
`
`via a communications link 125 (e.g., a telephone line).
`
`
`
`
`
`
`
`As shown in FIG. 2, a user of a computer system can
`access electronic content or other resources either stored
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`locally at the user’s own client system 202 (for example, a
`
`
`
`
`
`
`
`personal or laptop computer) or remotely at one or more
`
`
`
`
`
`
`
`server systems 200. An example of a server system is a host
`
`
`
`
`
`
`
`computer that provides subscribers with online computer
`services such as e-mail, e-commerce,
`instant messaging,
`
`
`
`
`
`
`chat rooms, Internet access, online games, electronic news-
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`papers and magazines, etc. Users of a host computer’s online
`services typically communicate with one or more central
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`server systems 200 through client software executing on
`
`
`
`
`
`their respective client systems 202.
`
`
`
`
`
`
`
`
`In practice, a server system 200 typically will not be a
`single monolithic entity but rather will be a network of
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`interconnected server computers, possibly physically dis-
`persed from each other, each dedicated to its own set of
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`duties and/or to a particular geographical region. In such a
`case, the individual servers are interconnected by a network
`
`
`
`
`
`
`
`of communication links,
`in a known fashion. One such
`
`
`
`
`
`
`
`
`server system is “America Online 4.0” from America
`
`
`
`
`
`
`
`
`
`
`Online, Incorporated of Virginia.
`
`
`
`
`
`
`One increasingly popular computer network-based activ-
`
`
`
`
`
`
`ity is referred to as “instant messaging.” An instant message
`is a form of electronic communication between users of a
`
`
`
`
`
`
`
`
`
`
`
`
`
`computer network in which a window pops-up on the
`
`
`
`
`
`
`
`recipient’s computer screen “instantly” and without
`the
`
`
`
`
`
`
`recipient having to access an e-mail program or otherwise
`
`
`
`
`
`
`
`check for messages. An instant message appears essentially
`
`
`
`
`
`
`
`
`
`
`as soon as the message sender clicks the send button subject
`
`
`
`
`
`
`
`
`
`to any time or propagation delays the message may have
`encountered on the network. In comparison to most e-mail
`
`
`
`
`
`
`
`
`
`US 7,181,497 B1
`
`2
`
`
`
`
`
`
`
`
`
`
`applications, instant messaging enables users to communi-
`
`
`
`
`
`
`
`
`cate with each other in a more dynamic, urgent and inter-
`active manner.
`
`
`
`
`
`
`
`
`
`FIG. 3 is a screen shot of an Instant Message (IM) window
`
`
`
`
`
`
`
`130 as used in AOL’s Instant Messenger (“AIM”) system.
`
`
`
`
`
`
`
`
`
`As shown therein, the window 130 includes a text display
`area 131 and text entry area 132. Both users involved in the
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`IM under consideration (i.e., sender and recipient) would
`
`
`
`
`
`
`
`
`
`have a similar window displayed on his or her computer
`
`
`
`
`
`
`
`
`monitor. When one user (PhilliszC) types a comment 134
`in text entry area 132 and clicks the Send button 133 (or,
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`depending on the configuration, presses the “ENTER” key
`
`
`
`
`
`
`
`
`
`
`on the keyboard), the entered text (e. g., “Hey, did you see the
`
`
`
`
`
`
`
`
`
`game last night?”) is displayed in the text display area 131
`of the window 130 such that it is visible to both users After
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`FRsnafu enters a comment 135 in response and clicks the
`
`
`
`
`
`
`
`
`
`Send button 133,
`that comment 135 appears in the text
`
`
`
`
`
`
`
`
`
`display area 131 underneath the previous comment 134. This
`
`
`
`
`
`
`
`exchange of comments continues indefinitely until the users
`
`
`
`
`decide to terminate the exchange.
`
`
`
`
`
`
`
`Typically, instant messages can be sent to another user
`
`
`
`
`
`
`
`
`only when that user is presently signed on to the computer
`
`
`
`
`
`
`
`
`service. Users who are signed of are unavailable to receive
`
`
`
`
`
`
`instant messages. Accordingly, another popular innovation
`
`
`
`
`
`
`
`introduced by America Online is the “Buddy List,” which
`
`
`
`
`
`
`
`
`allows users to monitor when other specified users (“bud-
`
`
`
`
`
`
`
`
`
`dies”) are signed onto and/or of of the computer service
`
`
`
`
`
`
`under consideration (e.g., AOL Instant Messenger).
`
`
`
`
`
`
`
`As shown in FIG. 4, the Buddy List is implemented as a
`
`
`
`
`
`
`
`
`window 140 that lists specified users, or buddies, who are
`
`
`
`
`
`
`
`
`signed on to the AIM system. In the example shown, the
`
`
`
`
`
`
`
`
`
`Buddy List for user “PhilliszC” indicates that four of
`
`
`
`
`
`
`
`PhilliszC’s buddies 1417144 currently are signed on to the
`
`
`
`
`
`
`
`
`system and thus available to receive instant messages. The
`
`
`
`
`
`
`
`Buddy List is updated based on information received from
`a server to add or delete names of buddies as they sign on
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`and of, respectively. Such Buddy List updates can be
`
`
`
`
`
`
`accompanied by various audible and visual indications to
`
`
`
`
`
`
`
`
`
`help notify the user that a buddy has signed on or of.
`
`
`
`
`
`
`
`
`Users may send instant messages to, and exchange com-
`ments with, more than one other user at a time. Conventional
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`instant message client software typically creates a separate
`instant message window for each user that is sent an instant
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`message. For example, as shown in FIG. 5, if a user sends
`three instant messages to three other users, one to each of the
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`users, three separate instant message windows 130a, 130b,
`
`
`
`
`
`
`
`
`
`and 1300 are created. To change from one instant message
`window to another, the user typically must move and/or
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`press a button on the mouse, or press a sequence of keys on
`
`
`
`
`
`
`
`
`the keyboard, to activate the desired instant message win-
`dow.
`
`
`
`
`
`
`
`
`
`The present inventors recognized that some users may
`find it undesirable to have to switch between instant message
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`windows in order to send instant messages to and exchange
`comments with more than one other user at a time. There-
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`the present
`inventors recognized that
`it would be
`fore,
`
`
`
`
`
`
`
`
`desirable to provide users with a user interface through
`
`
`
`
`
`
`
`
`which a user can send messages to and exchange comments
`
`
`
`
`
`
`
`
`with one or more users without having to switch among
`several different windows.
`
`
`
`SUMMARY
`
`
`
`
`
`
`
`
`
`
`Implementations may include one or more of the follow-
`
`
`
`
`
`
`ing features. In one aspect, a computer-implemented method
`
`
`
`
`
`
`of addressing a message to a member of a plurality of
`
`
`
`
`
`
`potential message recipients may include maintaining a
`
`
`
`
`
`
`
`subset of a plurality of potential message recipients. Each
`
`
`
`
`
`
`
`potential message recipient may have an associated address,
`
`
`
`
`
`
`
`and the subset may be determined using a predetermined
`Patent Owner Exhibit 2001, Page 24
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`Patent Owner Exhibit 2001, Page 24
`Google Inc. v. Blackberry Ltd., IPR2017-00911
`
`

`

`US 7,181,497 B1
`
`3
`criterion. The method also may include auto-completing a
`partially entered address based on the subset of potential
`message recipients.
`In another aspect, a method of addressing electronic
`messages to users of a computer network may include
`providing a set of user-selectable signals that modify auto-
`completion behavior and auto-completing a partially entered
`address for a message based on entry of one or more of the
`set of signals.
`In another aspect, a method of exchanging instant mes-
`sages among users of a computer network may include
`providing an instance of a user interface having an element
`for receiving addresses of instant message recipients. The
`method also may include allowing a user to send indepen-
`dent instant messages to different recipients by specifying an
`intended recipient’s address in the instance of the user
`interface element.
`
`In another aspect, an instant messaging user interface may
`include a user interface element having an input element for
`receiving instant messages for more than one separate
`instant message exchange and an output element for dis-
`playing instant messages for more than one separate instant
`message exchange.
`In another aspect, an instant messaging system may
`include an instant message server and a plurality of clients
`connected to the instant message server via a network. Each
`client may have software embodied in a computer-readable
`medium including instructions for causing the client
`to
`provide a user interface having an element for receiving
`addresses. The software also includes instructions for caus-
`
`ing the client to allow a user to address instant messages to
`a first recipient via the user interface element while partici-
`pating in a first instant message exchange and to allow the
`user to address instant messages to another recipient via the
`user interface element while participating in another instant
`message exchange separate from the first instant message
`exchange.
`In another aspect, a protocol for addressing a message to
`a member of a plurality of potential message recipients may
`include one or more user-selectable signals for modifying
`auto-completion behavior, and a predetermined criterion for
`selecting a subset of the plurality of potential message
`recipients. Each potential message recipient may have an
`associated address.
`
`One or more of the following advantages may be realized.
`The user interface allows a user to send instant messages to
`and exchange comments with a plurality of other users
`without having to switch among several instant message
`windows and without having to clutter up the user’s display
`screen with several instant message windows. Moreover,
`automatically completing the address of a message based on
`a partiall

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket