Abstract:
A system for detecting and communicating the presence of one or more computing devices is presented. The invention also presents a method and system for aggregating presence information generated by multiple devices associated with a single user. A server acting as a presence agent on behalf of a first user receives and responds to a subscription request generated by a computing device operated by a second wishing to be permitted as a watcher of the first user. When the second user corresponds to access preferences of the first user, a notify message is sent to the second user&#39;s device that includes presence information indicative of an activity level and availability level associated with the first user. When the first user employs multiple computing devices, the server generates an aggregate presence document that is representative of the overall presence of the first user.

Description:
CROSS-REFERENCE TO RELATED APPLICATION(S) 
     This application is a continuation of U.S. patent application Ser. No. 10/145,673 entitled “METHOD AND SYSTEM FOR SUPPORTING THE COMMUNICATION OF PRESENCE INFORMATION REGARDING ONE OR MORE TELEPHONY DEVICES, filed May 15, 2002, which application is incorporated herein by reference in its entirety. 
    
    
     TECHNICAL FIELD 
     The invention relates generally to communication between computers over a network, and more particularly, to methods and systems for conveying the presence information of one or more devices over the network. 
     BACKGROUND OF THE INVENTION 
     With today&#39;s widespread use of the Internet as a primary communication medium, standard communication tools are now capable of communicating over a computer network. For instance, telephones, pagers, cell phones, handheld computers, and even fax machines now offer features to allow them to be accessed and controlled from over the Internet via an IP address designation or other network addressing scheme. This ability, whereby various communication devices that traditionally use a circuit-switched telephone network, is known as network telephony, or IP telephony when an IP network is involved. 
     As a result of network telephony, today&#39;s devices have the ability to communicate with one another over networks such as the Internet to share information, or receive data. Furthermore, a user having several communication devices (e.g., a cell phone, laptop and handheld PC) can configure each of these devices to a network using a single alias or identifier, such as a username (e.g., username@b.com). In this way, the user is not limited to communicating with others via a single device, but instead has the ability to communicate via several different devices. Nonetheless, the ability for a user to have several devices “present” on a computer network creates a need for other users to be able to determine the status or state of the users many devices. 
     Presence refers to the availability, proximity, activity level or operating state of a user on a network. Commonly, the ability for users to monitor each other&#39;s presence and generate presence information is a feature offered in connection with computer-executable modules or applications that support network telephony. Such modules or applications are known commonly as presence user agents (PUAs). Examples of typical software applications that operate as PUAs or support PUA-like features include instant messaging applications such as MSN Messenger or AOL Instant Messenger. Both of these applications provide an “available buddy” feature, in which a user of the application can determine whether select users are available for engaging in a communication. The generated by the PUA to create the buddy list, i.e. “John OFFLINE” or “Susan ACTIVE,” is known as presence information, and is generally retrieved and maintained by a presence agent. 
     According to most conventional network configurations, the presence agent is a dedicated server or computer-executable module that maintains presence information on behalf of a user having one or more computing devices. Typically, the presence agent supports network telephony protocols such as the session initiation protocol (SIP). Users can register their computing devices with the presence agent (e.g., via a registrar module) in order to have their presence maintained and network telephony services facilitated. As such, a user of a first computing device wishing to detect the presence of a user of a second computing device does so by “subscribing” with the presence agent, such as via a SIP SUBSCRIBE message. The presence agent intermediates between the first user, also known as the watcher, and the second user to facilitate the communication of the second user&#39;s presence information to the first user. 
     The ability of a presence agent to accurately determine and maintain presence information for one or more users significantly enhances communication and task completion over the network. Accurate generation of presence information by the PUA operating upon a user&#39;s device is also critical for effectively conveying presence. For example, a very mobile user may only be on the network at limited times throughout the day, and from varying network locations. By subscribing as a watcher of this mobile user, it becomes possible for another user to assume the role of a watcher and detect the presence of the mobile user during the limited times at which the mobile user&#39;s computing device is actually connected to the network. So, when the mobile user is present, the watcher can correspond instantly with the mobile user via a chat session or videoconferencing call, as opposed to resorting to non-real-time communication such as e-mail messaging. Hence, presence is an especially important factor for facilitating communication between users. Unfortunately, however, conventional PUAs are unable to provide presence information with respect to varying network or operating conditions, and particularly, information sufficient enough to indicate the ability of the device being watched to actually engage in a communication session as a result of a change. 
     As an example of this phenomenon, consider a scenario where a second user has subscribed with a presence agent as a watcher of a first user. If the first user is in the second users&#39; available buddy list, and the first user&#39;s computing device suddenly goes into sleep mode, the second user&#39;s buddy list should still indicate that the first user&#39;s device is available for communication rather than indicate that the first user&#39;s device is “offline.” An indication of offline does not accurately reflect that the first user&#39;s device may still be connected to the network and may be available to receive messages. Yet, many PUAs only provide generalized presence information such as “offline” or “unavailable,” and do not account for more intricate presence conditions. Invariably, this phenomenon results in the present agent&#39;s inability to convey the presence of the user more accurately to the watcher. 
     Still further, many PUAs are unable to generate useful presence information for those users that have several devices registered and present upon the network. Current measures for conveying the presence of users having multiple devices simply call for the presence information of each individual device to be presented to the watcher as a compound document, such as an HTML file. As a result, the watcher that receives the compound document indicating the presence information for each device must inherently “guess” which device&#39;s presence information most accurately reflects the presence of the user. However, just because a user&#39;s mobile phone, pager, laptop, PDA, and desktop computer are all present on the network does not mean the user is using all of them. Indeed, the presence information of the individual devices says very little about the actual presence (e.g., activity or availability) of the user. 
     SUMMARY OF THE INVENTION 
     The invention presents a method for conveying the extent to which a user of a computing device is present upon the network given varying network and device operating conditions. The invention may be used on a variety of devices, including computing devices that communicate over a network via the SIP protocol, as well as those using other protocols. Also, the invention relates to a the use of a document for conveying the presence of a user of a plurality of computing devices. 
     In accordance with an embodiment of the invention, a computing device operable by a user over a computer network (e.g., PDA, cell phone, laptop, and pager) generates presence information indicative of the user&#39;s degree of presence upon the network. More specifically, the device operates a PUA, or the like, that generates a presence document that specifies an activity level and availability level pertaining to the user. The activity level is an attribute of the presence document that indicates what action the user or corresponding device may be engaged in (e.g., idle, away), thus providing an indication of the likelihood of calls or messages actually being accepted from over the network. In relation to the activity level is the availability level, which is an attribute of the presence document that indicates whether the user&#39;s computing device may actually receive calls based on various network or device operating conditions (e.g., offline, online). The activity level and availability level are assigned as a range of values (e.g., numerical, alphabetical), with the higher value representing a higher degree of activity or availability, and the lower value representing a lower degree of activity or availability. 
     In accordance with a further embodiment of the invention, the presence document may also specify a description attribute, which is an attribute associated with the activity or availability level that provides a functional or plain-language description of the assigned level. Also, in addition to the activity and availability level, other attributes may be included within the presence document for conveying user presence, including custom properties that are defined by the user or user&#39;s device. By including the user&#39;s level of availability and activity within the presence document, a watcher or presence agent that receives the document is able to determine more accurately the extent to which the user is present upon the network. 
     In accordance with yet another embodiment of the invention, a network device acting on behalf of a user of a plurality of computing devices generates a single presence document that conveys the overall presence of the user. The network device can be a server operating as a presence agent, or any other device capable of processing presence information. The user&#39;s computing devices generate presence documents to indicate their respective level of activity and availability upon the network, as described above. The network device then processes the presence documents, and generates a single presence document that includes the presence information for each of the plurality of devices, but only the activity level and availability level of the computing device that indicates the highest degree of presence. As such, a watcher is able to determine the user&#39;s presence with respect to all of the user&#39;s devices. 
     Additional features and advantages of the invention will be made apparent from the following detailed description of illustrative embodiments that proceeds with reference to the accompanying figures. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       While the appended claims set forth the features of the present invention with particularity, the invention, together with its objects and advantages, may be best understood from the following detailed description taken in conjunction with the accompanying drawings of which: 
         FIG. 1  is an example of a computer network; 
         FIG. 2  is an example of a computer; and 
         FIG. 3  is a diagram illustrating a server facilitating a call between a first computing device and a second computing device over the network in accordance with various embodiments of the invention. 
     
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
     The invention presents a method for conveying the extent to which a user of a computing device is present upon the network given varying network and device operating conditions. Also, the invention relates to a method for indicating the presence of a user of a plurality of computing devices using a single presence document. In the context of the invention, presence information describes any data that specifies the availability, proximity, activity level or operating state of a computing device or corresponding user of the device from over the network. For example, presence information can be analyzed by a user of a first computing device (a watcher) to determine if a user of a second computing device (a registered device user) is online or offline, busy or idle. This determination is dependent on various factors, including the current activity of the second user, the present operating state of the second user&#39;s computing device, etc. In an effort to stay consistent with common terminology used in the computing industry, this detailed description will use the term “presence” synonymously with the term “presence information” at various times. Moreover, the terms “presence” or “presence information” should be interpreted as relating to the user or one or more devices employed by the user. Those skilled in the art will easily recognize that these terms presence and presents relate to the same phenomenon with respect to network telephony. 
     Also, the invention will be described throughout the course of the description with respect to SIP as a messaging protocol for supporting communication between devices in accordance with the teachings of the invention. Once again, those of skill in the art will recognize that SIP is only one protocol suitable for supporting network telephony and presence, and that other protocols may just as easily be utilized. Other such protocols include the H.323 standard and the Single Computer Telephony Protocol (SCTP). The invention is not limited to any one protocol or messaging implementation, as any means or medium by which two or more devices may communicate to support network telephony applications is suitable. Furthermore, the invention is not limited to any particular network telephony configuration, as any means for exchanging messages between one or more computers via SIP or the like is suitable for use in connection with the invention. This includes network configurations where computing devices such as proxies, redirect servers, registration terminals, presence servers and agents, and one or more clients (presentities) are involved in the communication. 
     As used herein, the term “network telephony” relates to any process wherein a network, such as the Internet, is used as a transmission medium for placing telephone calls or facilitating multimedia sessions between two or more computing devices. This can include multimedia sessions where streaming media (e.g., audio and video data) is exchanged over the network, conference calls, virtual meetings, and other telephony sessions. The term “network telephony” is generic, and can therefore describe or pertain to several other communication processes involving the exchange of packetized data. These include, but are not limited to, IP telephony, Voice over the Internet (VOI) and Voice over IP (VOIP). Also, as used herein, the term “call” (e.g., telephone call) relates to a session in which an exchange of information is commenced or initiated between two or more computing devices over a network, such as with the aide of a telephony application (e.g., MICROSOFT NetMeeting™). In the context of the present invention, a “call” is synonymous to a “message” being sent between devices, and will be used interchangeably at times to describe the interaction between two or more devices over the network. 
     An example of a networked environment in which the invention may be used will now be described with reference to  FIG. 1 . The example network includes several computers  20  communicating with one another over a network  30 , such as the Internet, as represented by a cloud. Network  30  may include many well-known components, such as routers, gateways, hubs, etc. and may allow the computers  20  to communicate via wired and/or wireless media. 
     Referring to  FIG. 2 , an example of a basic configuration for a computer on which the system described herein may be implemented is shown. In its most basic configuration, the computer  20  typically includes at least one processing unit  42  and memory  44 . Depending on the exact configuration and type of the computer  20 , the memory  44  may be volatile (such as RAM), non-volatile (such as ROM or flash memory) or some combination of the two. This most basic configuration is illustrated in  FIG. 2  by dashed line  46 . Additionally, the computer may also have other features/functionality. For example, computer  20  may also include additional storage (removable and/or non-removable) including, but not limited to, magnetic or optical disks or tape. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to stored the desired information and which can be accessed by the computer  20 . Any such computer storage media may be part of computer  20 . 
     Computer  20  may also contain communications connections that allow the device to communicate with other devices. A communication connection is an example of a communication medium. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. The term computer readable media as used herein includes both storage media and communication media. 
     Computer  20  may also have input devices such as a keyboard, mouse, pen, voice input device, touch input device, etc. Output devices such as a display  48 , speakers, a printer, etc. may also be included. All these devices are well known in the art and need not be discussed at length here. 
     Referring now to  FIG. 3 , a general environment for facilitating the communication of presence between one or more computers is illustrated. A server  102  operates as a presence agent, and facilitates the maintenance and transfer of presence information pertaining to the first user  103  with other devices over the network, referred to as watchers. In this example, the server  102  facilitates the transfer of presence information pertaining to a first user  103  with a second user  107 . The server  102  is a computing device that processes messages conforming to a protocol for supporting network telephony (e.g., SIP, H.323). A second device  106 , which in this case is a watcher, executes a presence user agent (PUA) that allows it to receive and interpret the presence information of the user  103  of the first device  104 . The first user  103  operates a first device  104  that executes a PUA for generating presence information. When the second user  107  is allowed to receive the presence information pertaining to the first user  103 , the server  102  transfers the presence document to the second device  106 . 
     The various methods of orchestrating a communication session between the first and second devices, and for transferring presence information by the server  102 , are not discussed in herein. Also, the various access and control procedures commonly employed by a presence agent  102  for ensuring proper access to presence information will not be discussed. Indeed, it is well known in the art that various schemes exist for controlling and adapting the interaction between the first  103  and second user  107  to ensure proper access to and communication of presence information (e.g., usage of an access control list). 
     In accordance with an embodiment of the invention, the first device  104  generates a presence document  200  to convey the extent of its presence upon a network. The presence document  200  is comprised of one or more attributes that relate to the presence of the first computing device  104  or corresponding user  103  of the first computing device  104 . Such attributes include an availability level  208  and activity level  209 . Also, in association with the availability level  208  and activity level  209  is the description attribute  210 . The description attribute provides a functional, or plain-language description of the assigned activity or availability level, and is specified at the discretion of the first computing device  200 . For each presence document generated by a computing device related to the first user  103 , one activity level and availability level is specified. By specifying these attributes within the presence document  200 , the server  102 , acting as a presence agent on behalf of the first user  103  receives presence information that indicates the presence of the first user  103  and corresponding first device  104 . Similarly, the second user  107 , acting as a watcher of the first user  103 , is better able to understand the extent of presence of the first user  103 . 
     The availability level  208  ( FIG. 3 ) is an attribute that indicates whether the first computing device  104  or first user  103  may actually receive calls. The first computing device  104  specifies various availability levels, including those shown in TABLE 1 below. Yet, only one availability level need be specified for a single device at a time. 
                                   TABLE 1                   Availability level settings                Associated           Availability   Description of       Level   Availability Level   Explanation               000   Offline   The user cannot receive calls.       100   Undetermined   The user may be online, but               there is no way to know until a               call is attempted.       200   Connected   The user has a device currently               connected that can receive calls.       300   Online   The user is in proximity to a               device that can receive calls.                    
