CA2649964A1 - Method for sensing user presence for buddy list applications - Google Patents

Method for sensing user presence for buddy list applications Download PDF

Info

Publication number
CA2649964A1
CA2649964A1 CA002649964A CA2649964A CA2649964A1 CA 2649964 A1 CA2649964 A1 CA 2649964A1 CA 002649964 A CA002649964 A CA 002649964A CA 2649964 A CA2649964 A CA 2649964A CA 2649964 A1 CA2649964 A1 CA 2649964A1
Authority
CA
Canada
Prior art keywords
buddy list
user
buddy
user presence
list client
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
CA002649964A
Other languages
French (fr)
Inventor
Alicia Abella
Brian Amento
Lawrence Stead
Benjamin J. Stern
Ganesh K. Subramaniam
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
AT&T Corp
Original Assignee
At&T Corp.
Alicia Abella
Brian Amento
Lawrence Stead
Benjamin J. Stern
Ganesh K. Subramaniam
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by At&T Corp., Alicia Abella, Brian Amento, Lawrence Stead, Benjamin J. Stern, Ganesh K. Subramaniam filed Critical At&T Corp.
Publication of CA2649964A1 publication Critical patent/CA2649964A1/en
Abandoned legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/16—Analogue secrecy systems; Analogue subscription systems
    • H04N7/173—Analogue secrecy systems; Analogue subscription systems with two-way working, e.g. subscriber sending a programme selection signal
    • H04N7/17309—Transmission or handling of upstream communications
    • H04N7/17318—Direct or substantially direct transmission and handling of requests
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/442—Monitoring of processes or resources, e.g. detecting the failure of a recording device, monitoring the downstream bandwidth, the number of times a movie has been viewed, the storage space available from the internal hard disk
    • H04N21/44213—Monitoring of end-user related data
    • H04N21/44218—Detecting physical presence or behaviour of the user, e.g. using sensors to detect if the user is leaving the room or changes his face expression during a TV program
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/442—Monitoring of processes or resources, e.g. detecting the failure of a recording device, monitoring the downstream bandwidth, the number of times a movie has been viewed, the storage space available from the internal hard disk
    • H04N21/44213—Monitoring of end-user related data
    • H04N21/44222—Analytics of user selections, e.g. selection of programs or purchase activity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47—End-user applications
    • H04N21/478—Supplemental services, e.g. displaying phone caller identification, shopping application
    • H04N21/4788—Supplemental services, e.g. displaying phone caller identification, shopping application communicating with other users, e.g. chatting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47—End-user applications
    • H04N21/488—Data services, e.g. news ticker
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/643—Communication protocols
    • H04N21/64322—IP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/65—Transmission of management data between client and server
    • H04N21/654—Transmission by server directed to the client
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/65—Transmission of management data between client and server
    • H04N21/658—Transmission by the client directed to the server
    • H04N21/6582—Data stored in the client, e.g. viewing habits, hardware capabilities, credit card number
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users

Abstract

A method and system for sensing and reporting various types of user presence using "buddy list" applications. A buddy list client senses various types of user presence of a user and sends status information corresponding to the sensed user presence to a server. The buddy list client also receives status information from the server corresponding to various types of user presence information of buddies, and displays a buddy list indicating the various types of user presence information of the buddies. This can be implemented on an IPTV client in order to sense and display presence information relating to a user watching television.

Description

Method for Sensing User Presence for Buddy List Applications BACKGROUND OF THE INVENTION

[0001] The present invention is generally directed to sensing and reporting user presence using "buddy list" applications. More specifically, the present invention is directed to sensing and reporting various types of user presence at a user device using buddy lists to enhance various entertainment services.
[0002] Conventional buddy list applications, as used in instant messaging applications, display a list of "buddies" of an instant messaging user. The buddies are other instant messaging users that the instant messaging user has selected.
Conventional buddy list applications also display an indicator for each buddy to indicate the presence of that buddy. In conventionaf buddy list application, presence of a buddy indicates that the buddy is logged in to the instant messaging application that the user is also logged into. When a buddy list indicates presence of a buddy of a user (i.e., that the buddy is logged in), the user can act on the presence to start an instant messaging session with the present buddy.
[0003] Although-the conventional notion of user presence and the action associated with user presence allow buddy lists to be useful for instant messaging applications, this fails to take advantage of emerging entertainment and business technologies and services, such as Internet Protocol Television (IPTV), digital cable television, Voice over lntemet Protocol (VoIP), network enable digital music players, etc. For example, IPTV is a service in which television programming is delivered to consumers via a data network (e.g., the Internet) using Intemet Protocol. More particularly, in IPTV, television programming is delivered as video content, which is divided into data packets and streamed to consumers over the Internet. The data packets are received by an IPTV client, such as a set top box, which is connected to a consumer's television. Typically, IPTV clients connect to the Internet over a broadband connection.
[0004] IPTV provides greater control and flexibility to consumers than traditional TV distribution technologies. For example, because television programming is delivered point-to-point from a provider to a consumer, a consumer may individually control (i.e., pause, rewind, etc.) programming being delivered.
Also, because television programming is being delivered over the Internet, a consumer may receive IPTV programming from around the world. Additionally, IPTV can be provided with other Internet services, such as Voice over IP
(VOIP) services. An IPTV receiver can also be used in conjunction with or function as a digital video receiver (DVR) to record and store IPTV programming.

