I IIIII IIIIIIII II llllll lllll lllll lllll lllll lllll lllll lllll lllll lllll lllll 111111111111111111
`US 20040056893Al
`
`(19) United States
`(12) Patent Application Publication
`Canfield et al.
`
`(54)
`
`INSTANT MESSAGING INTERFACE HAVING
`A TEAR-OFF ELEMENT
`
`(76)
`
`Inventors: James Andrew Canfield, Arlington, VA
`(US); Kenneth Carbone, Annandale,
`VA (US); David Fairlie Colburn,
`Reston, VA (US); Linda Nols Myers,
`Purcellville, VA (US); Thomas E. Van
`Lenten, Ashburn, VA (US); Gregory
`Alan Willis, Arlington, VA (US)
`
`Correspondence Address:
`FISH & RICHARDSON P.C.
`1425 K STREET, N.W.
`11TH FLOOR
`WASHINGTON, DC 20005-3500 (US)
`
`(21)
`
`Appl. No.:
`
`10/284,429
`
`(22)
`
`Filed:
`
`Oct. 31, 2002
`
`Related U.S. Application Data
`
`(60)
`
`Provisional application No. 60/376,181, filed on Apr.
`30, 2002.
`
`(10) Pub. No.: US 2004/0056893 Al
`Mar. 25, 2004
`(43) Pub. Date:
`
`Publication Classification
`
`Int. Cl.7 ....................................................... G09G 5/00
`(51)
`(52) U.S. Cl. .............................................................. 345/753
`
`(57)
`
`ABSTRACT
`
`A user interface on a display enables user perception of
`information regarding a communications session that lever(cid:173)
`ages an instant messaging platform. The user interface
`includes an instant messaging application user interface and
`one or more tear-off elements corresponding to ongoing
`instant messaging communications sessions. Each tear-off
`element is configured to enable perception and selection by
`a user of a corresponding instant messaging communications
`session. Also, each tear-off element is configured to be
`independently visually separated from other elements of the
`instant messaging application user interface and maintained
`as a separate entity on the instant messaging application user
`interface.
`
`190-,.
`
`100
`
`' ' '::
`: : : : : :
`
`---······ D 196
`o o
`TV
`Remote oBo
`
`~f .... ~.···············~·
`:,~ill~: :; '~ootl);
`
`D
`PDA
`BBB····-·················-········
`·········
`88§ 192
`1
`Mobile
`
`6 1~
`
`~
`
`Phonre _ _ _ M_o_us_e _ _ _ _ --;-: .,..: .;..j .;../ ~! :;__;__·__,· ....... o .. ·~
`
`125
`l__
`
`170
`
`172
`
`Operating
`System
`
`Authoring
`Applicalion(s)
`
`Client
`Applicalion(s)
`
`Browser
`Appllcation(s)
`
`- - - -~ 1
`Com;iv~~;'ti-,=--i-------___J__{
`
`~1~
`~
`
`140
`Controller
`
`Facebook's Exhibit No. 1006
`001
`
`

`

`"'""
`>
`~
`00
`O'I
`Ul
`C
`C
`~
`C
`C
`N
`rF.J.
`d
`
`"'""
`-..J
`"'"" 0 ....,
`~ ....
`rF.J. =(cid:173)~
`
`,i;;..
`C
`C
`N
`Ul
`N
`:'i
`~
`~
`
`~
`
`.... 0 =
`~ ....
`O' -....
`~
`.... 0 =
`~ ....
`"Cl -....
`> "Cl
`~ .... ~ = ....
`
`I')
`
`I')
`
`""C
`
`Controller
`,140
`
`L115
`
`J'
`
`100
`
`Fig. 1
`
`CPU
`
`Communicati
`
`Device
`
`) ) )
`
`l.
`
`198
`
`-'
`
`: ............. ~
`
`.
`
`,.
`·····~
`
`Video
`
`: :
`
`· ·
`
`I I
`R;]~ 0
`
`196
`
`Display
`
`···································,
`····················--
`
`Application(s)
`
`Browser
`
`Application(s)
`
`Client
`
`Application(s)
`
`Authoring
`
`172
`
`System
`Operating
`
`MEMORY
`
`Mouse
`
`191
`
`~-------------
`
`PDA
`
`Keyboard
`
`170
`
`1L i (.)
`
`.9i
`
`Phone
`
`Mobl•
`gggr,.2
`
`_,,
`
`ODO
`
`D
`
`-195
`
`~~r;:r:i\···· ..........
`
`194
`
`193
`
`190---,.
`
`(120
`
`g
`
`Facebook's Exhibit No. 1006
`002
`
`

`

`Patent Application Publication Mar. 25, 2004 Sheet 2 of 17
`
`US 2004/0056893 Al
`
`0 ....
`....
`
`L.
`
`0
`
`~ ....
`
`II)
`
`~ ....
`
`...
`.!! g
`
`C
`0
`(.)
`
`D
`D
`
`~I
`
`IO
`M
`
`....
`
`0
`
`N ....
`
`I IO
`
`0 ....
`
`IO
`
`N ....
`
`Cl
`CD
`
`....
`
`U')
`
`....
`....
`
`N .
`C) ·-u.
`
`0
`IO
`
`....
`
`V :~
`•
`
`0
`M
`
`....
`
`I....
`
`.!! e c
`
`0
`(.)
`
`Facebook's Exhibit No. 1006
`003
`
`

`