The availability levels are spread into classes, where each class is a multiple of 100. This is analogous to the response code numbering system used in communication protocols such as the hypertext transfer protocol (HTTP) and SIP. Those skilled in the art will recognize, however, that different values or classes may be used to specify the availability level of the first computing device  104 , and that the invention is not limited to any specific implementation. For example, the first computing device  104  may want to indicate a greater level of availability than “online,” but may not want to show an availability of “always,” and create a new availability value  250 : “likely to take call.” If the second computing device  211  is not familiar with this particular attribute, and receives such presence information, it can abstract it to a class in which is it familiar (e.g., it can generalized to  200 : “connected”).
 
     The activity level  209 , provides an indication of the action in which the first computing device  104  or corresponding first user  103  is engaged. The activity level  209  indicates to the second computing device  106  or other devices that are in the role of watchers the likelihood of calls or messages being accepted by the first computing device  104  or first user  103 . Various activity levels may be specified within the presence document  200 , as shown in Table 2 below. 
     
       
         
               
             
               
               
               
             
           
               
                 TABLE 2 
               
             
             
               
                   
               
               
                 Activity level settings 
               
             
          
           
               
                   
                 Associated 
                   
               
               
                 Activity 
                 Description of 
               
               
                 Level 
                 Activity Level 
                 Explanation 
               
               
                   
               
               
                 000 
                 No explicit 
                 There is no information about the 
               
               
                   
                 activity 
                 activity of the user. 
               
               
                 100 
                 Away 
                 The user is away from the device 
               
               
                 150 
                 At lunch 
                 The user is away at lunch 
               
               
                 200 
                 Idle 
                 No specific activity is currently 
               
               
                   
                   
                 being engaged 
               
               
                 300 
                 Temporarily 
                 The user is not available at the 
               
               
                   
                 unavailable 
                 present time 
               
               
                 400 
                 Active 
                 The user is active 
               
               
                 500 
                 In call 
                 The user is already participating in a 
               
               
                   
                   
                 communications session. 
               
               
                 600 
                 Busy 
                 The user is busy 
               
               
                 700 
                 Do not disturb 
                 The user does not want to participate 
               
               
                   
                   
                 in a communication session 
               
               
                 800 
                 Always 
                 User will stop whatever they&#39;re doing 
               
               
                   
                 interruptible 
                 to receive a call. 
               
               
                   
               
             
          
         
       
     
     Again, those skilled in the art will recognize that the invention is not limited to the set of values or activity classes shown in TABLE 2. Also, it will be recognized by those skilled in the art that specifying the activity level  209  of the  208  first computing device  104  or user  103  in connection with the availability level ensures for more accurate presence. This is in contrast with many existing systems for conveying presence information, in which less useful presence attributes are provided. For example, if a presence document only indicates that the user is “busy,” this is not sufficient information for the watcher to determine if calls can actually be placed with the first computing device  104 . Just because the first user  103  is busy does not mean that calls are not to be received from the second computing device  106 . Various embodiments of the invention account for such intricate distinctions in presence by indicating both the activity level  208  (e.g., busy or active) and availability level  209  (e.g., connected) of a computing device and/or its corresponding user. 
     To further describe the various inventive concepts disclosed herein, examples of the kind information contained in a presence document will now be presented. Possible formats of the various attributes and data included within a presence document to more accurately confer the extent of a user&#39;s presence will also be discussed. Appropriate references will be made to Table 3, which shows an example of a presence document structured according to an embodiment of the invention. For the sake of discussion, those skilled in the art will recognize that the example presence document illustrated in Table 3 is not to be taken as representative of the format for every user situation. Indeed, the formatting and attributes included within the presence document of Table 3 may vary from user to user. Also, it will be recognized by those skilled in the art that numerous standards exist for formatting a presence document, such as XML or SGML, and that the invention is not limited to any one implementation. 
     
       
         
               
             
               
               
             
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
             
           
               
                 TABLE 3 
               
               
                   
               
             
             
               
                 &lt;presently uri = “SIP:nate@snake.net”&gt; 
               
             
          
           
               
                   
                 &lt;availability aggregate = “200” description=“online”/&gt; 
               
               
                   
                 &lt;activity aggregate = “800” description = “do not disturb” override=“true”/&gt; 
               
               
                   
                 &lt;contact contact=“2314@192.1.1.5:5060; q=0.3” /&gt; 
               
               
                   
                 &lt;modes modes=“TEXT” AUDIO VIDEO WHITEBOARD APPSHARE 
               
             
          
           
               
                 FILETRANSFER” /&gt; 
               
             
          
           
               
                   
                 &lt;displayName displayName=“Nate the evil genius.”/ &gt; 
               
               
                   
                 &lt;note note=“I am busy plotting. Don&#39;t bother me unless there&#39;s a good reason” /&gt; 
               
               
                   
                 &lt;phoneNumber label=“Phone in secret lair” number= “+1-787-312-8321” /&gt; 
               
               
                   
                 &lt;preferred Device 
               
             
          
           
               
                   
                 deviceType=“E164” 
               
               
                   
                 label=“Phone in secret lair” 
               
               
                   
                 number=“+1-787-312-8321” 
               
               
                   
                 affinity=“0” /&gt; 
               
             
          
           
               
                   
                 &lt;!-- some custom properties --&gt; 
               
               
                   
                 &lt;archEnemy 
               
             
          
           
               
                   
                 aggregate-“append” 
               
               
                   
                 name=“Doctor Nobody” 
               
               
                   
                 comment = “This guy is pretty tricky! Be careful if you meet him!” /&gt; 
               
             
          
           
               
                   
                 &lt;archEnemy 
               
             
          
           
               
                   
                 aggregate-“append” 
               
               
                   
                 name=“K9 the robot dog” 
               
               
                   
                 comment = “IMHO best to wait for his batteries to run flat.”&gt; 
               
               
                   
                 &lt;!-- custom props can pretty much do what 
               
               
                   
                 they like as long as they don&#39;t break the 
               
               
                   
                 &lt;instructions&gt; 
               
             
          
           
               
                   
                 Here are the schematics &lt;schematics encoding=“CAD”&gt; 
               
             
          
           
               
                   
                 ASOIDCIOPUASKDCOILUOIUOIPUASDKLCUASDLKFJALSKCKM 
               
               
                   
                 ASOIDCIOPUASKDCOILUOIUOIPUASDKLCUASDLKFJALSKCKM 
               
             
          
           
               
                   
                 SCHEMATICS&gt; for this pesky robot. 
               
             
          
           
               
                   
                 &lt;/instructions&gt; 
               
               
                   
                 &lt;/archEnemy&gt; 
               
             
          
           
               
                 &lt;/presentity&gt; 
               
               
                   
               
             
          
         
       
     
     The various elements, attributes, and properties that comprise the presence document of Table 3 are as follows:
 
