CA2634220A1

CA2634220A1 - Contact list display system and method

Info

Publication number: CA2634220A1
Application number: CA002634220A
Authority: CA
Inventors: Paulo Taylor; Jan-Joost Rueb; Onno Bakker
Original assignee: Individual
Current assignee: Ebuddy Technologies BV
Priority date: 2005-12-09
Filing date: 2006-12-11
Publication date: 2007-06-09
Anticipated expiration: 2026-12-11
Also published as: CA2632706A1; EP1969786A2; US20070168529A1; EP1969787A2; US10536412B2; US11438291B2; EP1969785A2; US20120036517A1; US20150081786A1; US10735364B2; WO2007129144A3; US20100228747A1; US11012393B2; US20220014490A1; US20230006959A1; US8510395B2; US8700713B2; CN101379785A; EP1969786B1; US20210352031A1

Abstract

A technique for contact list aggregation across networks involves logging into low level networks through a high level network. A system constructed according to the technique may include a network interface coupled to the different low level networks. The system may further include a contact aggregation engine coupled to the network interface and a network contacts database. In operation the system logs into one or more of the low level networks (or facilitates login for a user). To the extent that the data in the network contacts database is not current, the contact aggregation engine updates the networks contacts database contact information, then provides an aggregated contact list including the contact information to a display device. A
method according to the technique may include logging into a high level network and displaying contacts from the one or more low level networks in an aggregated contact list. The method may further include logging into the one or more low level networks.

Description

' ~""= .~a.

CONTACT LIST DISPLAY SYSTEM AND METHOD
BACKGROUND
Instant messaging requires the use of a client prograni that hooks up an instant messa;ing service and differs from e-mail in that conversations are then able to happen in real time. Most services offer a presence information feature, indicating whether people on one's list of'contac.ts are currently online and available to chat. This inay he called a contact list. In early instant messaging programs, each letter appeared as it was typed. anii when letters were deleted to cot7-ect typos this was also seen in real time. 'rhis made it more like a telephone coiiversation than exchanging letters. In modem instant messaging programs, the other party in the conversation generally only sees each line of text right aher a new line is started. Most instant messaging applications also include the ability to set a status message, roughly analogous to the niessage on a telephone answering machine.

Popular instant messaging services on the public Internet include NET
Messenger Service, AOL Instant Messenger, Excite/Pal, Gadtt-Gadu, Google Talk, iChat, ICQ, Jabber, Qnext, QQ, Meetro, Skype, Trillian and Yahoo! Messenger. These services owe many ideas to an older (and still popular) online chat medium known as Internet Relay Chat (IRC).

The foregoing examples of the related art and limitations related therewith are intended to be illustrative and not exclusive. Other limitations of the related art will become apparent to those of skill in the art trpon a reading of the specification and a study of the drawings.
SUMMARY
The following embodiments and aspects thereof are described and illustrated in conjunetion with systenis, tools, and methods that are meant to be exemplary and illustrative, not limiting in scope. In various embodiments, one or more of the above-described problems have been reduced or eliminated, while other embodiments are directed to other improvenients.

A technique for contact list aggregation across a plurality of different networks involves logging into low level networks through a high level network. A system constructed according to the technique may incltide a network interface coupled to the different low level networks.
The system may fttrther include a cotitact aggregation engine coupled to the network interface and a netwot-k contacts database. In operation the system logs into one or more of the low level networks (or facilitates login for a user). The network contacts database rrtay include some inl'ormation about coiitacts associated with the networks fi-orn, by way of'exarnple bttt not 91004-0013/LEGAL 12877050.1 tA~-,,*~.

timitation, previous lobins ot- data explicitly entered by a tiser. To the cxtent that the data in the nvtwork colitacts database is not etn-rent, the contact ageruoation engine updates the networks contacts database contact infonnation, then provides an aggregated contact list including the cotttact infonuation to a display device.

A metiiod according to the technique may inclttde logging into a lligh level network anci displaying contacts trom the onc or more low level networks in an aggregated contact list. The mcthod ntay further inclu.de logging into thc one or mor=e low level networks.

13RIEF DESCRIPTION OF THE .DRAW INGS
Embodiments of the inventions are illustrated in the figures. However, the enibodiinents and Fgures are illustrative rather than limiting; they provide examples of the invention, FIG. I depicts an example of a system for providing instant messages to clients via a web interface.

FIG. 2 depicts an example of a system for displaying content from an IM client at an alternative IM. client.

FIG. 3 depicts an example of a system capable of contact aggregation and display.
FIGS. 4A-4B depict examples of screenshots that depicts a multi-network IM
display.

F1G. 5 depicts a flowchart of an example of a method for contact list aggregation and display.
FIG. 6 cicpicts a f]owchart of an example of a niethod for aggregated contact list display.

FIG. 7 depicts a computer system suitable for implementation of the techniques described with reference to FIGS. 1-6.