BREIF SUMMARY OF THE INVENTION
[0005] The present invention provides a method and system for sensing various types of user presence at various user devices and reporting various types of user presence using buddy lists in order to enhance various entertainment and business services and technologies. This can be achieved by sensing various types of user presence at a buddy list client device, transmitting status information corresponding to the sensed user presence to a server, and receiving status information from the server corresponding to various types of user presence sensed at other buddy list client devices, and displaying a buddy list indicating the user presence at the other buddy list client devices.
[0006] According to various embodiments of the present invention, the buddy list shows status information corresponding to various types of user presence of buddies, such as television presence, telephone presence, physical presence, and presence of shared content on a buddy list client. In response to the buddy list indicating some form of user presence.for a buddy, a user can initiate various actions, such watching the same channel or program as a buddy, initiating a Voice over Intemet Protocol (VoIP) telephone call to a buddy, initiate an email to a buddy, initiating an instant messaging session with a buddy, or viewing playing play a buddy's shared content.
[0007] IPTV is an example of a service that can be used to implement an embodiment of the present invention. Because 1PTV delivers television programming over the Internet, there are many possible ways to utilize the Internet to enhance consumers' viewing experience. Collaborative viewing, in which consumer's in different locations experience IPTV viewing fogether, is one way to enhance the IPTV viewing experience. Accordingly, it is desirable to provide a way for users to easily interact with each other while viewing IPTV. The present invention allows users of Internet Protocol Television (IPTV) to easily interact with each other while viewing IPTV. This is accomplished by displaying a buddy list for each user of an IPTV client. The buddy list shows buddies of a user and user presence information for each buddy. A user can use the buddy list to interact with the buddies by selecting icons relating to various types of user presence.
[0008] In one embodiment of the present invention, an IPTV client senses user presence of a user and transmits status information corresponding to the sensed user presence to a server. The server determines which users of other IPTV clients list the user as a buddy, and sends the status information to the other IPTV clients. When an IPTV client receives status information from the server, the IPTC client displays a buddy list indicating the user presence of the buddies.
[0009] These and other advantages of the invention will be apparent to those of ordinary skill in the art by reference to the following detailed description and the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS
[0010] FIG. 1 illustrates an Intemet Protocol Television (IPTV) system configured to implement an embodiment of the present invention;
[0011] FIG. 2 illustrates a high level block diagram of a computer capable of implementing the present invention;
[0012] FIG. 3 illustrates an exemplary buddy list displayed by an IPTV
client;
[0013] FIG. 4 illustrates a method of controlling an IPTV client according to an embodiment of the present invention;
[0014] FIG. 5 illustrates an exemplary method of sensing various types of presence information according to an embodiment of the present invention; and [0015] FIG. 6 illustrates an exemplary method of using a buddy list to trigger a variety of actions according to an embodiment of the present invention.
DETAILED DESCRIPTION
[0016] The present invention is directed to sensing and reporting various types of user presence at a buddy list client device. A buddy list client device refers to any type of device capable of displaying a buddy list or any device for which some type of user presence can be sensed and displayed in a buddy list on another device. User presence refers to any way in which a user of a buddy list client device is directly or indirectly interacting with the buddy list client device.
Examples of various types of user presence are described in greater detail below Examples of buddy list client devices can include, but are not limited to, lntemet Protocol Televisioh (IPTV) clients, digital cable receivers, personal computers (PCs), personal digital assistants (PDAs), digital video recorders (DVRs), digital music players, etc. FIG. 1 illustrates an Intemet Protocol Television (IPTV) system 100 configured to implement an embodiment of the present invention. However, the present invention is not limited to being implemented as illustrated in FIG. 1, but may be implemented using any buddy list client device or combination of buddy list client devices.
[0017] As illustrated in FIG. 1, the IPTV system 100 includes a plurality of IPTV clients 110, 120. 130, 140, 150, and 160 which communicate with a server 170 via the Intemet. The IPTV clients 110, 120, 130, 140, 150, and 160 can be embodied as set top boxes, which respectively connect to televisions (TV) 114, 124, 134, 144, 154, and 164. The IPTV clients 110, 120, 130, 140, 150, and 160 receive television programming from an IPTV service provider via the Internet.
The television programming is transmitted to the IPTV clients 110, 120, 130, 140, 150, and 160 over the Internet in the form of data packets using Intemet Protocol (IP).
The IPTV clients 110, 120, 130, 140, 150, and 160 receive the data packets, convert the data packets to video signals, and transmit the video signals to the respective TVs 114, 124, 134, 144, 154, and 164 in order for the television programming to be viewed by users. Although FIG. 1 depicts TVs 114, 124, 134, 144, 154, and 164 being used to display the television programming, any display device capable of displaying the video signals transmitted from an IPTV client may also be used. Furthermore, Although FIG. 1 illustrates IPTV clients 110, 120, 130, 140, 150, and 160 respectively connected to separate TVs 114, 124, 134, 144, 154, and 164, the present invention is not limited thereto. For example, an IPTV
client and a display may be provided in the same device.
[0018] The IPTV clients 110, 120, 130, 140, 150, and 160 respectively include buddy list functions 112, 122, 132, 142, 152, and 162, which display buddy lists on the respective TVs 114, 124, 134, 144, 154, and 164. A user of an fPTV
client 110, 120, 130, 140, 150, and 160 can have a corresponding buddy list which is displayed on the user's TV 114, 124, 134, 'l44, 154, and 164. The buddy list for a particular user displays a list of buddies (i.e., users of other IPTV
clients) selected by the user, and shows status information for each buddy. The status information..
for=a buddy can reflect user presence of the buddy on an IPTV client. The buddy lists of the users of each IPTV client 110, 120, 130, 140, 150, and 160 are stored in a database 172 on the server 170.
[0019] The IPTV clients 110, 120, 130, 140, 150, or 160 sense user presence and send status information to the server 170 corresponding to the sensed user presence. User presence, as described above, refers to any direct or indirect interaction between a user and an IPTV client (or any other buddy list client). Examples of various types of user presence are described in greater detail below. The server 172 sends the status information to the IPTV clients 110, 120, 130, 140, 150, and 160 to be displayed on the buddy lists to reflect the user activity of the buddies in the buddy lists displayed by the IPTV clients 110, 120, 130, 140, 150, and 160. For example, if there is a change in the user presence on IPTV
client 110, IPTV client 110 sends status information indicating the change in user presence to the server 170. The server 170 then checks the database 172 to determine which users of the other IPTV clients 120, 130, 140, 150, and 160 list the user of IPTV client 110 as a buddy. If the users of IPTV clients 120 and 130 list the user of IPTV client 110 as a buddy, the server sends the status information to IPTV clients 120 and 130, and IPTV clients 120 and 130 update the buddy lists displayed on TVs 124 and 134, respectively, to display the status information in order to reflect the change in user presence on IPTV client 110.
[0020] A buddy list client, such as the IPTV clients of FIG. 1, having the buddy list functionality described herein may be implemented on a computer using well known computer processors, memory units, storage devices, computer software, and other components. A high level block diagram of such a computer is illustrated in FIG. 2. Computer 202 contains a processor 204 which controls the overall operation of the computer 202 by executing computer program instructions which define such operation. The computer program instructions may be stored in a storage device 212 (e.g., magnetic disk) and loaded into memory 210 when execution of the computer program instructions is desired. Thus, the buddy list function can be defined by the computer program instructions stored in the memory 210 and/or storage 212 and the buddy list function will be controlled by the processor 204 executing the computer program instructions. The computer 202 also includes one or more network interfaces 206 for communicating with other devices via a network. The computer 202 also includes input/output 208 which represents devices which allow for user interaction with the computer 202 (e.g., display, keyboard, mouse, speakers, buttons, etc.) The computer 202 may be provided in the form of a set-top box added functionality of the elements of FIG. 2.
In the case of the buddy list client being an IPTV client, a digital cable receiver or the like, a user may interact with the computer 202 using a remote control.
One skilled in the art will recognize that an implementation of an actual computer will contain other components as well, and that FIG. 2 is a high level representation of some of the components of such a computer for illustrative purposes.
[0021] - In addition to an IPTV client, other types of buddy list client devices (i.e., computer devices) may be used to perform various functions, such as Voice over Intemet Protocol (VoIP) telephone calling, email, storing audio and video files, and a calendar function. It is also possible that one buddy list client device, such as an IPTV client or a PC, be able to perform multiple functions. Accordingly, the buddy list can display status information that reflects a variety of types of user presence associated with different functions being performed by buddy list client devices associated with buddies. These types of presence can include, but are not limited to, whether a buddy is watching TV, what channel a buddy is watching, what program a buddy is watching, whether a buddy is currently on a VoIP
telephone call, whether new audio or video content is stored on a buddy's device (i.e., computer, IPTV set top box, or other network device), and whether a new appointment is stored in a buddy's calendar. Additionally, a computer, IPTV
client, wireless router, or other network-enabled computing device can be equipped to detect whether a registered wireless device of a user is within a limited range in order to detect physical presence of the user. A registered wireless device refers to any device that has wireless connectivity with a limited range, such as RFID, Bluetooth, WiFi, etc. Accordingly, in order to detect a registered wireless device, wireless functionality (e.g., antenna, radio, etc.) can be added to the buddy list client. When the buddy list client detects the registered wireless device of a user within its range, status information indicating physical presence of the user at the buddy list client can be displayed on buddy lists where the user is a buddy.
[0022] FIG. 3 illustrates an exemplary buddy list 320 being displayed on a display 310 (e.g., television) by an IPTV client 300. As illustrated in FIG.
3, the buddy list includes a list of user names (buddyl, buddy2, buddy3, and buddy4) and status information for each user name. The status information is displayed using icons representing different types of user presence. For example, a television presence icon 321 indicates that a buddy's TV is currently on, a telephone presence icon 322 indicates that a buddy is currently on a VoiP telephone call, an audio file presence icon 323 indicates that a buddy has stored a new audio file, an appointment presence icon 324 indicates that a new appointment has been added to a'buddy's calendar, and a physical presence icon 325 indicates the physical presence of a buddy at an IPTV client. A user can use an input device, such as a remote control, to select a username or an icon. When a username or an icon is selected, the IPTV client 300 can automatically perform a predetermined action or can display a menu of options to allow a user to select an action. For example, if a user selects the television icon of buddyl, the IPTV client 300 can -automatically set the channel of the display 310 to the channel that buddyl is watching.
[0023] As illustrated in FIG. 3, the buddy list 320 is displayed in a window on a screen of the TV 310, but the present invention is not limited thereto. A
buddy list may be displayed in a variety of other ways on a TV including on a scroll bar across the bottom of the screen or on a separate channel dedicated to the buddy list. It is also possible that a buddy list be displayed on another device, such as a desktop or laptop computer, a PDA, etc.
[0024] FIG. 4 illustrates a method of controlling a buddy list client according to an embodiment of the present invention. Referring to FIG. 4, at step 400, the buddy list client runs a buddy list application. The buddy list application can start automatically when the TV is turned on or can be started when a user of the buddy list client logs on to the buddy list application using a usemame and password. Furthermore, in the case of an IPTV client, the buddy list application can associate a single user and buddy list with an IPTV client or be configured to have separate buddy lists corresponding to plural users using the same IPTV
client. When the buddy list application is started at step 400, the buddy list client proceeds to steps 410 and 430. As illustrated in FIG. 4, the buddy list client simultaneously performs steps 410 and 420 and steps 430 and 440.
[0025] At step 410, the buddy list client senses user presence. As described above, the buddy list client can sense different types of user presence.
At step 420, the buddy list client transmits status information corresponding to the sensed user presence to a server via a data network, such as the lntemet. The buddy list client continuously loops through steps 410 and 420 while the buddy list application is running, such that whenever there is a change to the user presence, the buddy list client senses the change in user presence (step 410) and transmits updated status information corresponding to the change in user presence to the server (step 420).
[0026] FIG. 5 illustrates an example of sensing the user presence (step 410) and transmitting the status information to the server (step 420) for a.variety of types of user presence. It is to be understood that FIG. 5 is purely exemplary, and the present invention is not limited to sensing the types of user presence described therein.
[0027] Referring to FIG. 5, at step 510, the buddy list client senses whether a TV associated with the buddy list client is turned on or off, that is sensing a change in state of the television. If the TV is switched on or off at step 510, the method proceeds to step 515. If the TV is not switched on or off at step 510, the method proceeds to step 520. If the buddy list client detects that the TV is turned on, the buddy list client can also sense what channel and/or what program the TV
is on. The buddy list client can also sense any change in the channel and/or the program of the TV.
[0028] At step 515, the buddy list client sends a TV presence signal to the server. If it is sensed that the TV is tumed on at step 510, the buddy list client sends a TV presence start signal to the server to indicate that the TV is on.
If it is sensed. that the TV is tumed off at step 510, the buddy list client sends a TV
presence end signal to the server to indicate that the TV is off, thereby indicating that this client is no longer "present". When the buddy list client sends the TV
presence start signal, the buddy list client can also send a channel and/or a program signal to the server to indicate what channel/program the TV is on.
The buddy list client can also send the channel and/or the program signal whenever a change in the channel and/or the program is sensed.
[0029] At step 520, the buddy list client senses whether a telephone call is started or ended. For example, the buddy list client can sense whether a user begins or ends a VolP telephone call. If the buddy list client senses that a user begins or ends a telephone call at step 520, the method proceeds to step 525.
* If the buddy list client does not sense that a user begins or ends a telephone call at step 520, the method proceeds to step 530.
[0030] At step 525, the buddy list client sends a telephone presence signal to the server. When it is sensed that the user begins a telephone call at step 520, the buddy list client sends a telephone presence start signal to the server to indicate that the user is on the telephone. When it is sensed that the user ends a telephone call at step 520, the buddy list client sends a telephone presence end signal to the server to indicate that the user is no longer on the telephone.
[0031] At step 530, the buddy list client senses whether a registered wireless device enters or leaves a range of the IPTV client. As described above, a registered wireless device can refer to any device that has wireless connectivity with a limited range, such as RFID, Bluetooth, WiFi, etc. If the buddy list client senses that a registered wireless device enters or leaves the range of the IPTV
client at step 530, the method proceeds to step 535. If the buddy list client does not sense that a registered wireless device enters or leaves the range of the buddy list client at step 530, the method proceeds to step 540.
[0032] At step 535, the buddy list client sends a physical presence signal to the server. When it is sensed that the a registered wireless device of a user enters the range of the buddy list client at step 530, the buddy list client sends a physical presence start signal to the server to indicate that the a user is physically present within the range of the IPTV client. When it is sensed that the a registered wireless device of a user leaves the range of the buddy list client at step 530, the buddy list client sends a physical presence end signal to the server to indicate that the user is no longer physically present within the range of the IPTV client.
[0033] At step 540, the buddy list client senses whether a new audio file is downloaded. The buddy list client can sense when an audio file is downloaded onto the buddy list client or downloaded onto an extemal device, such as an internet enabled mp3 player, which communicates with the buddy list client. If the buddy list client senses that a new audio file is downloaded at step 540, the method proceeds to step 545. If the buddy list client does not sense that a new audio file is downloaded at step 540, the method proceeds to step 550. At step 545, the buddy list client sends an audio file presence start signal to the server to indicate that a new audio file has been downloaded.
[0034] At step 550, the buddy list client senses whether a new video file is downloaded. The buddy list client can sense when video file is downloaded onto the buddy list client or downloaded onto an extemal device, such as an extemal DVR, which communicates with the buddy list client. If the buddy list client senses that a new video file is downloaded at step 550, the method proceeds to step 555.
If the buddy list client does not sense that a new video file is downloaded at step 550, the method proceeds to step 560. At step 555, the buddy list client sends a video file presence start signal to the server to indicate that a new video file has been downloaded.-=
[0035] At step 560, the buddy list client senses whether a new appointment is added to a user's calendar application. The appointment can be added to a calendar application running on the buddy list client or on an external device, such as a PC or PDA, which communicates with the buddy list client. If the buddy list client senses that a new appointment is added to the calendar application at step 560, the method proceeds to step 565. If the buddy list client does not sense that a new appointment is added to the calendar application at step 560, the method returns to step 510. At step 565, the buddy list client sends an appointment presence start signal to the server to indicate that a new appointment has been added to the user's calendar. The method then returns to step 510, and continuously loops through steps 510 - 565 while the buddy list application is running.
[0036] Returning to FIG. 4, when the buddy list application is started at step 400, the buddy list client proceeds to steps 410 and 430. As illustrated in FIG.
4, the buddy list client simultaneously performs steps 410 and 420 and steps and 440. At step 430, the buddy list client receives status information from the server corresponding to user presence of buddies in a user's buddy list. The status information received from the server can correspond to a variety of different presence types for a plurality of buddies. At step 440, the buddy list client displays the users buddy list, which shows the status information for each buddy that is present in some form. For example, an IPTV client can display the buddy list in a variety of different ways on a TV associated with the IPTV client, such as a window on the TV screen, a scrolling ticker at the bottom of the TV screen, and as a dedicated iPTV channel. In the case of other computer devices being used as the buddy list client, the buddy list can be displayed in a window or part of a window of the buddy list application. In this case, the buddy list can be implemented together with a traditional Instant Messaging buddy list, or provided as a separate application.
[0037] The status information for each buddy may be displayed on the buddy list with a visual representation of the types of presence active for each buddy. This r-iay include different icons, different text colors, or another scheme to represent each type of user presence. The buddy list client continuously loops through steps 430 and 440 while the buddy list application is running, such that whenever updated status information is received for any buddies of the user of the buddy list client (step 430), the buddy list client displays an updated buddy list showing the updated status information (step 440).
[0038] When a buddy list is displayed at a display associated with a buddy list client, the user may use the buddy list to interact with buddies based on the status information displayed in the buddy list. For example, the user may select a buddy's icons to trigger actions including, but not limited to, automatically switching the channel to the same channel (or program) that a buddy is watching, launching a VolP telephone call, an email, or an instant messaging session with a buddy, initiating a conference call among more than one buddy, playing an audio or video file shared by a buddy, or viewing appointments on a buddy's calendar.
[0039] FIG. 6 illustrates an example of using a buddy list to trigger a variety of actions. Referring to FIG. 6, at step 600, a buddy list client runs a buddy list application. At step 610, the buddy list client determines whether new status information is received from the server. If new status information is received from the server at step 610, the method proceeds to step 615. If no new status information is received from the server at step 610, the method proceeds to step 620. At step 615, the buddy list client updates the buddy list by displaying (or removing) appropriate icons corresponding to the new status information received from the server.
[0040] At-step 620, the buddy list client detects whether a user selects a TV presence icon of a buddy in the buddy list. If a TV presence icon is selected at step 620, the method proceeds to step 625. If no TV presence icon is selected at step 620, the method proceeds to step 630. At step 625, a buddy list client, such as an IPTV client or a digital cable receiver, automatically switches the user's TV to the same channel as the TV of the buddy whose TV presence icon is selected at step 620. Alternatively, the buddy list client can automatically switch the user's TV
to the same program that the buddy is watching.
[0041] ' At*step 630, the buddy list client detects whether the user selects a telephone presence icon of a buddy. If a telephone presence icon is selected at step 630, the method proceeds to step 635. If no telephone presence icon is selected at step 630, the method proceeds to step 640. At step 635, the buddy list client displays menu options corresponding to the telephone presence icon.
These menu options can include initiating a VolP call to the buddy when the buddy gets off the phone, initiating an instant messaging session with the buddy, sending an email to the buddy, etc. When the user selects a menu option, the buddy list client performs the action corresponding to the selected menu option, or controls an external device communicating with the buddy list client to perform the action.
[0042] At step 640, the buddy list client detects whether the user selects a physical presence icon of a buddy. If a physical presence icon is selected at step 640, the method proceeds to step 645. If no physical presence icon is selected at step 640, the method proceeds to step 650. At step 645, the buddy list client displays menu options corresponding to the physical presence icon. These menu options can include initiating a VolP call to the buddy, initiating an instant messaging session with the buddy, sending an email to the buddy, etc. When the user selects a menu option, the buddy list client performs the action corresponding to the selected menu option, or controls an extemal device communicating with the buddy list client to perform the action.
[0043] At step 650, the buddy list client detects whether the user selects an audio file presence icon of a buddy. If an audio file presence icon is selected at step 650, the method proceeds to step 655. If no audio file presence icon is selected at step 650, the method proceeds to step 660. At step 655, the buddy list client displays menu options corresponding to the audio file presence icon.
These menu options can include downloading the same audio file, playing the audio file, initiating a VoIP call to the buddy, initiating an instant messaging session with the buddy, sending an email to the buddy, etc. When the user selects a menu option, the buddy list client performs the action corresponding to the selected menu option, or controls an external device communicating with the buddy list client to perform the action.
[0044] At step 660, the buddy list client detects whether the user selects a video file presence icon of a buddy. If a video file presence icon is selected at step 660, the method proceeds to step 665. If no video file presence icon is selected at step 660, the method proceeds to step 670. At step 665, the buddy list client displays menu options corresponding to the video file presence icon. These menu options can include downloading the same video file, playing the video file, initiating a VoIP call to the buddy, initiating an instant messaging session with the buddy, sending an email to the buddy, etc. When the user selects a menu option, the buddy list client performs the action corresponding to the selected menu option, or.controls an extemal device communicating with the buddy list client to perform the !action.
[0045] At step 670, the buddy list client detects whether the user selects an appointment presence icon of a buddy. If an appointment presence icon is selected at step 670, the method proceeds to step 675. If no appointment presence icon is selected at step 670, the method proceeds to step 680. At step 675, the buddy list client displays menu options corresponding to the appointment presence icon. These menu options can include viewing the buddy's calendar, adding the appointment to the user's calendar, initiating a VolP call to the buddy, initiating an instant messaging session with the buddy, sending an email to the buddy, etc. When the user selects a menu option, the buddy list client performs the action corresponding to the selected menu option, or controls an extemal device communicating with the buddy list client to perform the action.
[0046] At step 680, the buddy list client performs a loop over the content related presence signals (i.e., the audio file presence signal, the video file presence signal, and the appointment presence signal) received from the server. That is, the buddy list client only displays icons corresponding to these presence signals on the buddy list for a limited amount of time so that icons are only displayed for new content. Accordingly, at step 685, the buddy list client determines whether the age of a content related presence signal (i.e., how long it has been' since the signal was received from the server) is greater than a threshold. If the age of the content related signal is greater than the threshold at step 685, the method proceeds to step 690. At step 690, the buddy list client cancels the presence of the content and updates the buddy list to remove the corresponding icon. While the buddy list application is running the buddy list client continuously loops through steps 690.
[0047] Although the method of FIG. 6, describes displaying icons related to content (i.e., audio file, video file, and appointment) presence for a limited amount of time, the present invention is not limited thereto. For example, the content presence icons can be displayed until selected by a user, and then cleared.
It is also possible that the content presence icons only be displayed when displaying other presence icons.
[0048] As described above, the present invention allows a user to view status information indicating various types of user presence of buddies listed. on the users buddy list. In an embodiment of the present invention, a user can select what information is available to those who list the user on their buddy lists, in order to protect the user's privacy.
[0049] The foregoing Detailed Description is to be understood as being in every respect illustrative and exemplary, but not restrictive, and the scope of the invention disclosed herein is not to be determined from the Detailed Description, but rather from the claims as interpreted according to the full breadth permitted by the patent laws. It is to be understood that the embodiments shown and described herein are only illustrative of the principles of the present invention and that various modifications may be implemented by those skilled in the art without departing from the scope and spirit of the invention. Those skilled in the art could implement various other feature combinations without departing from the scope and spirit of the invention.

Claims (29)

1. A method comprising:
sensing a plurality of types of user presence at a buddy list client device;
transmitting status information corresponding to each of the sensed plurality of types of user presence to a server;
receiving status information from the server corresponding to a plurality of types of user presence sensed at at least one other buddy list client device;
and displaying a buddy list indicating the user presence at the at least one other buddy list client device.
2. The method of claim 1, wherein said buddy list client device comprises at least one of an Internet Protocol Television (IPTV) client, a digital cable receiver, a computer, a personal digital assistant, a digital music player, and a digital video recorder.
3. The method of claim 1, wherein said plurality of types of user presence comprises:
an on/off state of a television associated with a buddy list client device.
4. The method of claim 3, wherein said plurality of types of user presence further comprises at least one of:
a channel that the television associated with the buddy list client is tuned to; and a program that the television associated with the buddy list client is tuned to.
5. The method of claim 1, wherein said sensing step comprises:
sensing whether a user is logged into said buddy list client.
6. The method of claim 1, wherein said sensing step comprises:

sensing whether a Voice over Internet Protocol (VoIP) call is in progress.
7. The method of claim 1, wherein said sensing step comprises:
sensing whether a registered wireless device of a user exists within a predetermined range of the buddy list client.
8. The method of claim 1, wherein said sensing step comprises:
sensing newly stored content.
9. The method of claim 8, wherein said newly stored content comprises at least one of:
a newly stored audio file;
a newly stored video file; and a newly added appointment in a calendar application.
10. The method of claim 1, wherein said displaying step comprises:
displaying said buddy list using one of a window on a television screen, a scrolling ticker on a television screen, a dedicated IPTV channel, a computer screen, and a display of a handheld device.
11. The method of claim 1, wherein said displaying step comprises:
displaying visual indications representing said plurality of types of user presence.
12. The method of claim 11, wherein said visual indications comprise at least one of icons corresponding to said plurality of types of user presence and different colors of text corresponding to said plurality of types of user presence.
13. The method of claim 11, further comprising:
performing an action in response to a user selection of a displayed visual indication.
14. The method of claim 13, wherein said action comprises:
setting a television associated with said buddy list client device to a channel that a television associated with said at least one other buddy list client device is tuned to.
15. The method of claim 13, wherein said action comprises:
initiating one of a Voice over Internet Protocol (VoIP) call, an email, and an instant messaging session to said at least one other buddy list client.
16. The method of claim 1, further comprising:
receiving updated status information corresponding to a change in the user presence at said at least one other IPTV client; and updating the displayed buddy list to reflect the change in the user presence at the at least one other buddy list client.
17. A method comprising:
sensing user presence at a buddy list client device, said user presence corresponding to at least one of status of a television associated with said buddy list client device, whether a Voice over Internet Protocol (VoIP) call is in progress, physical presence of a registered wireless device of a user within a predetermined range of said buddy list client device, and newly stored content;
transmitting status information corresponding to the sensed user presence to a server;
receiving status information from the server corresponding to user presence sensed at at least one other buddy list client device; and displaying a buddy list indicating the user presence at the at least one other buddy list client device.
18. The method of claim 17, wherein said status of a television associated with said buddy list client device comprises at least one of:

an on/off state of said television;
a channel of said television; and a program that said television is tuned to.
19. The method of claim 17, wherein said newly stored content comprises at least one of:
a newly stored audio file;
a newly stored video file; and a newly added appointment in a calendar application.
20. A buddy list client device, comprising:
means for sensing a plurality of types of user presence;
means for transmitting status information corresponding to the sensed plurality of types of user presence to a server;
means for receiving status information from the server corresponding to a plurality of types of user presence of at least one buddy; and means for displaying a buddy list indicating said plurality of types of user presence of at least one buddy.
21. The buddy list client device of claim 20, wherein said sensing means comprises:
means for detecting a registered wireless device of a user within a predetermined range of said buddy list client device.
22. The buddy list client device of claim 20, wherein said displaying means comprises:
means for connecting to a display device to display the buddy list on the display device.
23. The buddy list client device of claim 20, further comprising:

means for receiving one of Internet Protocol Television (IPTV) programming and digital cable programming; and means for playing said received one of IPTV programming and digital cable programming.
24. The buddy list client device of claim 20, further comprising:
means for initiating at least one of a Voice over Internet Protocol (VoIP) call, an email, and an instant messaging session.
25. The buddy list client device of claim 20, further comprising:
means for storing at least one of audio files and video files.
26. A method of controlling buddy lists on a plurality of Internet Protocol Television (IPTV) clients, comprising:
receiving status information corresponding to user presence at an IPTV
client; and transmitting said status information to at least one other IPTV clients.
27. The method of claim 26, wherein said receiving step comprises:
receiving status information corresponding to user presence of a particular user at an IPTV client.
28. The method of claim 27, wherein said transmitting step comprises:
searching a database for at least one buddy list including said particular user; and transmitting said status information to at least one IPTV client associated with said at least one buddy list including said particular user.
29. The method of claim 26, wherein said status information comprises a plurality of types of information corresponding to a plurality of types of user presence.
CA002649964A 2006-06-13 2007-06-06 Method for sensing user presence for buddy list applications Abandoned CA2649964A1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US11/451,790 US20070288627A1 (en) 2006-06-13 2006-06-13 Method for sensing user presence for buddy list applications
US11/451,790 2006-06-13
PCT/US2007/013458 WO2007146089A2 (en) 2006-06-13 2007-06-06 Method for sensing user presence for buddy list applications

Publications (1)

Publication Number Publication Date
CA2649964A1 true CA2649964A1 (en) 2007-12-21

Family

ID=38754713

Family Applications (1)

Application Number Title Priority Date Filing Date
CA002649964A Abandoned CA2649964A1 (en) 2006-06-13 2007-06-06 Method for sensing user presence for buddy list applications

Country Status (4)

Country Link
US (1) US20070288627A1 (en)
EP (1) EP2027686A2 (en)
CA (1) CA2649964A1 (en)
WO (1) WO2007146089A2 (en)

Families Citing this family (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070291747A1 (en) * 2006-06-19 2007-12-20 Stern Benjamin J Method and system for user to user targeted advertising
US20080034038A1 (en) * 2006-08-04 2008-02-07 Jean-Pierre Ciudad Sharing Application Output In Chat Environment
US20080082668A1 (en) * 2006-09-28 2008-04-03 Nortel Networks Limited Presence information delivery based on session participation
US7660749B2 (en) * 2006-09-29 2010-02-09 Apple Inc. Method, system, and medium for representing visitor activity in an online store
US7861175B2 (en) 2006-09-29 2010-12-28 Research In Motion Limited IM contact list entry as a game in progress designate
US20080235337A1 (en) * 2007-03-21 2008-09-25 Cisco Technology, Inc. Adaptive buddy lists
US8498654B2 (en) * 2007-03-23 2013-07-30 At&T Intellectual Property I, L.P. Method and system for location-based communication
JP2009093356A (en) * 2007-10-05 2009-04-30 Sony Corp Information processor and scroll method
KR101413563B1 (en) * 2007-11-05 2014-07-04 삼성전자주식회사 A method to provide seeing and hearing information for displaying channels watched by users
EP2081362B1 (en) 2008-01-21 2013-07-24 Alcatel Lucent Resource arbitration in a converged multi-media environment
CN101981930A (en) * 2008-03-28 2011-02-23 三星电子株式会社 Data receiving method and device for applications providing an IPTV communications service
US8196163B2 (en) * 2008-05-21 2012-06-05 Telefonaktiebolaget L M Ericsson (Publ) Controlled delivery of event information to IPTV users
US9559867B2 (en) 2008-05-30 2017-01-31 Google Technology Holdings LLC Contact group dynamics in networked communication devices
US8630683B2 (en) * 2008-11-24 2014-01-14 Centurylink Intellectual Property Llc System and method for displaying information associated with a cellular device on a user specified display unit
JP4683128B2 (en) * 2009-01-06 2011-05-11 ソニー株式会社 Presence information sharing apparatus, presence information sharing method, presence information sharing program, and presence information sharing system
KR101542520B1 (en) * 2009-01-13 2015-08-07 삼성전자주식회사 Apparatus and method for sharing information through presence service in a communication network
JP2011040036A (en) 2009-03-30 2011-02-24 Avaya Inc System and method for managing communication session using graphical user interface
GB2473261A (en) 2009-09-08 2011-03-09 Nds Ltd Media content viewing estimation with attribution of content viewing time in absence of user interaction
FR2951894B1 (en) * 2009-10-27 2011-11-11 Alcatel Lucent METHOD AND SYSTEM FOR PRESERVING BANDWIDTH IN AN IPTV NETWORK
EP2357806B1 (en) * 2010-01-06 2018-05-23 Lg Electronics Inc. A display device and a method for displaying contents on the same
WO2012000167A1 (en) * 2010-06-29 2012-01-05 青岛海信传媒网络技术有限公司 Method, apparatus and system for service implementation
US20120151357A1 (en) * 2010-12-08 2012-06-14 Microsoft Corporation Presenting device availability statuses
US20140026157A1 (en) * 2011-04-11 2014-01-23 Tao Wang Face recognition control and social networking
CN102752334B (en) * 2011-04-22 2015-05-20 腾讯科技（深圳）有限公司 Geographical location information-based method and system for showing user dynamics
US11089134B1 (en) * 2011-12-19 2021-08-10 Majen Tech, LLC System, method, and computer program product for coordination among multiple devices
US10776103B2 (en) 2011-12-19 2020-09-15 Majen Tech, LLC System, method, and computer program product for coordination among multiple devices
JP5615316B2 (en) * 2012-04-13 2014-10-29 株式会社ソニー・コンピュータエンタテインメント Information processing system and media server
US9544197B2 (en) * 2012-05-01 2017-01-10 Ricoh Company, Ltd. Communication terminal, communication system, display control method, and recording medium storing display control program
US9001216B2 (en) 2012-10-12 2015-04-07 Sony Corporation Method and apparatus for video streaming
CN104854889B (en) * 2013-05-02 2019-05-14 东莞宇龙通信科技有限公司 Terminal and contact person grouping method
KR102099625B1 (en) * 2013-07-16 2020-04-10 삼성전자주식회사 Potable terminal and Method for controlling external device thereof
US9282096B2 (en) * 2013-08-31 2016-03-08 Steven Goldstein Methods and systems for voice authentication service leveraging networking
CN104572771B (en) * 2013-10-25 2020-07-28 腾讯科技（深圳）有限公司 Processing state display method and device
US20150278737A1 (en) * 2013-12-30 2015-10-01 Google Inc. Automatic Calendar Event Generation with Structured Data from Free-Form Speech
CN108366275B (en) * 2018-01-26 2021-04-27 北京一览科技有限公司 Method and apparatus for providing video stream

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6754904B1 (en) * 1999-12-30 2004-06-22 America Online, Inc. Informing network users of television programming viewed by other network users
US6892359B1 (en) * 2000-02-18 2005-05-10 Xside Corporation Method and system for controlling a complementary user interface on a display surface
JP4765182B2 (en) * 2001-01-19 2011-09-07 ソニー株式会社 Interactive television communication method and interactive television communication client device
US7774711B2 (en) * 2001-09-28 2010-08-10 Aol Inc. Automatic categorization of entries in a contact list
US7899915B2 (en) * 2002-05-10 2011-03-01 Richard Reisman Method and apparatus for browsing using multiple coordinated device sets
JP4254996B2 (en) * 2002-06-04 2009-04-15 株式会社日立製作所 Communication system and communication method
US7853563B2 (en) * 2005-08-01 2010-12-14 Seven Networks, Inc. Universal data aggregation
US7239338B2 (en) * 2003-10-01 2007-07-03 Worldgate Service, Inc. Videophone system and method
GB0418411D0 (en) * 2004-08-18 2004-09-22 King S College London A method of discovering contact means for network access devices
US8244179B2 (en) * 2005-05-12 2012-08-14 Robin Dua Wireless inter-device data processing configured through inter-device transmitted data

Also Published As

Publication number Publication date
EP2027686A2 (en) 2009-02-25
WO2007146089A2 (en) 2007-12-21
WO2007146089A3 (en) 2008-03-13
US20070288627A1 (en) 2007-12-13

Similar Documents

Publication Publication Date Title
US20070288627A1 (en) Method for sensing user presence for buddy list applications
US11509341B2 (en) Systems and methods for reconfiguring buttons of a remote control device
JP2020167721A (en) Multi-function remote control device
US9325931B2 (en) Content display-playback system, content display-playback method, recording medium having content display-playback program recorded thereon, and operation control apparatus
US8310602B2 (en) Interactive remote control
US8166504B2 (en) Method and apparatus for processing content in home network using TV channels
US20110291971A1 (en) Highly Integrated Touch Screen Handheld Device
EP1761049A2 (en) Method and apparatus for constructing dynamic menu for user interface
US20120066602A1 (en) Methods and systems for drag and drop content sharing in a multi-device environment
US20070185968A1 (en) Communicating with a remote control
US9288518B2 (en) Information processing system, information processing apparatus, and information processing method
US20130027314A1 (en) Portable Information Processing Device
JPWO2008117586A1 (en) Content reproduction system, content reproduction / control apparatus, and computer program
KR20130050984A (en) Intelligent remote control system
US20090070696A1 (en) System and Method for Programming a Remote Control Device
JP7131383B2 (en) Information processing device, television receiver, information processing system and information processing program

Legal Events

Date Code Title Description
EEER Examination request
FZDE Discontinued