Presentity:&lt;presentity uri=“SIP:nate@snake.net”&gt;
 
     The containing element for the presence document of Table 3 is &lt;presentity&gt;, which identifies the user with a uniform resource indicator (URI). All sub-elements in &lt;presentity&gt; are regarded to be individual properties.
 
Availability:&lt;availability aggregate=“200” description=“online”/&gt;
 
     The &lt;availability&gt; property indicates whether the user can receive a call. Possible values include “offline,” “undetermined” (e.g. cell phone carriers obscure availability default), and “online.” 
     Rather than using a hard-coded enumeration, a numeric value is used in this example. This makes it easy to compare the activity sent by two different PUAs. For example: given 200 “online,” and 100 “undetermined,” a watcher can conclude that the overall state is 200, since the number is higher. The “description” attribute provides a label for the availability state. In the example of Table 3, the pre-defined values are split into classes defined by multiples of 100. Hence, an implementer can add an additional state and software that doesn&#39;t recognize that particular state still knows how to aggregate states, and still knows a state that is approximately the same as the proprietary state. For example, a value of 250 could mean “likely to take call.” This is in the 2xx class; hence a variant of “online,” but it is more informative. Hence if one PUA sets 200, and another sets 250, the aggregate is 250—“likely to take a call.” 
     Activity:
 