2 91004-0013/LEGAL12877050.1 Ok 63017=8005. W001 DETAILED .DESCRIPTION
In the following description, several specific details are presented to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention can be pr~icticed Without one or more of the speciiic details. or in conihinauion wiih other components, etc. I.n other instances, well-known implementations or operations are not shown or di:scribecl in detail to avoid obscuring aspects of various embodiments, of the invention.

FIG. 1 depicts an example of a system 100 for providing instant messages to clients via a web interface. In the exam.ple of FIG. 1, the system 100 includes a network 102, a server 104, and an fnstant Messenger (IM) server 106, and an IM network 108. The server 104 is coupled to the network at least by way of port 80. The two way communi.cation via port 80 is represented in the example of FIG. I as an arrow 110. The server 104 is coupled to the IM
server 106 via one or more other ports. The two way coninitutication via the other ports is represented in the example of FIG. I as an arrow 112. The IM server 106 is coupled to the IM
network 108 via auy known or convenient mechanist.n. Indeed, the IM server 106 may be thought of as part of the IM
tietrivork 108. The network 102 couples a plurality of clients 114-1 to 114-N
(referred to collectively as clients 114) to the server 104. In the example of FIG. 1, the server 104 includes an event queue 116.

The network 102 may include by way of example but not limi.tation LAN, WAN, VLAN, WLAN. Internet, cellular network, phone network, radio network, or some other known or convenient network. The tet-m "Internet" as used herein refers to a network of netivorks that uses certain protocols, such as TCP/IP, atid possibly other protocols such as the hypertext transfer protocol (HTTP) for hypertext markup language (HTML) docunlents that make up the World Wide Web (tlie web). The physical connections of the lnternet and the protocols and communication procedures are well known, but any convenient physical connections or protocols could be used.

The server 104 may include a multiple servers. Indeed, it may be desirable, depending upon details of a particular implementation, to install several servers to cope with the number of siniultaneous users the systeni 100 supports. It may ftu-ther be desirable, depending upoti details of a particular implementation, for the server 104 to have a high CPLI
througllput, tocietlier with large amounts of RAM, to handle a large nuniber of users. It mav fiirther be clesirable, depending upon details of a particular imlalemerttation, to accomplish resource stiaring via thread handling where a pool of threads is shared and used bv one or more of the clients 114 for client-server communication and between the servei- 104 and the IM server 106.

3 91004-0013; L E GAL 12877050.1 6.3017=8005WOU1 The server 104 may include one or more of an application servet', database server, web server, baiulers server, and content server, or any combination tliereof. 'fo rnake the most of the techniqucs described herein, the server 104 should, though is not required to, irtclude at least one application server. 'I'he other servers can 11ave supporting roles in, by way of example but not timitation. serving static content or advertising (e.g., banners), storing usage data, or fulflling some other known or convenient function.