`Patent Application Publication Mar. 25, 2004 Sheet 3 of 17
`
`US 2004/0056893 Al
`
`0 .... C")
`
`It)
`
`....
`....
`
`~I
`
`7
`
`-C:
`.! E
`a,
`0
`,, ~
`~ ui
`,, u,
`:l co
`
`It)
`0
`C")
`
`('I) . C')
`
`LL
`
`E
`
`a, -~ u, -C:
`
`a,
`0
`
`It)
`
`0 ....
`
`Facebook's Exhibit No. 1006
`004
`
`

`

`Patent Application Publication Mar. 25, 2004 Sheet 4 of 17
`
`US 2004/0056893 Al
`
`1 105
`
`Client System
`
`1 310
`
`IM System
`
`Render General Client UI including IM UI and
`General Interface Tear-Off Element
`
`Connect to IM host
`
`+ Gp
`~
`
`Render First Tear-Off Element for IM UI
`
`Send IM Message to First IM Buddy
`- - - - - - - - - - - - - - - - - - - - - - - - - - ,
`
`Provide IM message
`from First IM Buddy
`
`Provide IM message to
`First IM Buddy
`
`Render Second Tear-Off Element for IM UI
`
`Perform Tear-Off of IM General Interface Tear-Off Element
`
`Navigate to different functionality and Render updated UI
`
`Perform Tear-Off of Second Tear-Off Element
`
`Reattach IM General Interface Tear-Off Element
`
`Navigate to different functionality and Render updated UI
`
`Navigate to IM UI and reattach Second Tear-Off Element
`
`Fig. 4
`
`Facebook's Exhibit No. 1006
`005
`
`

`