&lt;activity aggregate=“800” description=“do not disturb” override=“true”/&gt;
 
     The &lt;activity&gt; property indicates the activity of a computing device. It uses a numerical value in a manner similar to the availability property. 
     An attribute called “override” is shown as being used in conjunction with the &lt;activity&gt; property, but it may also be used in conjunction with other properties. The override attribute is used to indicate that a particular property is exempt from the aggregation rules. A possible scenario is that a user may actively set a property at a particular PUA, and may want this property to be used in their aggregate presence regardless of what other values were sent by other PUAS.
 
Contact: &lt;contact contact=“2314@192.1.1.5:5060; q=0.3”/&gt;
 
     The &lt;contact&gt; property indicates how the user can be contacted. There can be any number of &lt;contact&gt; entries in a presence document. 
     Communications Modes:
 
&lt;modes modes=“TEXT AUDIO VIDEO WHITEBOARD APPSHARE FILETRANSFER”/&gt;
 
     The modes supported by the devices the PUA represents are listed in a &lt;modes&gt; property. If a mode isn&#39;t listed, it isn&#39;t supported. For example, assume there is a new collaborative technology called Super Foo. When a user runs Super Foo, the user&#39;s computing device advertises its capabilities as &lt;modes modes=“SUPERFOO AUDIO VIDEO”/&gt;. If a watcher of the user just wants to talk to the user using audio, it may. But if the watcher&#39;s computing device also has Super Foo capability, it can use the new collaboration technology. 
     If the presence document represents devices that support different sets of modes (e.g. an instant messaging client and a phone), it can include multiple &lt;modes&gt; elements. If a watcher wants to know whether the user supports a specific combination of modes, the watcher looks for a &lt;modes&gt; element that contains the specific combination. If a watcher doesn&#39;t care that these modes are on different devices, the watcher just looks to see if the modes are listed in any of the &lt;modes&gt; elements.
 