The server 104 may act as a proxv server between the clients 1 t 4 and the IM
set-ver 106. The server 104 receives communications from the clients 114 on http port 80, and responds to the clients 114 on http port 80. Communications from the clients 114 that are bound for the [M network 108, however, must also come through http port 80 to the server 104, and are then 1"ottivarded to the IM server 106. In this way, ttie server 104 acts as a carrier of the data from users to the IM network 108 using a mechauism that controls attd manages the data (e.g., text niessages, display images, enioticons, audio/video streams, etc.) sent between one of the clients 114 and the sei-ver 104, and vice versa.

The IM server 106 may be any known or convenient IM sei-ver that is compatible with 1M. Events, messages, or other appropriate data from the IM server [06 are collected in the event queue 116 of the server 104. The everits may be collected in association with a variety of protocols including by way of example but not limitation port 1863, port 5050, port 5222, port 5190, etc.

The IM network 108 may include one or a conibination of networks selected from MSN
Messenger, Yahoo! Messenger, AIM AOL, ICQ, QQ, Jabber, Google Tatk, [RC, or some other known or convenient IM network.

The clients 114 may include any known or convenient device, including by way of example but not liniitation, a Web browser, mobile client, PDA, game console, TV box, native application, etc. I'he clients poll the server 104 for events. The events can be removed from the event queue 116 and translatect into text, JavaScript, XML, or some ottier known or convcnient format that one or more of the clients 114 need or expect in order to process data associated with the event.

T'o interact with the IM network 108, the clients 114 send data to the server 104. The data, which mav include commands, is processed and translated into corresponding data that will be seni to the appropriate IM network. In an enibodiinent., the appropr-iate IN/I network niav be detertninable based upon the protocol encoded in a message.

4 91004-0013lL E GAL 12877050.1 63017-8005.WO0 i !vlessa<res or actions from the clients 114 are collected over network protocols such as, by way of example but not limitation, HTTP or plain socket connections. The messages or actions sire transfi:>rmed to an appropriate protocol format to be sent over a compliant port from tlic clicnts 114 to the server 104, with thc IM protocol on the application side. In a non-lim;ting tilc C;impliau port is hup pon 8it. Hu~~ever, tunypurt simiiar chai-acteristics to those of a typical port 80 could be used.

The latest available browsers, as of Deceinber 2005, enable the use of a techniqtle called AJAX (Asynchronous JavaScript And XML). With AJAX, appropriately configured clients 114 can e;tei:ute actions and poll for messages or events using only JavaScript.
The method is based on using an XMLF1ttpRequest object to make I-ITTP requests to th.e server 104.
The server 104 mav reply with messages taken from the qucue of the corresponding session in XML. (or another) format that are parsed and displayed according to the message content.

For clients 114 that include a browser, when accessing the server 104 the browser typically uses hidden HTML frames to update information on visible frames. The visible frames display appropriate inl'ormation while the hidden frames are reloaded in short periods of time. In each refresh thai hiis the server 104, the browser ident.ifes the current messaging session and checks ifnew event5 or niessages associated with the session are in the event queue 116. When flt:\~, lntUCIIt:1tWI1 ar:ives and needs to be clisplayed in sonie form, the bro\vser makes use of, for example, JavaScript code to update the visible frames and windows with new messages or events keeping the information up to date in the screen. In this way, automatic refreshing can take place in a hidden frame.

In another embodiment, certain of the clients 114 with browsers niay not nlake use of refreslies. For example, a form of updating the screen without using a refresh tecluiique is to keep one single HTTP socket request alive for the whole period of a messaging session without actually closing the socket connection. In this example, information is initially loaded and displayed in one single visible frame. While events aiid messages are being received by the server 104, JavaScript code can be injected into the HTML document through the same I-ITTP
socket kept alive and managed by the server 104. For each event or message, the browser can inteipret the JavaScript code injected and the co.tresponding parts of the HTNIL docuinent and windoWs will bc updated.

In another enibodiment, certain of the clients 114 with browsers may make use of manual refi=eshes. Some relatively unsophisticated browsers, such as WAP and xHTML
browsers often available on mobile p.hones, do not support hidden franies andlor JavaScript (and others may be contigured such that they do not support hidden frames andlor JavaScript). Tn

5 91004-0013.'L F GAL 128 7 7050.1 Oft 63017-8005, WO01 such cases, the inforniation displayed ttas to b(: updated manually by the user. ManuaI updating cnables any mobile phone, PDA, TV Set or ariy device with a browser to connect to the server 104 and use the messaging platforms made available by the server 104 assuring the coitinninication between the clients 114 and the IM server 106.

Message history can be stored by most IM clients on a local cotnputer. For alteniative web and mobile-based clients local storage may riot be possible. In a non-limiting embodiment, the server 104, may have the capability to storc message histor,v from IM
cotivei-sations done via one oi- more of the clients 114. The message history can be ace.essed and searched at any time via the server 104 by one or more of the clients 114 FIG. 2 depicts an example of a system 200 for displaying content from an IM
client at an alternative IM client. In the exainple of PIG. 2, the system 200 includes a client 202, an IM
network 204, a set-ver 206, an IM network 208, a client 210, other IM networks 212-1 to 212-N
(referred to collectively as other IM networks 212), and other clients 214-1 to 214-N (referred to collectively as other clients 214).

For illustrative purposes, it is assumed that the client 202 has content that is conipatible with the IM network 204. However, the client 210 is capable of reading content fotmatted to be compatible with the IM network 208. Thus, in operation, the server 206 collects content froni the client 202 (either through the IM network 204, as shown in FIG. 2, or directly from the client 202, such as is shown by way of exaniple in FIG. 1). The server 206 then forrnats the content as appropriate for use on the IM network 208. Once the content is properly formatted, it can be made available to the client 210 (either through the IM network 208, as sliown in FIG. 2, or directly to the client 210, such as is shown by way of example in FIG. I).
Depending upon the embodiment and/or implementation, the content may also be foi-matted as appropriate for one or more of the other IM networks 212, ta be made available for one or more of the other clients 214, In an embodiment, the server 206 can save the content in one or nlany formats.
Tn this way, ttie client 202 could make content available in a first IM fomiat, the server 206 could convert the content into a second IM fonnat, and the server 206 can save the content in at least the second TM fol-niat. Thus, the client 210 could receive the data in the seconcl IM fonnat. 'The server 206 could easily store the content in the first IM lori7iat, as well, and make the content, available to other clients coupled to the IM network 204. In addition, the server 206 could convert the content to other IM formats, such as those fonnats that are associatecl witli the otlier lM networks 212, and save the other IM fot-niats. In this way, the other clients 214 may have access to the content.

6 63017-8005. WO01 In a non-limiting enlbodiment, the client 202 may be able to view the client 2t0 and the c:lients 214 siniultancously. This is advantageous because IM clients typically cannot view IM
clients froni other 1M networks. AdvantaKeously, since the server 206 is used, the client 202 cuulcl evc;n include, for cxample, a mobile dL!vicu ~~,ithout a clicnt. (Of course. this coul(i he interpreted to mean that the client 202 is nut an IM client at all, thougii the term client is still used for illustrative purposes because the client 202 is sei-ved by the set-ver 206 in a client-server-like fashioti.) In a non-limiting embodiment, if the client 202 does not or cannot install client software, the client 202 can use a browser for web-based messaging and display.

FIG. 3 depicts an exaniple of a system 300 capable of contact aggregation .and display.
The systeiit 300 includes low level networks 302-I to 302-N (collectively refer-red to as t.he low level networks 302), a computer 304, and a display 306. The low level networks 302 may include, by way of example but not limitation, various IM networks. I.t may be noted that the computer 304 and the display 306 may be referred to, in certain implementations, as comprising a computer systenz.

The coniputer 304 includes a network interface 308, network login en;ines 310-I to 310-N (collectively referred to as network login engines 310), network contacts databases 312-1 to 312-N (collectively referred to as the network contacts database 312), a high level contacts database 314, a user profile database 316, and a contact aggregation engine 318.

The network interface 308 is coupled to the low level networks 302. In a typical implementation, the network interface 308 also couples the computer 304 to a network such as the Internet and/or a high level network (not shown).

The network login engines 310 may include logic and storage that facilitates login to the various low level networks 302. For example, the network login engine 310-1 may include a user name (and perhaps a password, if the password is not requested from the user at each login) associated with the low level network 302-1. Conceptually, each of the network login engines 310 is intended to represent the capability of login to the low level networks 302 in a general sense (i.e., the data and logic required for any device to connect to the low level networks 302) and a uscr-specific sense (e.g., the data provided frorri a user that enables login to accounts associated with the user).

The network contacts database 312, which is embodied in a computer-readable rnedium, includes contacts data associated with any of the networks into which a user has logged. When a user logs out, the data may oi- may not be cached (or stored in non-volatiie mernory) for future reference, depending upon the implementation and!or user configuration.

7 91004-00131LE GAL 1 2877050.1 63017 8005. W001 The higli level contacts database 414, which is embodied in a computer-readable medium, is an optional database that includes contacts associated with a high level network.
The liigh level contacts database is optional for at least two reasons. -I'he first reason is that a systcni need not provide thc ability to maintain high levcl contacts, requirin,11 lhat a user mainlairl only low level coritacts. The second reason is that even if the system provides the ability to maintain high level eontacts, a user niay opt not to maintain any higlt Icvcl contacts, opting uistead for low level contacts.

T'he user profile clatabase 416, which is embodied in a computer-readable medium, is intended to represent data associated with a user. The amount of data maintained is implenientation-speci fic.

The contact aggregation engine 418 is coupled to the databases 412, 414, 416, the network login engines 410, and the display 406. In operation, the contact aggregation engine 418 controls the network login engines 410 to login to or facilitate login by a user to the various low level networks 402. The databases 412, 414, 416 are accessed in such a way that a list of contacts stored in the netvvork contacts database 412 is aggregated and displayed on the display 406, as illustrated by the screenshots of FIGS. 4A-413, and the flowcharts of FIGS. 5-6.

FIGS. 4A-4I3 ciepiet exanrples of screenshots that clepicts a multi-network IM
display.
In many cases, a user will login to a high level account and adjust user configurations such that the system will autoniatically login the user to various low level accounts.
This may require storing login credentials so that the system can automatically login the user to each selected interface. FIG. 4A depicts an example of a screenshot 400A for a full screen display. In the example of FIG. 4A, the screenshot 400A includes a contacts list tab 402, an "add a network"
hyperlink 404, a plurality of MSN icons 406, a plurality of Yalioo! icons 408, and a plurality of AIM icons 410.

As the name implies, the contacts list tab 402 includes a listin.g of designated IM. client contacts. For an IM clicnt to be included in the listing, a user associated with ttie contact list typically must explicitly enter a client into the list. This may be accomplished with a single click. For exaniple, when a new IM client contacts the user, the user may be prompted to allow the IM. client to be enta-cd intc.i the user's contacts list.

As is suggested by the foldei-s depicted in the contacts list tab 402, a user may organize contacts in various folders. A single contact may be listed in no folders, one folder, or multiple folders, depending upon implementation and user confi gurations. Depending upon the implementation details, all contacts who are not currently online are listed in the "Offline" folder.

8 91004-0013/LE GAL 12877050.1 63017-8005. W(701 "1'he "ad<i a network" hyperlink 304 can be followed to add networks for display. In a non-tirniting embodiment, when a network is added. contacts of the user in the added netxuork are added to the contacts list tab 402. The added contacts are distinguishable by network using, for example, the icons 406, 408, 410.

In an alicmative embodiment, the contact list cottlci be maintained in a high level network (i.e., all ccmtacts are listed in the contact list, even if the contacts are from a network that has not been added). If a contact is a melnbet= of a network that is not added, the contact would presutnably be listed in the "Offline" folder because the contact is not known to the user to be online. However, depending upon the implenientation, the "Offline"
folder could be effectively split into two folders, if desired, one which indicates a contact is offfine, and one that indicates a contact is a member of a network that ltas not been added. In the example of FIG.
4A, this is implicit because the added networks have icon 406, 408, 410 associated with them, and each ofthe contacts have icons 406, 408, 410 associated with them. So, it is apparent from viewing the display whether a contact is or is not a member of a network that is currently added.

In a non-limiting embodiment, adding a network requires that the user be a member of the added network. For example, if the user wistles to add the MSN IM network, the user must have an IM account with MSN. However, in an alternative embodiment, a system could set up a dununy account for a user who wishes to add an account for a network with which the user is not a tnetnbcr. The dtun.my accotrnt will be associated with the user, but the user might feel tnore conlfortable with not ever logging in, remembering a password, etc. The system could handle all of these details for che user without the user's knowledge, and with.out exposing the user to security risks suct- as compromised passwords (since some users use the same password for multiple accounts, but in this case the system would generate a randoni, and presunlably strong, password for use witlt the accottnt).

FIG. 4B depicts an exatnple of a screenshot 400B fbr a mobile phone display.
In the example of FIG. 4B, the contact list includes a series of contacts and their associated network-identifyin; icons 406, 408, 410. The infot-tnation available on a niobile phone display is less than that of a full screen display, such as is available on, for example, a laptop display.

In the example of FIG. 4B, a user can add accounts by clieking on an "add account"
hyperlink 412. Depending upon the implementation, clicking on the "add account" hyperlink 412 could prompt the user to select an account from a list of accounts the user lias ah=eady designated in a contacts list (or add a new account), to select a list of accounts associated with a particular subset (see, e.g., the folders of FIG. 4A), to select a particular network (which may ine.htde logging the user in to the network or prompting the user to do so), storing log.in

9 9 1 004-00 1 31LEGAL 1287?050 1 63017-8005. WOa 1 credentials and, when logging in, the system can automatically login the user to each selected inti:ri~aWe, or to select accounts in sottZe othcr manner. I'rUõun,_ibiy, iCan accouut is selected for a contact that is a rnentber o1'a network in which thc user has ttot logged in, in a non-limiting embodimeni, either the user or the system will have to louin to the network.

In the example of FIG. 413, the user can remove accounts from the online list by clicking on a"signout" hyperlink 414 next to the accounts. Depending on the imptementatiott, clicking on the "siguout" hyperlink 414 may cause the ttset- to go offline with respect to the account associated with the particular "signout" hyperlinl<, or with all accounts on the same uetwork as the account associated with the particular "signout" hyperlink.
A"sigiout" hyperlink 416 may be used to sign out of all networks at once or, in a different implenientation, cause the user to be prompted regarding the networks from wliich to sign out.

In the exainple of FIG. 4B, the screenshot 400B includes a "reload" hyperlink 418_ It may be desirable to occasionally refresh the screen. Sotne mobile devices may even be incapable of refreshing without an explicit reload.

FIG. 5 depicts a flowchart 500 of' an example oi'a method for contact list aggregation and display. This method and other methods are clepicted as serially arranged rnodules.
However, tnodules of the methods may be reordered, or arranged for parallel execution as appropriate. In the example of FIG. 5, the flowchart 500 begins at module 502 where a high level network is joined. A high level network may inciude, by way of exaniple but not limitation, eBuddy.

In the example of FIG. 5, the flowchart 500 continues to module 504 where a low level network is joined. Low level networks may include IM networks, such as MSN
Messenger, Yalioo! Instant Messenger, AIM, or any otlier known or convenient network. It should also work properly if high level networks were joined as if the high level networks were low level.
For example, a member of a first high level network could join a second high level network, which in turn is associated with first and second low level networks. The second high level netwot-k would ittnction rather like a nocle in a tree, where the first liigh level nethvork is the root, and the leaves of ttie node ai-e the first and second low level rteriworks.
Thus, the second high level netwot-k could be thought of as a mid-level network. lJnless a distinction is needed, mid-level networks are treated as low level networks herein.

In the example of FIG. 5, the flowchart 500 continues to decision point 506 where it is determined whether to join more low level networks. If it is detennined that more low level networks are to bejoinetl (506-Y), then the flowchart 500 loops back to module 50=1, as 91004-0013/LEGAL 12877050.1 Av- Oftl.

described previously. il; on the other hand, it is detcrnlined that no more low level networks are to be joined (506-N), then the flowchart 500 cantinues to module 508 where a contact list associated with one or more of the low level nehvoi-ks is maintained.

While contact lists are not particularly inlpeu=tant in email environments (beeause you can write an email to anyone whose email address you know), in IM
environnients, contact lists are more desirable because users want to see wlio is online before sending an IM. If a contact is not ortline, IM is not allowed in many implenlcntations (and in an implementation that "allor.i-s"
1M with an offline contact, the communication is arguably not an instant message). Accordingly, at least in an IM environment, most users will maintain a contact list (508).

In the example of FIG. 5, the flowchatK 500 continues to module 51 tl where the high level networks is logged into. When a user logs into a high level network, the user will typically have a number of options, including requesting that a list of contacts be displayed. The list of contacts could also be displayed autotnatically upot- login, depending upon the irnpletuentation and user con figtu-ations.

In the exarnple of FIG. 5, the flowchart 500 continues to modute 512 where contacts from each of the low level networks are displayed in an aggregated contact list. Depending upon the implementation or user eonftguration, the contaet list could include high level contacts, too.
Also depending upon the implementation and/or user configuration, the user may or may not be required to login to each of the low level networks for which contacts are to be displayed in the aggregated contact list.

In the example of FIG. 5, the flowchart 500 contuiues to decision point 514 where it is detemZined whether to quit the high level network. If the user does not quit the high level network (514-N), then the tlowchart 500 continues to decision point 516 where it is determined whether the user logs out of the high level network. If it is deteimined that the user is to logaut of the high level network (516-Y), then the flowchart 500 continues to module 518 where the user logs out. Whetlier the user logs out (516-t', 518), ur not (516-N), the flowchart 500 loops back to decision point 506, as described previouslv.

In many cases, a user may never quit the high level network, however it is theoretically possible that a user would quit (or a user would be banneci ). If the user quits or is banned from the high level network (514-Y), then the flowchart 500 ends.

FIG. 6 depicts a flowchart 600 of an example of a mettlod for ag;rregated contact list di.splay. In the example of FiG. 6, the flowchart 600 starts at module 602 where a metnber logs into a high level networl..

91004-0013/LE GAL12877050.1 AW, 63017-8005. W00 i In the example of FIG. 6, the flowchart 600 continues to module 604 where a user logs into a low level network through the liigh level network. Depending upon the implenientation and/or user configurations, the user niay be logged into the low level network automatically whcn logging inlo the high luvcl nctwork, explieit(y by the usea-, or thc use r may be logged into the low level network whcn thc user selects a contae.t that is associated with the low level netwurk.

In the example of FIG. 6, the flowchart 600 continues to module 606 where high level and low level contacts are displayed in an aggregated contact list. It may be noted that a user may not have a high level contact list, either because a high level systeni does not allow for contact lists, or because the user does not opt to maintain any contact lists at the high level.

In the example of FIG. 6, tJie tlowchart 600 continues to decision point 608 where it is detenn.ined whether to logout of the low level network. If it is determined to logout of tbe low level network (608-Y), then the flowchart 600 continues to module 610 where the relevant low level contacts are removed from the aggregated display, and the flowchart 600 loops back to module 606, as described previously. The relevaazt low level contacts are those contacts that are in ttie contact list associated with the low level network from which logout was elected. If, on the other hand, it is detertnined not to logout of the low level network (608-N), then the flowchart 600 continues to decision point 612.

In the example of FIG. 6, the flowchart 600 continues to decision point 612 where it is determ.ined whether to login to a low level network. It is possible to login to an implenlentation-specific number of low level networks (or, in the alternative, practically any nunlber of low level networks). If it is determined to login to a low level network (612-Y), then the flowchart 600 loops back to module 604, as ciescribed previously. If, on the other hand, it is determined not to login to a low level network (612-N), then the flowchart 600 continues to decision point 614, where it is detemiined whetlier to logout of the high level network. If not (614-N), the flowchart 600 loops back to niodule 606, as described previously. If so (614-Y), then the flowchart 600 ends.

FIG. 7 depicts a computer system 700 suitable for implementation of the techniques described above with reference to FIGS. 1-6. The computer system 700 includes a computer 702, 110 devices 704, and a display device 706. The computer 702 incl-,ides a processor 708, a conimunications interG;ice 71(), merr-ory 712, display controller 7 t4, non-volatile stora~e ? 10, and I/O controller 718. The computer 702 may be coupled to or include the I/O
devices 704 and display device 706.

9 t 004-0013/LEGAL12877050.1 AMk The computer 702 interfaces to external systems thi-ough the communications interface 7( 0, which may inclucle a rnodem or network interface. The conimunications interface 710 can be considered to be part of the computer systeni 700 or a part ofthe computer 702. Thc cummunications intc:rlacc 710 can be an analog rnodem, ISDN ntoctem, cabic i'viodem, token ring interface, satellite transniission interface (e.g. "ilireet PC"), or other inleri'aces lor coupling a computer system to other computer systenis. Although conventional cotnputers typically include a communications interface of sonie type, it is possible to create a computer that does not inclttde one, thereby making the communicatiotis interface 710 optional in the strictest sense of the word.

The processor 708 may include, by way of exain.ple but tlot limitation, a conventional microprocessor sucli as an Intel Pentium microprocessor or Motorola power PC.:
microprocessor.
Whiie the processot- 708 is a critical coinponent of all conventional computers, any applicable known or conveniertt processor could be used for the purposcs of implementing the techniques described herein. The memory 712 is coupled to the processor 708 by a bus 720.
The memory 712, which mav be referred to as "primary memory," can include Dynamic Random Access Memory (DRAM) and can also include Static RAM (SRAM). The bus 720 couples the processor 708 to the memory 712, and also to the non-volatile storage 716, to the display controller 714, and to the UO controller 718.

The I/O devices 704 can include a keyboard, disk drives, printers, a scaiiner, and other input and output devices, including a mouse or other pointing device. For illustrative purposes, at least one of the UO devices is assumed to be a block-based media device, such as a DVD
player. The display controller 714 may control, in a known or convenient maiiner, a display on the display device 706, which can be, for example, a cathode ray tube (CRT) or liquid crystal display (LCD).

The display controller 714 and I/O controller 718 may include device drivers.
A device driver is a specific type of computer software developed to allow interaction with liardware devices. Typically this constitutes an interface for comniunicating with the device, through a bus or communications subsystem that the hardwarc is connected to, providing commands to and/or receiving data fi-om the dcvice, anci on the otlier end, the requisite interfaces to the OS and software applications.

I'he device driver mav include a hardware-depcndent coinputei- pro~~ram that is also OS-specific. The computer program etiables another program, typically an OS or applications software package or computer program running under the OS kernel, to interact transparently with a hardware device, and usually provides the requisite interrupt liandling necessary for any necessary asynchronous time-dependent hardware interfacing needs.

Or,-63617-8005. WOD 1 Thc non-volatile storage 716, wltich may be t'el'crrcci to as "secondary memory," is otten a magnetic hard disk, an optical disk, or anothcr form of storage for large atnounts of data. Sorne of this data is offten written, by a direct memory access process, into memory 712 during execution of so[lware in the comintter 702. The non-volatile storage 716 tilay include a block-based niedia device. The terms "machine-readable mediurn" or "computer-readable medium"
include any lcnown or convenient storage device that is accessible by the processor 608 and also encompasses a carrier wave that cncodes a data signal.

The cotnputer system 700 is one example of many possible computer systems which have different architectures. For example, personal computers based on an Intel microprocessor olten have multiple buses, one of which can be an I/O bus for the peripherals and one that direclly connects the processor 708 and the memory 712 (often referred to as a memory bus).
The buses are connected together through bridge components tiiat perfotm any necessary translation due to diffcring bus protocols.

Network computers are anotl--er type of computer system that can be used in catijunction with the teachings provided herein. Network coniputers do not usually include a liard disk or other mass storage, and the executable prog.ranis are loaded from a network connection into the memory 712 for execution by the processor 708. A Web TV
system, which is known in the art, is also considered to be a computer systeni, but it may lack some of the features shown in FIG. 6, such as certain input or output devices. A typical coniputer system will usually include at least a processor, memory, and a bus coupling the meni.ory to the processor.

The cotnputer system 700 may be controlled by an operating systein (OS). An OS
is a software program-used on most, but not all, conlputer systems - that manages the hardware and software resottrces of a computer. Typically, the OS performs basic tasks such as controlling and allocating memory, prioritizing system requests, controlling input and output cievices, facilitating networking, and managing files. F?xamples of operating systems for personal computers include Microsoft Windows(Di,, Linux, and Mac OS- R.
Delincating between the OS and application software is sometimes rather difficult. Fortunately, delineation is not neccssary to understand the techaiques described herein, since anv reasonable delineation should su ffice.

The lowest level of an OS may be its kernel. The kern4l is typically the first layer of software loaded into meinory when a systeni boots or starts up. The kernel provides access to various common core services to otlier system and application programs.

9 t 004-0013ILEGAL12877050.1 63017-8005 WOOf As used herein, algorithmic descriptions and symbolic representations of operations cm data bits within a coniputer meniory are believed to most effectively convey the techniques to others skilled in the art. An algorithm is here. and generally, conceived to be a self-eonsistent sequence of operations leading to a desired result. 'hhe operations are those requiring physical manipulations of physical quantities. Usually, tltou,h not necessarily, these quantities take the form of electrical or magnetic signals capablc ol'bcira- stored, transferred, conibined, compared, anii otherwise manipulated. It ltas proven convenicnt at t'imes, principally for reasons of common usage, to rcfer to these signals as bits, values, elements, symbols, characters, terms, nwnbers, or the like.

It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as "processing"
or "computing" or "calculatin;" or "determining" or "displaying" or the like, refer to the action and processes of a computer that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such infomiation storage, transmission or display devices.

An apparatus for performing techniques describeci herein may be specially constructed for the required purposes, or it may coniprise a general ptrrpose computer selectively activated or reconfigured by a conlputer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, by way of example but not limitation, read-only memories (ROMs), RAMs, EPROMs, EEPROMs, magtietic or optical cards, any type of disk including floppy disks, optical disks, CD-ROMs, DVDs, and magnetic-optical disks, or any known or convenient type of media suitable for storinD electronic instructlons.

The algorithms and displays presented herein are not inherently related to any particular computer architecture. The tecliniques may be implemented using any known or convenient progr-anlming laaiguage, whether high level (e.g., C/C++) or low level (e.g., assembly language), and whether interpreted (e.g., .Pcrl), compiled (e.g., C/C++), or Just-rn-Time (JIT) compiled froni hytecode (e.g., .lava). Any known or convenient contputer, regardless of architecttire, should be capable ofexecuting machine cocle compiled or otherwise assembled ti-onl an-y language into rrrachine code that is conlpatible with the computer's architc;cturC.

As i.rSed herein, the term "embodinient" nieans an cmbodin-rent that serves to illustrate by wav of example but not limitation.
91004 -0013/L ECoAL 12877050.1 It will be appreciauc.tl to tliosc,l.illed irL the art that the preceding examples and crubodinlents are exemplary and not liniiling to the scope ot'the present invention. tt is inteilded that all permutations, enlianeemerits, equivalents, and itnprovements thereto that are apparent to those skilled in the art upon a reading of the specification and a study of the drawings are includecl within the true spirit and scope of the present invetltion. It is tllerefot-e intended that the folluwing appended claims include all such modifications, permutations and equivalents as fall within the true spirit and scope of thc present invention.

91 004-001 31LEGAL 12877050.1

Claims

1. A system comprising:
a network interface;
a network login engine coupled to the network interface;
a network contacts database embodied in one or more computer-readable mediums;

a web server coupled to the network contacts database;
a contact aggregation engine coupled to the network login engine and the network contacts database;
wherein, in operation, the contact aggregation engine controls the network login engine to login or facilitate login to one or more networks, updates in the networks contacts database contact information associated with the one or more networks, stores the aggregated contact list in a computer-readable medium at the web server, and provides an aggregated contact list including the contact information to a display device.

2. The system of claim 1 further comprising a high level contacts database embodied in a computer readable medium, wherein, in operation, contacts from the high level contacts database are included in the aggregated contact list.

3. The system of claim 1, wherein the network login engine includes a plurality of network login engines that include sufficient information to login or facilitate login to a respective plurality of low level networks.

4. The system of claim 1, further comprising a user profile database, embodied in a computer-readable medium and coupled to the network login engine, wherein, in operation, the user profile database includes a user-specific information that the network login engine uses to login or facilitate login to the one or more networks.

5. The system of claim 1, further comprising the display device.

6. The system of claim 1, further comprising the one or more networks.

7. A method comprising:
joining a high level network;
joining one or more low level networks;
maintaining a contact list associated with the one or more low level networks;

logging into the high level network;

displaying contacts from the one or more low level networks in an aggregated contact list.

8. The method of claim 7, further comprising logging into the one or more low level networks.

9. The method of claim 7, further comprising:
maintaining a contact list associated with the high level network;
displaying contacts from the high level network in the aggregated contact list.

10. The method of claim 7, further comprising joining an additional low level network, wherein the aggregated contact list does not include contacts of the additional low level network.

11. The method of claim 7, further comprising:
logging into the one or more low level networks and an additional low level network;
displaying contacts from the one or more low level networks and the additional low level network in the aggregated contact list;
logging out of the additional low level network.

12. The method of claim 7, further comprising logging out of the high level network.

13. A method comprising:
logging into a high level network;
logging into a low level network;
displaying an aggregated contact list that includes contacts associated with the low level network through the high level network.

11. The method of claim 13, further comprising automatically logging into the low level network in response to logging into the high level network.

15. The method of claim 13, further comprising facilitating an explicit login to the low level network.

16. The method of claim 13, wherein the logging into the low level network is in response to a user selecting a contact for display in the aggregated contact list that is associated with the low level network.

17. The method of claim 13, wherein the low level network is a first low level network, further comprising:

91004-00131LEGAL12877050.1 logging into a second low level network through the high level network;
displaying the aggregated contact list, including contacts associated with the second low level network.

18. The method of claim 17, further comprising:
logging out of the second low level network;
removing low level contacts associated with the second low level network from the aggregated contact list.

19. The method of claim 17, further comprising:
logging out of the first low level network;
removing low level contacts associated with the first low level network from the aggregated contact list.

20. The method of claim 13, further comprising displaying the aggregated contact list including contacts associated with the high level network.