`Patent Application Publication Mar. 25, 2004 Sheet 5 of 17
`
`US 2004/0056893 Al
`
`I
`
`i
`I
`•
`II) I
`
`r,.. C"-·
`II) a.
`~ :::,
`II)
`£ 1u
`:::, .c.
`~~
`
`I 11
`I , ..
`
`.
`i;:; l
`!.~
`~ (I
`iii
`ill
`
`.. b
`
`an
`CD
`LL
`
`:,..
`n
`
`i] ~ d
`i .. ~
`.. <
`l ;
`
`••• •
`
`Facebook's Exhibit No. 1006
`006
`
`

`

`"'""
`>
`~
`00
`O'I
`Ul
`C
`C
`~
`C
`C
`N
`rFJ.
`d
`
`"'""
`-..J
`0 ....,
`~ ....
`rFJ. =(cid:173)~
`
`O'I
`
`,i;;.,
`C
`C
`N
`~Ul
`N
`~ :;
`~
`
`.... 0 =
`~ ....
`O' -....
`~
`.... 0 =
`~ ....
`~ "Cl -....
`~ .... ~ = ....
`
`I')
`
`I')
`
`""C
`
`("z_~
`
`I 6<-J-f
`
`,-~----.-
`
`~~Z..J..Ji!._
`
`Fig. 6
`
`(1 tJ
`
`61 s-
`
`:ru 5'"1..tc
`
`(' 3 II)
`
`S-'2. s-
`
`('4J
`
`!:"]..."L-__,
`
`1{";2,_
`6'2V
`
`,2 J C
`6"2.. j6
`
`y6Z-J
`
`I*. oiJ~
`
`.
`
`1
`
`.
`
`I
`~ m~~ile e~~~:.ng
`rre, M
`.
`II Notify AOL
`fill Buddy Info
`
`b
`
`r-
`fi;:..::.:.:=..:._, .~,.....--,..--.__...,1,1~~~"V"'r:==:=ary.~§tct;Fl··r~H'.,~·c.~?:)1,T1;;1
`
`. ·--1
`
`~z2j
`
`I
`SurfinJerry: yep, what's up?
`ChattingChuck: you there? -52/,:
`
`67...."'2.. -.
`
`&"f_r
`
`f't'J~
`
`ts-o
`
`(to
`
`rs-~
`
`(46
`
`600
`
`Facebook's Exhibit No. 1006
`007
`
`

`

`Patent Application Publication Mar. 25, 2004 Sheet 7 of 17
`
`US 2004/0056893 Al
`
`~I
`
`I
`I
`
`...... .
`C')
`ii:
`
`Facebook's Exhibit No. 1006
`008
`
`

`

`Patent Application Publication Mar. 25, 2004 Sheet 8 of 17
`
`US 2004/0056893 Al
`
`Facebook's Exhibit No. 1006
`009
`
`

`

`Patent Application Publication Mar. 25, 2004 Sheet 9 of 17
`
`US 2004/0056893 Al
`
`~I
`
`I
`
`1111
`
`Facebook's Exhibit No. 1006
`010
`
`

`

`Patent Application Publication Mar. 25, 2004 Sheet 10 of 17 US 2004/0056893 Al
`
`I
`I
`
`.
`C> ·-u.
`
`Facebook's Exhibit No. 1006
`011
`
`

`

`Patent Application Publication Mar. 25, 2004 Sheet 11 of 17
`
`US 2004/0056893 Al
`
`~I
`
`--C)
`
`LL
`
`Facebook's Exhibit No. 1006
`012
`
`

`

`Patent Application Publication Mar. 25, 2004 Sheet 12 of 17
`
`US 2004/0056893 Al
`
`c(
`0
`0
`N ,...
`
`<C
`N
`~
`
`C)
`LL
`
`Facebook's Exhibit No. 1006
`013
`
`

`

`Patent Application Publication Mar. 25, 2004 Sheet 13 of 17
`
`US 2004/0056893 Al
`
`co
`0
`0
`N
`......
`
`I
`I
`
`Dl
`N
`"I"'"
`
`C>
`u.
`
`Facebook's Exhibit No. 1006
`014
`
`

`

`Patent Application Publication Mar. 25, 2004 Sheet 14 of 17 US 2004/0056893 Al
`
`.l;«:-ll .}i~
`
`"
`
`'Q
`
`z.
`Q .5 ~.;
`ii~~
`alz ! E
`1111.oJ•
`"
`
`(.)
`0
`0
`.....
`N
`
`""
`~
`.ii
`"
`,,,
`:,,,
`[
`c..
`[
`~
`:E
`t
`"''
`i
`-~
`f "" C
`~
`:,-Ii "::,
`~
`
`·5~
`"'-"
`:, ::,
`f! a
`
`l:)'1)
`
`~~
`
`.!!2
`" ~
`ii ii
`
`.
`.
`;
`
`I
`I;
`i
`
`. .
`.
`.
`
`(.)
`N
`~
`
`C)
`LL
`
`'
`" ~
`'
`~ ..
`;
`
`:E
`"'
`'E
`.E
`
`~
`
`I
`I
`I
`
`Facebook's Exhibit No. 1006
`015
`
`

`

`Patent Application Publication Mar. 25, 2004 Sheet 15 of 17
`
`US 2004/0056893 Al
`
`gf
`~
`.0
`h
`
`" 9 g
`
`C.
`
`C
`0
`0
`N .....
`
`;:.·~
`~
`R.
`t
`" r
`~ r-: :{
`£
`"' " 1
`"'
`
`1'i
`6
`:,:
`.;,;
`'-'
`
`6
`""
`C: "' '!:!
`
`G
`
`I
`;,
`
`""" ~
`Ii
`Ii'
`
`.
`
`C
`N
`
`'I'"" . C)
`
`lL
`
`Facebook's Exhibit No. 1006
`016
`
`

`

`Patent Application Publication Mar. 25, 2004 Sheet 16 of 17
`
`US 2004/0056893 Al
`
`"" ¥
`
`j:.
`l;
`e
`~
`~:
`~
`:,
`
`C
`
`5
`
`C
`
`.E
`E:
`{;_
`
`~
`.)'>
`:,
`!.;'_
`~-
`""
`~
`;: git
`..
`s, l
`~ iii
`
`I
`I
`
`w
`N
`'l"""
`
`C) ·-LL
`
`-I
`
`
`
`,..
`s
`.,
`i5
`.9
`.,
`"'
`.c "'
`~~!!:;
`=> E :,
`"'- j<.
`
`~ I
`
`w
`0
`0
`
`N -
`
`.:C:cr~~
`
`z,
`oi:_! £1.l
`'.8 C ~~
`in~~ I
`1111114:1 I
`"' .
`
`"l=
`~
`<=
`2
`
`Facebook's Exhibit No. 1006
`017
`
`

`

`Patent Application Publication Mar. 25, 2004 Sheet 17 of 17 US 2004/0056893 Al
`
`u.
`0
`0
`N ....
`
`I '
`I
`
`LL
`N
`""'"
`C)
`LL
`
`Facebook's Exhibit No. 1006
`018
`
`

`

`US 2004/0056893 Al
`
`Mar. 25, 2004
`
`1
`
`INSTANT MESSAGING INTERFACE HAVING A
`TEAR-OFF ELEMENT
`[0001] This application claims priority from U.S. Provi(cid:173)
`sional Application No. 60/376,181, filed Apr. 30, 2002,
`which is incorporated by reference.
`
`TECHNICAL FIELD
`
`[0002] The following description relates generally to pro(cid:173)
`viding an instant messaging interface having a tear-off
`element.
`
`BACKGROUND
`
`[ 0003] Online service providers facilitate access to infor(cid:173)
`mation and services by providing interactive Uis (User
`Interfaces) that help users navigate to desired resources.
`Generally, a UI allows a user to execute particular com(cid:173)
`mands or to link to certain locations by simply selecting
`screen objects such as icons, windows, and drop-down
`menus. The design of a UI has a significant impact on a
`user's online experience. In particular, the icons, the win(cid:173)
`dows, and the menus of a UI may be arranged to enable a
`user to locate preferred information and services quickly and
`easily.
`
`SUMMARY
`
`[0004]
`In one general aspect, a user interface on a display
`enables user perception of information regarding a commu(cid:173)
`nications session that leverages an instant messaging plat(cid:173)
`form. The user interface includes an instant messaging
`application user interface and one or more tear-off elements
`corresponding to ongoing instant messaging communica(cid:173)
`tions sessions. Each tear-off element is configured to enable
`perception and selection by a user of a corresponding instant
`messaging communications session. Also, each tear-off ele(cid:173)
`ment is configured to be independently visually separated
`from other elements of the instant messaging application
`user interface and maintained as a separate entity on the
`instant messaging application user interface.
`[0005]
`Implementations may include one or more of the
`following features. For example, the instant messaging
`application user interface may include a general interface
`tear-off element that is configured to enable perception and
`selection of several of the tear-off elements collectively and
`to enable collective visual separation of the several tear-off
`elements from other elements of the instant messaging
`application user interface. The general interface tear-off
`element may be, for example, a tab or a button. The interface
`may be configured to enable reattachment to other elements
`of the general interface. For instance, a tear-off element may
`be configured to be reattached to an interface other than the
`interface from which the tear-off element was separated.
`[0006]
`In one implementation, one or more tear-off ele(cid:173)
`ments may be dedicated to and enable perception and
`selection of a single corresponding instant messaging com(cid:173)
`munications session. The dedicated tear-off elements may be
`independently visually separable from other elements of the
`instant messaging application user interface. The dedicated
`tear-off elements may include, for example, tabs or buttons.
`The user interface may also include a manual status control
`associated with a dedicated tear-off element. For instance,
`the manual status control may enable an indication of
`
`whether a message in the corresponding instant messaging
`communications session has been perceived by the user.
`[0007]
`In one implementation, one or more of the tear-off
`elements may be rendered visually as an integral part of the
`instant messaging application user interface. In another
`implementation, the display of the tear-off element persists
`when the element is visually separated from other elements
`of the instant messaging application user interface. In yet
`another implementation, the tear-off element may be con(cid:173)
`figured to enable reattachment to other elements of the
`instant messaging application user interface.
`[0008] The tear-off elements may be configured to be
`separately manipulable. In one implementation, one or more
`of the tear-off elements may be configured to be separately
`removable from the instant messaging application user inter(cid:173)
`face, separately invokable, separately minimizable and/or
`separately movable.
`[0009]
`In one implementation, more than one of the tear(cid:173)
`off elements may be configured to be collectively visually
`separated from other elements of the instant messaging
`application user interface and maintained as a separate
`display element. In another implementation, a tear-off ele(cid:173)
`ment may configured to be individually visually separated
`from other elements of the instant messaging application
`user interface and maintained as a separate display element.
`In yet another implementation, the instant messaging appli(cid:173)
`cation user interface and tear-off elements may be config(cid:173)
`ured to display limited information about one or more
`concurrent instant messaging sessions. For instance, the user
`interface may enable a more detailed display of one or more
`of the instant messaging sessions through selection of a
`corresponding tear-off element.
`[0010] Aspects of the instant messaging interface having a
`tear-off element may be implemented by an apparatus and/or
`by a computer program stored on a computer readable
`medium. The computer readable medium may comprise a
`disc, a client device, a host device, and/or a propagated
`signal. In addition, aspects of the instant messaging interface
`having a tear-off element may be implemented in a client/
`host context or in a standalone or offline client device. The
`instant messaging interface having a tear-off element may be
`rendered in a client/host context and may be accessed or
`updated through a remote device in a client/host environ(cid:173)
`ment. The instant messaging interface having a tear-off
`element also may be rendered by the standalone/offline
`device and may be accessed or updated through a remote
`device
`in a non-client/host environment such as, for
`example, a LAN server serving an end user or a mainframe
`serving a terminal device.
`[0011] Other features will be apparent from the following
`description, including the drawings, and from the claims.
`
`DESCRIPTION OF DRAWINGS
`[0012] FIGS. 1-3 are block diagrams of a communications
`system.
`[0013] FIG. 4 is a flow chart of a process that may be
`implemented by the systems of FIGS. 1-3.
`[0014] FIGS. 5-11 and 12A-12F are illustrations of dif(cid:173)
`ferent graphical user interfaces that may be implemented by
`the systems of FIGS. 1-3 when executing the process of
`FIG. 4.
`
`Facebook's Exhibit No. 1006
`019
`
`

`

`US 2004/0056893 Al
`
`Mar. 25, 2004
`
`2
`
`[0015] Like reference symbols m the vanous drawings
`indicate like elements.
`
`DETAILED DESCRIPTION
`[0016]
`In general, one or more tear-off elements may be
`provided in an interface for instant messaging (IM) appli(cid:173)
`cations or other online applications. For example, tear-off
`elements may be provided to collectively form a tabbed IM
`user interface (UI), where each tear-off element represents a
`corresponding ongoing IM session. A user may tear-off one
`or more of the tear-off elements individually or collectively.
`Tear-off elements that have been torn off may be indepen(cid:173)
`dently or collectively reattached to the user interface from
`which they were torn, or they may be reattached to a
`different user interface. In addition, once torn, the tear-off
`elements may be separately or collectively manipulated,
`moved, minimized, invoked, and activated.
`
`[0017]
`In the example of a tabbed IM UI, the tear-off
`elements may be presented as tabs positioned adjacent to
`one another to enable selection of and switching between IM
`sessions, and other operations. When several tear-off ele(cid:173)
`ment tabs are concurrently shown, an active tab corresponds
`to the IM session currently being viewed or manipulated by
`the user, and inactive tabs correspond to the IM sessions
`which are not currently being viewed or manipulated by the
`user. A tear-off element tab typically includes an identifier,
`such as the screen name of an IM buddy, to identify the
`particular IM session to which the tab is assigned. When
`displayed, the identifier for an IM session typically is
`configured such that a user is able to read or otherwise
`recognize the identifier without additional information. A
`tear-off element tab also may include a status indicator to
`indicate whether a new IM message is waiting to be viewed
`in the IM session corresponding to that tear-off element tab.
`
`[0018] A tear-off element may be rendered by any type of
`hardware, software, device, computer, computer system,
`equipment, component, program, application, code, storage
`medium, or propagated signal. In one implementation, the
`tear-off element is rendered in a client/host context, and the
`tear-off element may be accessed or updated through a
`remote device in a client/host environment. In another
`implementation, the tear-off element is implemented in a
`standalone or offline client context, where the tear-off ele(cid:173)
`ment is rendered by the standalone/offline device and
`accessed or updated through a remote device in a non-client/
`host environment such as, for example, a LAN server
`serving an end user or a mainframe serving a terminal
`device.
`
`[0019] Typically, IM communications involve an instan(cid:173)
`taneous or nearly instantaneous communication between
`two users, where each user is able to perceive online
`presence information regarding other selected users ("bud(cid:173)
`dies"). The IM communications may be machine-to-ma(cid:173)
`chine communications that occur without intervention by, or
`communication through, an instant messaging server after a
`communication session is established or authentication is
`performed. Examples of IM communications include those
`provided by AIM (America Online Instant Messenger), AOL
`(America Online) Instant Messaging, Yahoo Messenger,
`MSN Messenger, and ICQ, among others. Although dis(cid:173)
`cussed below primarily with respect to IM applications, the
`tear-off element may be provided for other online applica(cid:173)
`tions such as chat, e-mail, and players for streaming media.
`
`[0020] For illustrative purposes, FIGS. 1 and 2 show an
`example of a communications system for implementing
`techniques for transferring electronic data. For brevity, sev(cid:173)
`eral elements in the figures described below are represented
`as monolithic entities. However, as would be understood by
`one skilled in the art, these elements each may include
`numerous
`interconnected computers and components
`designed to perform a set of specified operations and/or
`dedicated to a particular geographical region.
`
`[0021] FIG. 1 illustrates a communications system 100
`including a client system 105 communicating with a host
`system 110 through a communications link 115.
`
`[0022] The client device 120 typically includes a general(cid:173)
`purpose computer 170 having an internal or external
`memory 172 for storing data and programs such as an
`operating system 174 (e.g., DOS, Windows™, Windows
`95™, Windows 98™, Windows 2000™, Windows Me™,
`Windows XP™, Windows NT™, OS/2, or Linux) and one
`or more application programs. Examples of application
`programs include authoring applications 176 ( e.g., word
`processing programs, database programs, spreadsheet pro(cid:173)
`grams, or graphics programs) capable of generating docu(cid:173)
`ments or other electronic content; client applications 178
`(e.g., America Online (AOL) client, CompuServe client,
`AOL Instant Messenger (AIM) client, interactive television
`(ITV) client, Internet Service Provider (ISP) client, or
`instant messaging (IM) client) capable of communicating
`with other computer users, accessing various computer
`resources, and viewing, creating, or otherwise manipulating
`electronic content; and browser applications 180 (e.g.,
`Netscape's Navigator or Microsoft's Internet Explorer)
`capable of rendering standard Internet content and other
`content formatted according to standard protocols such as
`the Hypertext Transfer Protocol (HTTP).
`[0023] One or more of the application programs may be
`installed on the internal or external storage 172 of the
`general-purpose computer 170. Alternatively, in another
`implementation, the client controller 125 may access appli(cid:173)
`cation programs externally stored in and/or performed by
`one or more device(s) external to the general-purpose com(cid:173)
`puter 170.
`
`[0024] The general-purpose computer 170 also includes a
`central processing unit 182 (CPU) for executing instructions
`in response to commands from the client controller 125, and
`a communication device 184 for sending and receiving data.
`One example of the communication device 184 is a modem.
`Other examples include a transceiver, a set-top box, a
`communication card, a satellite dish, an antenna, a network
`adapter, or some other mechanism capable of transmitting
`and receiving data over the communications link 115
`through a wired or wireless data pathway 150. The general(cid:173)
`purpose computer 170 optionally includes a television
`("TV") tuner 186 for receiving television programming in
`the form of broadcast, satellite, and/or cable TV signals. The
`TV tuner 186 permits the client device 120 to selectively
`and/or simultaneously display network content received by
`communications device 184 and TV programming content
`received by the TV tuner 186.
`
`[0025] The general-purpose computer 170 may include an
`input/output interface 188 that enables wired or wireless
`connection to various peripheral devices 190. Examples of
`peripheral devices 190 include, but are not limited to, a
`
`Facebook's Exhibit No. 1006
`020
`
`

`

`US 2004/0056893 Al
`
`Mar. 25, 2004
`
`3
`
`mouse 191, a mobile phone 192, a personal digital assistant
`193 (PDA), an MP3 player (not shown), a keyboard 194, a
`display monitor 195 with or without a touch screen input, a
`TV remote control 196 for receiving information from and
`rendering information to users, and an audiovisual input
`device 198.
`
`[0026] Although FIG. 1 illustrates devices such as a
`mobile telephone 192, a PDA 193, and a TV remote control
`196 as being peripheral with respect to the general-purpose
`computer 170, in another implementation, such devices may
`themselves include the functionality of the general-purpose
`computer 170 and operate as the client device 120. For
`example, the mobile phone 192 or the PDA 193 may include
`computing and networking capabilities and function as a
`client device 120 by accessing the delivery network 160 and
`communicating with the host system 110. Furthermore, the
`client system 105 may include one, some or all of the
`components and devices described above.
`
`[0027] Referring to FIG. 2, a communications system 200
`is capable of delivering and exchanging data between a
`client system 105 and a host system 110 through a commu(cid:173)
`nications link 115. The client system 105 typically includes
`one or more client devices 120 and/or client controllers 125,
`and the host system 110 typically includes one or more host
`devices 135 and/or host controllers 140. For example, the
`client system 105 or the host system 110 may include one or
`more general-purpose computers (e.g., personal computers),
`one or more special-purpose computers (e.g., devices spe(cid:173)
`cifically programmed to communicate with each other and/
`or the client system 105 or the host system 110), or a
`combination of one or more general-purpose computers and
`one or more special-purpose computers. The client system
`105 and the host system 110 may be arranged to operate
`within or in concert with one or more other systems, such as,
`for example, one or more LANs ("Local Area Networks")
`and/or one or more WANs ("Wide Area Networks").
`
`[0028] The client device 120 and the host device 135 are
`generally capable of executing instructions under the com(cid:173)
`mand of, respectively, a client controller 125 and a host
`controller 140. The client device 120 and the host device 135
`are connected to, respectively, the client controller 125 and
`the host controller 140 by, respectively wired or wireless
`data pathways 130 and 145, which are capable of delivering
`data.
`
`[0029] The client device 120, the client controller 125, the
`host device 135, and the host controller 140 typically each
`include one or more hardware components and/or software
`components. An example of a client device 120 or a host
`device 135 is a general-purpose computer (e.g., a personal
`computer) or software on such a computer capable of
`responding to and executing instructions in a defined man(cid:173)
`ner. Other examples include a special-purpose computer, a
`workstation, a server, a device, a component, other physical
`or virtual equipment or some combination of these capable
`of responding to and executing instructions. The client
`device 120 and the host device 135 may include devices that
`are capable of establishing peer-to-peer communications.
`
`[0030] An example of client controller 125 or host con(cid:173)
`troller 140 is a software application loaded on the client
`device 120 or the host device 135 for commanding and
`directing communications enabled by the client device 120
`or the host device 135. Other examples include a program,
`
`a piece of code, an instruction, a device, a computer, a
`computer system, or a combination of these for indepen(cid:173)
`dently or collectively instructing the client device 120 or the
`host device 135 to interact and operate as described. The
`client controller 125 and the host controller 140 may be
`embodied permanently or temporarily in any type of
`machine, component, physical or virtual equipment, storage
`medium, or propagated signal capable of providing instruc(cid:173)
`tions to the client device 120 and the host device 135.
`
`[0031] The communications link 115 typically includes a
`delivery network 160 making a direct or indirect commu(cid:173)
`nication between the client system 105 and the host system
`110, irrespective of physical separation. Examples of a
`delivery network 160 include the Internet, the World Wide
`Web, WANs, LANs, analog or digital wired and wireless
`telephone networks (e.g. Public Switched Telephone Net(cid:173)
`work (PSTN), Integrated Services Digital Network (ISDN),
`and Digital Subscriber Line (xDSL)), radio, television,
`cable, or satellite systems, and other delivery mechanisms
`for carrying data. The communications link 115 may include
`communication pathways 150, 155 that enable communica(cid:173)
`tions through the one or more delivery networks 160
`described above. Each of the communication pathways 150,
`155 may include, for example, a wired, wireless, cable or
`satellite communication pathway.
`
`[0032] FIG. 3 illustrates a communications system 300
`including a client system 105 communicating with a buddy
`client system 305 and an IM host system 310 through a
`communication link 115. Such a communications system
`may be used by users of IM service providers, such as, for
`example, AIM, ICQ, Yahoo Messenger, and Microsoft Mes(cid:173)
`senger.
`In one implementation, the IM host system 310
`[0033]
`may have characteristics similar to those described above
`with respect to host system 110, and the client system 105
`and the buddy client system 305 may include communica(cid:173)
`tion software to enable users of the client systems to the IM
`host system 310.
`
`[0034] The IM host system 310 may support IM services
`irrespective of a user's network or Internet access. Thus, the
`IM host system 310 may allow users to send and receive
`IMs, regardless of whether they have access to any particular
`ISP. The IM host system 310 also may support associated
`services, such as administrative matters, advertising, direc(cid:173)
`tory services, chat, and interest groups related to the IM. The
`IM host system 310 has an architecture that enables the
`devices (e.g., servers) within the IM host system 310 to
`communicate with each other. To transfer data, the IM host
`system 310 employs one or more standard or exclusive IM
`protocols.
`
`[0035] To access the IM host system 310 to begin an IM
`session in the implementation of FIG. 3, the client system
`105 establishes a connection to the IM host system 310.
`Once a connection to the IM host system 310 has been
`established, the client system 105 may directly or indirectly
`transmit data to and access content from the IM host system
`310. By accessing the IM host system, a user can use the IM
`client application to view whether particular users ("bud(cid:173)
`dies") are online, exchange IMs with particular buddies,
`participate in group chat rooms, trade files such as pictures,
`invitations or documents, find other buddies with similar
`interests, get customized information such as news and stock
`
`Facebook's Exhibit No. 1006
`021
`
`

`

`US 2004/0056893 Al
`
`Mar. 25, 2004
`
`4
`
`quotes, and search the Web. Buddy client system 305 may be
`similarly manipulated to establish a contemporaneous con(cid:173)
`nection with IM host system 310.
`
`[0036] Once connectivity is established, a user who is
`using client system 105 may view whether a buddy using
`buddy client system 305 is online, and typically may view
`whether the buddy is able to receive IMs. If the buddy is
`online, the user may exchange IMs with that buddy.
`
`[0037]
`In one implementation, the IMs sent between client
`system 105 and buddy client system 305 are routed through
`IM host system 310. In another implementation, the IMs
`sent between client system 105 and buddy client system 305
`are routed through a third party server (not shown), and also
`may or may not be routed through IM host system 310. In
`yet another implementation, the IMs are sent directly
`between client system 105 and buddy client system 305.
`
`[0038] Referring to FIG. 4, a client system 105 and an IM
`host system 310 interact according to a procedure 400 to
`provide a tear-off element for instant messaging (IM) appli(cid:173)
`cations or other online applications. The procedure 400 may
`be implemented by any type of hardware, software, device,
`computer, computer system, equipment, component, pro(cid:173)
`gram, application, code, storage medium, or propagated
`signal. Furthermore, although not shown in FIG. 4, the
`client system 105 and the IM host system 310 may be
`directly or indirectly interconnected through known or
`described delivery networks, examples of which are
`described with respect to network 160. In one implementa(cid:173)
`tion, the procedure 400 may be implemented in a client/host
`context, and the tear-off element may be provided for instant
`messaging (IM) applications or other online applications
`through a remote device in a client/host environment. In
`another implementation, the procedure 400 may be imple(cid:173)
`mented in a standalone or offline client context, and the
`tear-off element may be provided for instant messaging (IM)
`applications or other online applications by the standalone/
`offline device and may be accessed or updated through a
`remote device in a non-client/host environment such as, for
`example, a LAN server serving an end user or a mainframe
`serving a terminal device. The procedure 400 may be
`implemented to provide tear-off elements for instant mes(cid:173)
`saging (IM) applications or other online applications of any
`OSP or ISP.
`
`[0039] Procedure 400 generally involves rendering a tear(cid:173)
`off element for instant messaging (IM) applications or other
`online applications. While some functions of procedure 400
`may be performed entirely by the client system 105, other
`functions may be performed by the collective operation of
`the client system 105 and the IM host system 310. For
`example, a tear-off element may be rendered entirely by the
`client. However, the UI may be rendered based upon infor(cid:173)
`mation provided to the client by the IM host system.
`
`In procedure 400, a general client UI, including an
`[0040]
`IM UI and a general interface tear-off element, is rendered
`(step 405). For example, FIG. 5 illustrates an example of a
`general client user interface (UI) 500 that may be presented
`to a user of an online service provider. The UI 500 includes
`a toolbar 505 for quickly enabling activation of features such
`as, for example, reading or writing e-mail, exchanging IM
`messages with another user, entering chat areas with other
`users, sho