Display Name: &lt;displayName displayName=“Nate the evil genius.”/&gt;
 
     The &lt;displayName&gt; property is the watched user&#39;s screen name. 
     Note:
 
&lt;note note=“I am busy plotting. Don&#39;t bother me unless there&#39;s a good reason”/&gt;
 
     The &lt;note&gt; property includes whatever additional notes the watched user wishes to add. 
     Phone Number:
 
&lt;phoneNumber label=“Phone in secret lair” number=“+1-787-312-8321”/&gt;
 
     The &lt;phone number&gt; property represents the watched user&#39;s phone number or numbers. Possible labels include “Cell” or “Office.” 
     
       
         
               
             
               
               
             
               
               
             
           
               
                   
               
               
                 Preferred Device: 
               
               
                   
               
             
             
               
                   
               
             
          
           
               
                   
                 &lt;preferredDevice 
               
             
          
           
               
                   
                 deviceType=“E164” 
               
               
                   
                 label=“Phone in secret lair” 
               
               
                   
                 number=“+1-787-312-8321” 
               
               
                   
                 affinity=“0” /&gt; 
               
               
                   
                   
               
             
          
         
       
     
     The &lt;preferredDevice&gt; property indicates the device on which the watched user prefers to communicate. If the deviceType is “DNS,” the requests are to be routed through the SIP proxy network using DNS URI addressing. If the deviceType is “E164,” for example, a phone number is also included. Affinity may also be used to establish relative preference when multiple preferred devices are listed. A label is included so the user can describe his/her preferences, if desired. 
     
       
         
               
             
               
               
             
               
               
             
               
               
             
           
               
                   
               
               
                 Custom Properties: 
               
               
                   
               
             
             
               
                   
               
             
          
           
               
                   
                 &lt;archEnemy 
               
             
          
           
               
                   
                 aggregate=“append” 
               
               
                   
                 name=“Doctor Nobody” 
               
               
                   
                 comment=“This guy is pretty tricky! Be careful if you meet 
               
             
          
           
               
                   
                 him!” /&gt; 
               
               
                   
                   
               
             
          
         
       
     
     Custom properties are properties that applications can define for themselves. 
     Up to this point, the invention has been described with respect to the interaction between one or more users that act as watchers, a computing device, and a corresponding user being watched. However, in many instances the user being watched may have more than one device (registered) with the network device at a time. In such cases, presence information is generated by each of the devices, resulting in several presence documents being generated and exchanged with the server that handles presence administration. 
     According to various embodiments of the invention, presences documents generated by multiple devices of a user are aggregated into a single document. There are a variety of ways in which this can be done, but one implementation involves the following: 
     (a) The document having the highest activity level is identified; 
     (b) overrides are applied; 
     (c) the activity and availability properties for the document having the highest activity level are copied into the new aggregate presence document, except as otherwise dictated by overrides; 
     (d) all other properties (other than activity and availability) are copied into the new aggregate presence document. 
     (e) The “contacts” properties are removed. 
     The following example illustrates this implementation. In this example, it is assumed that a fictional character, Nate, is an evil mastermind with his own SIP address (SIP:nate@snake.net). Nate has the following devices:
         An IP desk phone;   A PC running the RTC client UI; and   A fancy wristwatch that does audio as well as text.
 
Nate communicates with a number of other evil geniuses. As well as using his presence service for basic presence information, this circle of collaborators like to know who each other&#39;s enemies are. So Nate maintains another property in his presentity that indicates who his arch enemy is. This enables the villains to gang up and/or backstab each other with greater efficiency.
       

     Nate&#39;s desk phone doesn&#39;t have a PUA. However it is registered to the network. The presence agent server (PAS) notes that the phone is registered, but doesn&#39;t have a presence document posted. It assumes the default document shown in Table 4: 
                                                 TABLE 4                           &lt;presentity uri=“SIP:nate@snake.net”&gt;                &lt;availability aggregate=“300” description=“online” /&gt;           &lt;activity aggregate= “000” description=“no explicit           activity” /&gt;           &lt;contact contact=“1324123@192.1.1.3:5060; user=phone;           q=0.3” /&gt;           &lt;modes modes=“AUDIO” /&gt;                &lt;/presentity&gt;                        
Nate is logged on at his desk PC where he set “do not disturb,” but he hasn&#39;t used it for hours because he isn&#39;t there. He also uses his PC to maintain his ever expanding list of arch enemies. His PC generates the presence document shown in Table 5.
 
                                                                                                                                 TABLE 5                           &lt;presentity uri=“SIP:nate@snake.net”&gt;                &lt;availability aggregate=“200” description=“connected” /&gt;           &lt;activity aggregate=“800” description=“do not disturb”           override=“true”/&gt;           &lt;contact contact=“e2314@192.1.1.5:5060; q=0.3” /&gt;           &lt;modes modes=“TEXT AUDIO VIDEO WHITEBOARD           APPSHARE FILETRANSFER” /&gt;           &lt;displayName displayName=“Nate the evil genius. Bwa ha           ha ha!” /&gt;           &lt;note note=“I am busy plotting. Don&#39;t bother me.” /&gt;           &lt;phoneNumber label=“Phone in secret lair” number= “+1-           787-312-8321” /&gt;           &lt;preferredDeviceType                deviceType=“E164”           label=“Phone in secret lair”           number=“+1-787-312-8321”           affinity=“0” /&gt;                &lt;!-- some custom properties --&gt;           &lt;archEnemy                aggregate=“append”           name=“Doctor Nobody”           comment=“This guy is pretty tricky! Be careful if           you meet him!” /&gt;                &lt;archEnemy                aggregate=“append”           name=“K9 the robot dog”           &lt;instructions&gt;                Here are the schematics &lt;schematics           encoding=“UTF-8”&gt;           ASOIDCIOPUASKDACOILUOIUOIPUAS           &lt;/schematics&gt; for this pesky robot.                &lt;/instructions&gt;                &lt;/archEnemy&gt;                &lt;/presentity&gt;                        
He&#39;s used his wristwatch to override the “do not disturb” with “active,” and the wristwatch generates the presence document shown in Table 6.
 
     
       
         
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
           
               
                   
                 TABLE 6 
               
               
                   
                   
               
             
             
               
                   
                 &lt;presentity uri=“SIP:nate@snake.net”&gt; 
               
             
          
           
               
                   
                 &lt;availability aggregate=“200” description=“connected” /&gt; 
               
               
                   
                 &lt;activity 
               
             
          
           
               
                   
                 aggregate= “400” 
               
               
                   
                 description=“active” 
               
               
                   
                 scope=“user:Mon, 01 Jan 2002 16:10:44 GMT”/&gt; 
               
             
          
           
               
                   
                 &lt;contact contact=“1234123@192.1.1.231:443; q=0.9” /&gt; 
               
               
                   
                 &lt;!-- This device supports a mode not native to the V.1 or 
               
               
                   
                 V.1.1 client --&gt; 
               
               
                   
                 &lt;modes modes=“TEXT AUDIO TELEPATHY” /&gt; 
               
               
                   
                 &lt;displayName displayName=“Nate” /&gt; 
               
               
                   
                 &lt;note note=“Now is a good time to call me” /&gt; 
               
               
                   
                 &lt;phoneNumber label=“Phone in secret lair” number= “+1- 
               
               
                   
                 787-312-8321” /&gt; 
               
               
                   
                 &lt;phoneNumber label=“Fancy watch phone” number= “+1- 
               
               
                   
                 787-312-3121” /&gt; 
               
               
                   
                 &lt;preferredDeviceType 
               
             
          
           
               
                   
                 deviceType=“IP” 
               
               
                   
                 affinity=“900” /&gt; 
               
             
          
           
               
                   
                 &lt;/presentity&gt; 
               
               
                   
                   
               
             
          
         
       
     
     The document with the highest activity level is the document shown in Table 5, which represents the document generated by Nate&#39;s PC. Therefore, an availability level of 200 and an activity level of 800 would ordinarily be copied into the aggregate document. However, Nate has chosen to override the “Do not disturb” level (800) with the “connected” level (200). Thus, watchers see the following aggregate document. 
     
       
         
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
           
               
                   
                 TABLE 7 
               
               
                   
                   
               
             
             
               
                   
                 &lt;presentity uri=“SIP:nate@snake.net”&gt; 
               
             
          
           
               
                   
                 &lt;availability aggregate=“200” description=“connected” /&gt; 
               
               
                   
                 &lt;activity aggregate= “400” description=“active”/&gt; 
               
               
                   
                 &lt;modes modes=“AUDIO” /&gt; 
               
               
                   
                 &lt;modes modes=“TEXT AUDIO VIDEO WHITEBOARD 
               
               
                   
                 APPSHARE FILETRANSFER” /&gt; 
               
               
                   
                 &lt;modes modes=“TEXT AUDIO TELEPATHY” /&gt; 
               
               
                   
                 &lt;displayName displayName=“Nate Jones” /&gt; 
               
               
                   
                 &lt;note note=“I am busy plotting. Don&#39;t bother me.” /&gt; 
               
               
                   
                 &lt;note note=“Now is a good time to call me” /&gt; 
               
               
                   
                 &lt;!-- phone numbers have been concatenated --&gt; 
               
               
                   
                 &lt;phoneNumber label=“Phone in secret lair” number= “+1- 
               
               
                   
                 787-312-8321” /&gt; 
               
               
                   
                 &lt;phoneNumber label=“Fancy watch phone” number= “+1- 
               
               
                   
                 787-312-3121” /&gt; 
               
               
                   
                 &lt;preferredDeviceType 
               
             
          
           
               
                   
                 deviceType=“IP” 
               
               
                   
                 affinity=“900” /&gt; 
               
             
          
           
               
                   
                 &lt;preferredDeviceType 
               
             
          
           
               
                   
                 deviceType=“E164” 
               
               
                   
                 label=“Phone in secret lair” 
               
               
                   
                 number=“+1-787-312-8321” 
               
               
                   
                 affinity=“0” /&gt; 
               
             
          
           
               
                   
                 &lt;archEnemy 
               
             
          
           
               
                   
                 aggregate=“append” 
               
               
                   
                 name=“Doctor Nobody” 
               
               
                   
                 comment=“This guy is pretty tricky! Be careful if 
               
               
                   
                 you meet him!” /&gt; 
               
             
          
           
               
                   
                 &lt;archEnemy 
               
             
          
           
               
                   
                 aggregate=“append” 
               
               
                   
                 name=“K9 the robot dog” 
               
               
                   
                 &lt;instructions&gt; 
               
             
          
           
               
                   
                 Here are the schematics &lt;schematics 
               
               
                   
                 encoding=“UTF-8”&gt; 
               
               
                   
                 ASOIDCIOPUASKDACOILUOIUOIPUAS 
               
               
                   
                 &lt;/schematics&gt; for this pesky robot. 
               
             
          
           
               
                   
                 &lt;/instructions&gt; 
               
             
          
           
               
                   
                 &lt;/archEnemy&gt; 
               
             
          
           
               
                   
                 &lt;/presentity&gt; 
               
               
                   
                   
               
             
          
         
       
     
     In view of the many possible embodiments to which the principles of this invention may be applied, it should be recognized that the embodiment described herein with respect to the drawing figures is meant to be illustrative only and should not be taken as limiting the scope of invention. For example, those of skill in the art will recognize that the elements of the illustrated embodiment shown in software may be implemented in hardware and vice versa or that the illustrated embodiment can be modified in arrangement and detail without departing from the spirit of the invention. Therefore, the invention as described herein contemplates all such embodiments as may come within the scope of the following claims and equivalents thereof. 
     Software applications suitable for generating presence documents include, but are not limited to, e-mail utilities, instant messaging programs, network monitoring programs, video/audio conferencing programs and other such applications. The invention is not limited to any particular PUA implementation, as any mechanism usable by a computing device for generating presence information pertaining to a user is within the scope of the invention.