US 7,769,154 B1Grant
Aggregated perceived presence
Issue Date:2010-08-03
•32 Claims
•6 Drawing Sheets
Abstract
A system for controlling the presence of a user perceived by contacts is provided. In particular, a rules engine receives a number of inputs related to the desired accessibility of the user, and from such inputs generates a perceived presence for the user that can be used to control how the user is notified of an incoming communication. Inputs may include an accessibility rating assigned to a contact, the physical presence of the user, the user selected desired accessibility level, and environmental factors. The system allows a user to limit distractions from unimportant contacts or while the user is engaged in other tasks, while allowing more important contacts to have immediate access to the user.
Metadata
Assignee
- Avaya Inc.
Inventors
- Ricardo D. Craft
- Cynthia Ann Hiatt
- Erik J. Johnson
- Ross E. Yakulis
Application Information
Application Number:US 12/147,355
Filing Date:2008-06-26
Priority Date:2004-06-09
Art Unit:2614
Classifications
IPC:
H04M3/42
Patent Drawings (6 sheets)
Description
Cross Reference to Related Applications
[0001] This application is a continuation of application Ser. No. 10/865,114, filed Jun. 9, 2004 now abandoned, the entire disclosure of which is hereby incorporated herein by reference in its entirety.
Field of the Invention
[0002] The present invention is directed to providing a perceived presence in response to attempts to establish communication with a user. In particular, the present invention is directed to providing a different level of perceived presence in response to different communication situations, and to adjusting a level of perceived presence in response to changed conditions.
Background of the Invention
[0003] A wide variety of communication forms are available to users. For example, in a typical office environment, a user may be contacted by telephone, email, instant messages, and messages left in various mailboxes. In order to better manage their time, users need to restrict which communications they receive and when they receive communications.
[0004] Conventional solutions for managing a user's availability through different communication streams include filters to block unwanted communications. However, such filters are typically binary in nature. For instance, a telephone can be placed in a do not disturb setting, according to which all incoming calls will be routed to voice mail. As yet another example, in connection with instant messaging, a user can be either present in the system or not. As still another example, a communications device or application associated with a communications channel can be off or on. Accordingly, conventional systems allow a user to either enable all communications using a selected communications channel, or disable all such communications.
[0005] As a further example, messages from specific senders can be blocked or routed to alternate mailboxes using mail delivery options provided as part of conventional email systems. Even in connection with systems that allow selective filtering, enabling or disabling the filter is a cumbersome process that is not practical to frequently reconfigure, for example in response to changes in the user's environment that may occur during the course of a day.
[0006] Accordingly, conventional communications systems must be administered individually. In addition, such systems implement static filters or blocking mechanisms. That is, changes to filter or blocking parameters are only made in response to direct user intervention. Accordingly, manipulation of available filter mechanisms in response to changes in a user's activities are impractical or impossible. For example, managing a number of communication channels to provide desired levels of accessibility in response to whether the user is in a meeting, on a phone call, needing quiet time, or being completely available, has been impractical or impossible. Such systems have also been limited in their ability to allow only communications from selected senders to pass while blocking communications from other senders.
Summary of the Invention
[0007] According to embodiments of the present invention, a user's level of accessibility or perceived presence can be varied as the user's needs or activities change. In addition, embodiments of the present invention allow a user to select different accessibility ratings for different contacts. In accordance with embodiments of the present invention, the accessibility of a user may be automatically varied according to the user's physical presence or location, and according to environmental factors, such as whether the user is participating in a meeting, engaged in another communication, the time of day, or other factors. The physical presence, environmental factors, and the user selected desired accessibility are provided to a rules engine, together with the accessibility rating associated with a contact, to generate a perceived presence for the user. That is, the presence of a user as seen or perceived by a contact is adjusted according to the presence level that a user wants the contact to see, which is not necessarily the user's true presence. Furthermore, the perceived presence of a user may be different for different contacts.
[0008] In accordance with embodiments of the present invention, the perceived presence of a user determines how an incoming communication will be treated. For example, if the user's perceived presence is “not available,” no attempt will be made to notify the user in real-time of an incoming communication. As another example, if a user's perceived presence is “fully available,” the user will be notified in real-time of any incoming communication. In accordance with still another example, a user may have an intermediate level presence. In accordance with an intermediate level of presence, a user may be notified of certain communications in real-time, but not notified in real-time of other communications. Distinctions between communications that the user will be notified of in real-time and other communications can be made based on, for example, the communication channel used for the communication, the identity of the originator of the communication, and/or the level of urgency attributed to the communication by the originator. In accordance with additional embodiments of the present invention, exceptions can be maintained for selected contacts or communications media. For example, an attempt to notify the user of a communication from a contact designated as always having full access to the user may always be made. As another example, the user may designate contacts whose communications are never allowed to interrupt the user. The perceived presence of a user may also determine through what communications devices or applications an attempt to notify a user of an incoming communication are made. For instance, if a user is in a meeting and has an intermediate level of presence with respect to an incoming communication, a call to the user's cell phone may result in an instant message displayed on the user's personal digital assistant, but no ring on the user's cellular telephone.
[0009] In accordance with embodiments of the present invention, accessibility ratings associated with contacts may be modified in response to a detected number of communications between the user and the contact. For example, the accessibility ranking of a contact may be automatically promoted by the system if the user frequently communicates with that contact. In accordance with other embodiments of the present invention, the accessibility ranking selected by a user for association with a contact will not be modified except by direct user input.
[0010] In accordance with embodiments of the present invention, the perceived presence of a user is determined by a rules engine. Inputs to the rules engine may include selections made by a user with respect to a desired level of accessibility and with respect to accessibility rankings associated with contacts. In addition, the rules engine may receive input regarding environmental factors, such as whether the user is in a meeting, or whether the current time is within normal working hours. Information regarding environmental factors may be provided to the rules engine by calendar applications, including a personal calendar associated with the user. In accordance with other embodiments of the present invention, the rules engine receives input regarding the physical presence of the user. For example, information may be provided regarding which communication devices are available to the user, or whether the user is in a location at which an attempt at real-time notification of an incoming communication should not be made. From the various inputs, a perceived presence is aggregated.
Brief Description of the Drawings
[0011] FIG. 1 is a block diagram of a system in which a perceived presence is provided to contacts in accordance with an embodiment of the present invention;
[0012] FIG. 2 is a block diagram of an apparatus suitable for providing a perceived presence to contacts in accordance with an embodiment of the present invention;
[0013] FIG. 3 is a functional block diagram illustrating the inputs and the output of a rules engine in accordance with embodiments of the present invention;
[0014] FIG. 4 is a flowchart illustrating the determination of a user's perceived presence in accordance with embodiments of the present invention; and
[0015] FIG. 5 is a flowchart illustrating the handling of an incoming communication in accordance with embodiments of the present invention.
Detailed Description
[0016] With reference now to FIG. 1 , a system 100 incorporating a perceived presence subsystem 104 in accordance with embodiments of the present invention is illustrated. The perceived presence subsystem 104 is typically associated with a user 108. In addition, the system 100 includes one or more communications networks 112 that interconnect a number of sending communications devices 116 (e.g., first sending communications device 116a and second sending communications device 116b). Typically, each sending communications device 116 is associated with a corresponding contact person 120.
[0017] The perceived presence subsystem 104 may include a communications manager 124 and one or more communications devices or applications 128. As illustrated in FIG. 1 , examples of communications devices or applications include an email application 128a and an instant messaging application 128b. As can be appreciated by one of skill in the art, an email application 128a or an instant messaging application 128b may run on a variety of platforms, including general purpose computers, personal digital assistance (PDAs) or wireless telephones. Further examples of communications devices or applications 128 include a desk top telephone 128c, an IP telephone 128d, which may include a stand-alone device or a device implemented through a general purpose computer, a wireless telephone 128e, a personal digital assistant (PDA) 128f, and a pager 128g. Still other examples of communications devices or applications include a notification application 128h for providing visual and/or audible notification of communications, for instance through a computing platform, and a voice mail application 128i, which may be provided by a telephony service provider or by a device associated with the user.
[0018] As depicted in FIG. 1 , communications with various communications devices and/or applications 128 associated with the user 108 may be made through the communications manager 124. Alternatively or in addition, communications need not be through the communications manager 124, however notification of a communication directed to a communications device 128 is generally provided to the communications manager 124 so that the communications manager 124 can generate a perceived presence that is to be applied to the incoming communication.
[0019] The communications networks 112 may be any communication network over which a communication channel to a communication device 128 associated with the user 108 may be established. Accordingly, examples of a communication network 112 include the public switched telephony network (PSTN), a wide area network (WAN), such as a the Internet, a local area network (LAN), a private branch exchange (PBX), a wireless communication network, a paging network, and various combinations of different networks. In general, the particular communication network 112 is determined by the sending communications device 116 and by the receiving communications device 128.
[0020] With reference now to FIG. 2 , a communications manager 124 in accordance with embodiments of the present invention is depicted. The communications manager 124 may comprise a general purpose programmable computer or device. Accordingly, the communications manager 124 may include a processor 204, memory 208, an input device 212, an output device 216, a communications network interface 220, and data storage 224. The communications manager 124 may also include a communication bus 228 to enable communications between the various components.
[0021] The processor 204 may include any general purpose programmable processor or controller for executing application programming or instructions. Alternatively, the processor 204 may comprise a specially configured application specific integrated circuit (ASIC). The processor 204 generally functions to run programming code implementing various of the functions performed by the communications manager 124, including the generation of a perceived presence as described herein.
[0022] The memory 208 may be provided for use in connection with the execution of programming by the processor 204, and for the temporary or long-term storage of data or program instructions. The memory 208 may comprise solid state memory, such as DRAM and SDRAM. Where the processor 204 comprises a controller, the memory 208 may be integral to the processor 204.
[0023] Examples of input devices 212 include a keyboard and a pointing device. Examples of output devices 216 that may be associated with a communications manager 124 include a video display.
[0024] The communications network interface 220 may serve to interconnect the communications manager 124 to one or more communications networks 112. For example, where a communications manager 124 is involved with the monitoring of communications addressed to one or more communications devices 128, the communications network interface 220 supports interconnections to the appropriate communications networks 112, and/or to each such communications device 128 directly. Furthermore, a number of communication network interfaces 220 may be provided as part of a communications manager 124 to support the various connections between the communications manager 124 and one or more communication networks 112 and one or more communication devices 128. Accordingly, examples of communication network interfaces 220 include Ethernet, IEEE 802.11, universal serial bus (USB), IEEE 1394, tip/ring, or other interface.
[0025] The data storage 224 may provide storage for application programming and data. For example, application programming stored in the data storage 224 may include a rules engine 232. In addition, the data storage 224 may provide storage for rules 236 that are applied in connection with the operation of the rules engine 232. As further examples, programming for implementing a calendar application 240 and contacts or address list information 244 may be provided. Application programming for implementing various communication functions may also be maintained in the data storage 224. For instance, a mailbox application 248 and call or message log application programming 252 may be stored. Application programming for implementing or providing various communication functions may also be maintained in data storage 224. For example, instant messaging 256, email 260 or telephone (such as a soft telephone) 264 applications may be stored in data storage 224. Application programming for determining a location 268 of a user, for example in connection with a wireless network or other system capable of providing location information may also be maintained in data storage 224.
[0026] With reference now to FIG. 3 , the inputs to and output from a rules engine 232 in accordance with embodiments of the present invention are illustrated. In general, inputs to the rules engine 232 may include contact accessibility 304, physical presence 308, desired accessibility 312, and environmental factors 316. Based on such inputs, the rules engine 232 generates a perceived presence 320 that is used to determine the presence of a user with respect to a particular incoming communication.
[0027] Contact accessibility 304 relates to the accessibility rating of a contact associated with a communication device 116 initiating a communication or otherwise identified as making an attempt to contact the user (hereinafter referred to as a contact or caller). An accessibility rating for an individual may therefore be assigned by the user or by an administrator. An accessibility rating may also be associated with a contact automatically, for example based on the number of previous real-time communications between the contact and the user. Other examples of criteria that may be used to automatically assign an accessibility rating include information related to an entity associated with the sending communication device 116, the location or region from which the communication originated, or any other information that can be obtained in connection with the receipt of incoming communication. A contact accessibility rating can also be assigned by default. For instance, contacts associated with entries in a calendar application 240 maintained by the user may by default be assigned a particular contact accessibility rating, which can then be modified by the user as desired. Contacts that are not associated with the user by an entry in a calendar application 240 or otherwise may be assigned a second accessibility rating by default. The association of a contact accessibility rating with different contacts allows the user to control the accessibility or the presence of the user perceived by a contact, based on the identity of the contact. Examples of selections that can be made by a user include assigning a high accessibility ranking to a spouse, child or boss, a moderate accessibility rating to a coworker, and a low accessibility rating to a salesperson. Therefore, according to the selections made, a user can ensure that some selected contacts will always or usually perceive a high level of user presence, while other selected contacts will always or usually perceive a low level of user presence.
[0028] The physical presence 308 of the user relates to the physical or actual presence of the user. Accordingly, the physical presence 308 may be determined by whether the user is already engaged in a communication (for example is on the telephone), composing a text message, or in a location at which one or more communication devices are not available or operable. As can be appreciated by one of skill in the art, the physical presence of the user can be obtained in various ways. For instance, if the user's telephone line is in use, the user can be assumed to be on the telephone. As a further example, if the user has an email message composition window open, the user can be assumed to be composing a textual message. In addition to input from the status of various communication devices associated with the user, information related to the user's location can also be used as a physical presence 308 input. Location information can be obtained from information related to the location of devices associated with the user. For instance, a personal digital assistant 128f carried by a user within an office building having wireless communication capabilities, for example through Bluetooth connectivity, may be used to determine whether the user is in their own office, in the library, in a colleague's office, or in a boss's office. As an additional example, location information may be obtained from the user's cellular telephone. The physical location 308 may be used to determine the different notification methods that are available in connection with an incoming communication. For instance, if the physical location of the user is determined to be outside of the user's office, a telephone call placed to the user's office telephone 128c could be routed to the user's cellular telephone 128e or directly to voice mail 128i, depending on the various other inputs to the rules engine 232 or on the particular physical location.
[0029] The desired accessibility 312 of the user allows the user to select a general accessibility level. For instance, a user may select a high accessibility, according to which the perceived presence of the user will allow all or many incoming communications to be handled by attempting to notify the user of the communication in real-time. Alternatively, the user can select lower accessibility levels, which have the effect of presenting lower levels of presence with respect to incoming communications. Examples of situations in which a user might select lower levels of desired accessibility 312 include when the user needs quiet time in order to complete a project or where the user is speaking with someone who has dropped by. Accordingly, it can be appreciated that the desired accessibility level 312 allows a user to change their accessibility level generally to in part determine the perceived presence of the user calculated by the rules engine 232 in connection with the various other inputs. In accordance with embodiments of the present invention, the desired accessibility level 312 comprises the input that a user is most likely manipulate during the course of the day in order to exert manual control over the presence of the user perceived by contacts.
[0030] Environmental factors 316 include actual or scheduled activities of the user, the day of the week, time of day, and whether the day is a normal workday. Accordingly, the input environmental factors 316 may be obtained from information regarding the scheduled activities of the user, for example as may be maintained as part of a calendar application 240 associated with the user. Furthermore, environmental factors can be obtained from general schedule information, such as an enterprise calendar, and selected normal working hours, etc. As can be appreciated from the description provided herein, the physical presence 308, desired accessibility 312, and environmental factors 316 are related to the general availability of a user.
[0031] Based on the various inputs 304-316, the rules engine 232 operates to synthesize a level of user presence that is the perceived presence 320 used to determine how the incoming communication is handled. For instance, the rules engine 232 may generate a perceived presence according to which an attempt to notify the user of the incoming communication in real-time is always made when the communication originates from a contact granted a high access level. As a further example, a contact associated with a medium level of access may sometimes be routed to voice mail, while a contact granted a low level of access may always be mounted to voice mail. In addition, the physical presence 308 of a user and environmental factors 316 can be used to determine what communications devices or applications 128 are used in an attempt to notify the user of an incoming communication, and the particular notification method applied by such devices or applications 128.
[0032] With reference now to FIG. 4 , the operation of embodiments of the present invention in connection with generating a perceived presence 320 is illustrated. Initially, at step 400, an incoming communication is detected by the communications network 124, and in particular by the rules engine 232. The user's current desired accessibility selection is then retrieved (step 404). That is the desired accessibility generally specified by the user is retrieved, or a default accessibility selection is retrieved if the user has not set a particular accessibility level (step 404).
[0033] At step 408, a determination is made as to whether physical location information for the user is available. If physical location information is available, that information is retrieved and applied as a physical presence input 308 to the rules engine 232 (step 412). After applying available physical location information, or if no physical location information is available, a determination is made as to whether environmental factor information 316 is available for the user (step 416). If environmental factor information is available, that information is retrieved and applied as an environmental factor 316 input to the rules engine 232. After applying available environmental factor 316 information, or if no such information is available, a determination is made as to whether contact accessibility 304 rating information associated with the originator (i.e., the contact) of the incoming communication is available (step 424). Any available accessibility rating information is applied as a contact accessibility input 304 to the rules engine 232 (step 428). After retrieving available accessibility rating information for the contact, or if such information is not available, the available information (i.e., the desired accessibility 312, physical presence 308, environmental factor 316, and/or contact accessibility 304) is used by the rules engine 232 to determine the perceived presence of the user with respect to the incoming communication (step 432). The determined perceived presence determines, for example, whether an attempt to notify the user of the incoming communication will be made in real-time, or whether it will be routed to a mailbox without an attempt at notification in real-time. The determined presence can also be used to control what devices or applications 128 are used to attempt to notify the user of the incoming communication.
[0034] With reference now to FIG. 5 , aspects of the operation of embodiments of the present invention in selecting a notification mode as a result of an aggregated perceived presence are illustrated. Initially, at step 500, the aggregated perceived presence determined with respect to an incoming communication is obtained. For example, a rules engine 232 may operate as described in connection with FIG. 4 to determine the presence of a user that is to be perceived with respect to the incoming communication.
[0035] At step 504, a determination is made as to whether the perceived presence is at a highest or most access level. If the determined perceived presence is at a most access level, an attempt to connect the originator of the incoming communication (i.e., the contact) to the user in real-time is made (step 508). Furthermore, attempts to notify the user of the incoming communication can be made using multiple devices or applications 128 to improve the chances of successfully notifying the user. If the perceived presence is not at a most access level, a determination is made as to whether the perceived presence is at an intermediate access level (step 512). If the perceived presence is at an intermediate level, the user is notified of the incoming communication in real-time using an intermediate notification method (step 516). An intermediate notification method applied at step 516 may differ from the notification method applied at step 508 in that an attempt to notify the user of the incoming communication in real-time may be made through the communication device or application 128 to which the incoming communication is actually addressed, rather than being made on or through multiple devices or applications. According to further embodiments, an intermediate notification method may result in an attempt to notify the user through a communication device 128 other than the one to which the incoming communication is actually addressed, but that can notify the user in a less obtrusive way.
[0036] If the perceived presence is not at an intermediate level, a determination is then made as to whether the perceived presence is at a low access level (step 520). If the perceived presence is at a low access level, the user is not notified of the incoming communication in real-time (step 524). For example, the incoming communication can be routed to a voice mail immediately. In accordance with embodiments of the present invention, a call may be routed to voice mail, while still providing a relatively unobtrusive notification of the communication to the user. For instance, a ring by a device or application 128 to which an incoming communication comprising a voice telephony call is made may be suppressed, while a textual indication of the incoming communication, such as caller ID information, may be provided by another device or application 128, such as a notification application 128h associated with the user's desktop computer, or with a user's PDA 128f.
[0037] If the perceived presence has not been determined to equal a low access level, or after applying notification as indicated at steps 508, 516 or 524, a determination is made as to whether the user has accepted the incoming communication for real-time handling (528). If the user has accepted the incoming communication for real-time handling, for example by accepting a call, the user is connected to the originator or contact (step 532). If the user does not accept the incoming communication for real-time handling, the communication attempt is logged and any message left by the originator or contact is stored in the user's mailbox (step 536). After connecting the user to the originator at step 532, or after logging the communication attempt and storing any associated message at step 536, the procedure may end.
[0038] Embodiments of the invention described herein allow a user to manage their accessibility, by controlling the user's level of presence that is perceived by (or granted to) different contacts. More particularly, embodiments of the present invention allow a user to assign different accessibility rankings to different contacts, for example to ensure that some contacts are always or usually able to reach the user, and to ensure that other contacts are never or usually unable to reach the user in real-time. In addition, the user can control a desired accessibility level that is applied with respect to all incoming communications, to allow the user to adjust or control their accessibility throughout the day. Furthermore, as described herein, other factors may be monitored and automatically adjusted, for example to control accessibility or perceived presence as the physical presence and/or environmental factors associated with the user change.
[0039] The foregoing discussion of the invention has been presented for purposes of illustration and description. Further, the description is not intended to limit the invention to the form disclosed herein. Consequently, variations and modifications commensurate with the above teachings, within the skill and knowledge of the relevant art, are within the scope of the present invention. The embodiments describes hereinabove are further intended to explain the best mode presently known of practicing the invention and to enable others skilled in the art to utilize the invention in such or in other embodiments with various modifications required by their particular application or use of the invention. It is intended that the appended claims be construed to include the alternative embodiments to the extent permitted by the prior art.
Claims
What is claimed is:
1. A method for managing access to a user, comprising:
receiving a selection of a first availability level from a first user, wherein said first availability level is selected from a plurality of availability levels;
receiving a first communication associated with a first contact, wherein said first communication is addressed to said first user;
determining a level of presence of said first user with respect to said first communication associated with said first contact, wherein said determination is based on:
said selected first availability level,
a contact accessibility rating of said first contact,
a first physical presence of said first user, wherein said first physical presence of said first user is determined from at least one of a status of a communication device associated with said first user, and a location of a device associated with said first user, and
a first environmental factor associated with said first user, wherein said first environmental factor is obtained from at least one of a calendar application associated with said first user and first user schedule information; and
based on said determined level of presence, selecting a first mode of handling said first communication.
2. The method of claim 1, further comprising:
receiving a second communication associated with said first contact, wherein said second communication is addressed to said first user;
detecting a change in said environmental factor associated with said first user from said first environmental factor to a second environmental factor;
determining a level of presence of said first user with respect to said second communication associated with said first contact, wherein said determination is based on said selected first availability level, a contact accessibility rating of said first contact, and said second environmental factor associated with said first user; and
based on said determined level of presence, selecting a second mode of handling said second communication.
3. The method of claim 2, wherein said environmental factor comprises user schedule information and at least one of a time of day, a day of the week, and a status of a day as a holiday or regular work day.
4. The method of claim 1, further comprising:
receiving a second communication associated with said first contact, wherein said second communication is addressed to said first user;
detecting a change in a physical presence of said first user from said first physical presence to a second physical presence;
determining a level of presence of said first user with respect to said second communication associated with said first contact, wherein said determination is based on said selected first availability level, a contact accessibility rating of said first contact, and said second physical presence of said first user; and
based on said determined level of presence, selecting a second mode of handling said first communication.
5. The method of claim 4, wherein said detecting a change in a physical presence of said first user comprises detecting a change in a location of a device associated with said first user.
6. The method of claim 4, wherein said detecting a change in a physical presence of said first user comprises detecting a change in an availability of a communication channel of a communication device associated with said first user.
7. The method of claim 1, wherein said first mode of handling said first communication comprises notifying said first user that said first communication is being directed to a message repository, and providing said first user an opportunity to answer said first communication in real-time.
8. The method of claim 2, wherein said first mode of handling said first communication comprises allowing a communication device to which said first communication is addressed to ring normally, and wherein said second mode of handling said second communication comprises suppressing an audible ring by a communication device to which said second communication is addressed.
9. The method of claim 1, further comprising:
compiling a list of contacts associated with said first user; and
associating a first contact accessibility rating with each contact within said list of contacts.
10. The method of claim 1, further comprising receiving from said first user a selected accessibility rating for a contact.
11. A computational component for performing a method, the method comprising:
detecting a first incoming communication;
retrieving a desired user accessibility associated with a first user;
obtaining: 1) a contact accessibility rating for a first contact associated with said incoming communication; 2) first physical location information associated with said first user, wherein said first physical location information is determined from at least one of a communication status of a communication device associated with said first user, and a location of a communication device associated with said first user; and 3) environmental factor information associated with said first user, wherein said environmental factor information is obtained from at least one of a calendar application associated with said first user and first user schedule information;
applying said retrieved desired user accessibility and said contact accessibility rating for said first contact, first physical location information associated with said first user, and environmental factor information associated with said first user to a rules engine to determine a level of presence of said first user with respect to said first communication;
in response to determining a first level of presence, applying a first mode of handling said first communication; and
in response to determining a second level of presence, applying a second mode of handling said first communication.
12. The method of claim 11, wherein said contact accessibility rating for a first contact is obtained, and wherein said obtained contact accessibility rating for said first contact is applied to determine a level of presence of said first user with respect to said first communication.
13. The method of claim 11, wherein said obtaining said environmental factor information includes:
accessing a calendar associated with said first user; and
determining a scheduled status of said first user, wherein said availability of said first user includes a scheduled status of said first user.
14. The method of claim 11, further comprising:
receiving from said first user an association of a first accessibility rating with a first contact, and
receiving from said first user an association of a second accessibility rating with respect to a second contact, wherein at said first accessibility level a communication from said first contact over a first communication channel is immediately forwarded to said first user, and wherein at said first accessibility level a communication from said second contact over said first communication channel is not immediately forwarded to said first user.
15. The method of claim 14, wherein an association of an accessibility rating with respect to a third contact is not received from said first user, and wherein said second accessibility rating is associated with said third contact with respect to a communication received from said third contact.
16. The method of claim 11, wherein said computational component comprises a computer readable storage medium containing instructions for performing the method.
17. The method of claim 11, wherein said computational component comprises a logic circuit.
18. An apparatus for filtering communication channels, comprising:
first means for providing communications associated with a user;
means for detecting a first communication from a first contact addressed to said first means for providing communications;
means for determining from a plurality of inputs a perceived presence for application in response to said first communication, said inputs including:
a) an accessibility rating of said first contact;
b) a physical presence of said user, wherein said physical presence includes at least one of a status of a user communication device and a location of a user communication device;
c) a desired accessibility of said user;
d) an environmental factor associated with said user, wherein said environmental factor includes a scheduled status of said user;
wherein in response to a first perceived presence a first notification method is applied.
19. The apparatus of claim 18, further comprising:
means for maintaining a schedule, wherein an input to said means for determining includes an environmental factor associated with said first user, and wherein said environmental factor includes a scheduled status as indicated by said means for maintaining a schedule.
20. The apparatus of claim 18, further comprising:
means for determining a physical location of a user communication device of said first user, wherein an input to said means for determining includes a physical location of said user communication device of said first user.
21. The apparatus of claim 18, further comprising:
means for maintaining accessibility ratings for contacts, wherein an input to said means for determining includes an accessibility rating of said first contact.
22. The apparatus of claim 18, further comprising:
means for maintaining a desired accessibility of said user, wherein an input to said means for determining includes a desired accessibility of said user.
23. The apparatus of claim 18, further comprising:
second means for providing communications associated with said user, wherein said first notification method comprises notifying said user of said incoming communication through said first means for providing communications and said second means for providing communications.
24. The apparatus of claim 18, further comprising:
second means for providing communications associated with said user, wherein said first communication is addressed to said first means for providing communications, and wherein said first notification method comprises notifying said user of said incoming communication through said second means for providing communications only.
25. An apparatus for establishing a perceived communications presence of a user, comprising:
a rules engine;
a first set of information input to said rules engine, including a contact accessibility rating, wherein said first contact accessibility rating is selected from a set of at least three different contact accessibility rating levels, a physical presence of a first user, wherein said physical presence of said first user is provided by at least one of a status of a communication device associated with said first user and a location of a communication device associated with the first user, a desired accessibility selected by said first user, and an environmental factor associated with said first user, wherein said environmental factor is associated with at least one of a calendar application and schedule information associated with said first user;
an output from said rules engine, wherein a perceived presence for use in connection with a communication addressed to said first user is determined by said rules engine.
26. The apparatus of claim 25, further comprising:
a computing platform wherein said rules engine runs on said computing platform.
27. The apparatus of claim 25, further comprising:
a first communication device associated with said first user, wherein said output from said rules engine controls at least a first operating parameter of said first communication device.
28. The apparatus of claim 27, wherein said at least a first operating parameter of said first communication device comprises operation of a device for notifying said first user of an incoming communication.
29. The apparatus of claim 27, further comprising a second communication device associated with said first user, wherein said output from said rules engine controls at least a first operating parameter of said second communication device.
30. The apparatus of claim 27, wherein said rules engine is running on said first communication device.
31. A method for managing access to a user, comprising:
receiving a selection of a first availability level from a first user;
receiving a first communication associated with a first contact, wherein said first communication is addressed to said first user;
determining a level of presence of said first user with respect to said first communication associated with said first contact, wherein said determination is based on said selected first availability level, a contact accessibility rating of said first contact, and at least one of a first physical presence of said first user and a first environmental factor associated with said first user;
based on said determined level of presence, selecting a first mode of handling said first communication;
monitoring communications addressed to said first user over a first communication channel;
monitoring communications addressed to said first user over a second communication channel;
presenting to said first user a list contacts associated with said monitored communications; and
receiving from said first user a selected contact accessibility rating for association with at least some of said listed contacts.
32. A method for managing access to a user, comprising:
receiving a selection of a first availability level from a first user;
receiving a first communication associated with a first contact, wherein said first communication is addressed to said first user;
determining a level of presence of said first user with respect to said first communication associated with said first contact, wherein said determination is based on said selected first availability level, a contact accessibility rating of said first contact, and at least one of a first physical presence of said first user and a first environmental factor associated with said first user;
based on said determined level of presence, selecting a first mode of handling said first communication;
monitoring communications addressed to said first user over a first communication channel;
compiling a list of contacts associated with said monitored communications;
associating a first contact accessibility rating with contacts associated with a first number of communications with said first user that result in real-time communications; and
associating a second contact accessibility rating with contacts associated with less than said first number of communications with said first user that result in real-time communications.
Patent Citations (194)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4817130(A) | 1989-03-01 | Frimmel, Jr. | Applicant |
| US4941168(A) | 1990-07-01 | Kelly, Jr. | Applicant |
| US5003577(A) | 1991-03-01 | Ertz et al. | Applicant |
| US5185782(A) | 1993-02-01 | Srinivasan | Applicant |
| US5206903(A) | 1993-04-01 | Kohler et al. | Applicant |
| US5329578(A) | 1994-07-01 | Brennan et al. | Applicant |
| US5341414(A) | 1994-08-01 | Popke | Applicant |
| US5371534(A) | 1994-12-01 | Dagdeviren et al. | Applicant |
| US5410343(A) | 1995-04-01 | Coddington et al. | Applicant |
| US5430792(A) | 1995-07-01 | Jesurum et al. | Applicant |
| US5434908(A) | 1995-07-01 | Klein | Applicant |
| US5511112(A) | 1996-04-01 | Szlam | Applicant |
| US5555376(A) | 1996-09-01 | Theimer et al. | Applicant |
| US5712902(A) | 1998-01-01 | Florence et al. | Applicant |
| US5742763(A) | 1998-04-01 | Jones | Applicant |
| US5802510(A) | 1998-09-01 | Jones | Applicant |
| US5819084(A) | 1998-10-01 | Shapiro et al. | Applicant |
| US5826039(A) | 1998-10-01 | Jones | Applicant |
| US5828747(A) | 1998-10-01 | Fisher et al. | Applicant |
| US5864874(A) | 1999-01-01 | Shapiro | Applicant |
| US5905793(A) | 1999-05-01 | Flockhart et al. | Applicant |
| US5982873(A) | 1999-11-01 | Flockhart et al. | Applicant |
| US5999611(A) | 1999-12-01 | Tatchell et al. | Examiner |
| US6018655(A) | 2000-01-01 | Bartle et al. | Applicant |
| US6031896(A) | 2000-02-01 | Gardell et al. | Applicant |
| US6038296(A) | 2000-03-01 | Brunson et al. | Applicant |
| US6046762(A) | 2000-04-01 | Sonesh et al. | Applicant |
| US6068188(A) | 2000-05-01 | Knowles | Applicant |
| US6088441(A) | 2000-07-01 | Flockhart et al. | Applicant |
| US6094681(A) | 2000-07-01 | Shaffer et al. | Applicant |
| US6128304(A) | 2000-10-01 | Gardell et al. | Applicant |
| US6130937(A) | 2000-10-01 | Fotta | Applicant |
| US6144644(A) | 2000-11-01 | Bajzath et al. | Applicant |
| US6154738(A) | 2000-11-01 | Call | Applicant |
| US6163607(A) | 2000-12-01 | Bogart et al. | Applicant |
| US6167266(A) | 2000-12-01 | Havinis et al. | Applicant |
| US6169795(B1) | 2001-01-01 | Dunn et al. | Applicant |
| US6173053(B1) | 2001-01-01 | Bogart et al. | Applicant |
| US6185603(B1) | 2001-02-01 | Henderson et al. | Applicant |
| US6188756(B1) | 2001-02-01 | Mashinsky | Applicant |
| US6192122(B1) | 2001-02-01 | Flockhart et al. | Applicant |
| US6199048(B1) | 2001-03-01 | Hudetz et al. | Applicant |
| US6226360(B1) | 2001-05-01 | Goldberg et al. | Applicant |
| US6272319(B1) | 2001-08-01 | Narusawa | Applicant |
| US6298062(B1) | 2001-10-01 | Gardell et al. | Applicant |
| US6307931(B1) | 2001-10-01 | Vaudreuil | Applicant |
| US6310947(B1) | 2001-10-01 | Polcyn | Applicant |
| US6311231(B1) | 2001-10-01 | Bateman et al. | Applicant |
| US6317593(B1) | 2001-11-01 | Vossler | Applicant |
| US6330243(B1) | 2001-12-01 | Strandberg | Applicant |
| US6330317(B1) | 2001-12-01 | Garfinkel | Applicant |
| US6332081(B1) | 2001-12-01 | Do | Applicant |
| US6360222(B1) | 2002-03-01 | Quinn | Applicant |
| US6408177(B1) | 2002-06-01 | Parikh et al. | Applicant |
| US6411682(B1) | 2002-06-01 | Fuller et al. | Applicant |
| US6430271(B1) | 2002-08-01 | DeJesus et al. | Applicant |
| US6430602(B1) | 2002-08-01 | Kay et al. | Applicant |
| US6449260(B1) | 2002-09-01 | Sassin et al. | Applicant |
| US6456711(B1) | 2002-09-01 | Cheung et al. | Applicant |
| US6463299(B1) | 2002-10-01 | Macor | Applicant |
| US6463471(B1) | 2002-10-01 | Dreke et al. | Applicant |
| US6477105(B2) | 2002-11-01 | Wu | Applicant |
| US6477373(B1) | 2002-11-01 | Rappaport et al. | Applicant |
| US6477374(B1) | 2002-11-01 | Shaffer et al. | Applicant |
| US6480484(B2) | 2002-11-01 | Morton | Applicant |
| US6535600(B1) | 2003-03-01 | Fisher et al. | Applicant |
| US6546097(B1) | 2003-04-01 | Peltz | Applicant |
| US6549612(B2) | 2003-04-01 | Gifford et al. | Applicant |
| US6561805(B2) | 2003-05-01 | Kumar | Applicant |
| US6614783(B1) | 2003-09-01 | Sonesh et al. | Applicant |
| US6636587(B1) | 2003-10-01 | Nagai et al. | Applicant |
| US6665534(B1) | 2003-12-01 | Conklin et al. | Applicant |
| US6668167(B2) | 2003-12-01 | McDowell et al. | Applicant |
| US6675168(B2) | 2004-01-01 | Shapiro et al. | Applicant |
| US6700967(B2) | 2004-03-01 | Kleinoder et al. | Applicant |
| US6738462(B1) | 2004-05-01 | Brunson | Applicant |
| US6741586(B1) | 2004-05-01 | Schuster et al. | Applicant |
| US6750897(B1) | 2004-06-01 | Moshrefi et al. | Applicant |
| US6788773(B1) | 2004-09-01 | Fotta | Applicant |
| US6789120(B1) | 2004-09-01 | Lee et al. | Applicant |
| US6839735(B2) | 2005-01-01 | Wong et al. | Applicant |
| US6868395(B1) | 2005-03-01 | Szlam et al. | Applicant |
| US6871062(B2) | 2005-03-01 | Trop et al. | Applicant |
| US6879677(B2) | 2005-04-01 | Trandal et al. | Applicant |
| US6879828(B2) | 2005-04-01 | Virtanen et al. | Applicant |
| US6891933(B2) | 2005-05-01 | Kumamoto | Applicant |
| US6925166(B1) | 2005-08-01 | Chan | Applicant |
| US6968052(B2) | 2005-11-01 | Wullert, II | Applicant |
| US6968179(B1) | 2005-11-01 | De Vries | Applicant |
| US6988126(B2) | 2006-01-01 | Wilcock et al. | Applicant |
| US6999731(B2) | 2006-02-01 | Cronin | Applicant |
| US7023971(B1) | 2006-04-01 | Huart et al. | Applicant |
| US7023980(B2) | 2006-04-01 | Lenard | Applicant |
| US7027586(B2) | 2006-04-01 | Bushey et al. | Applicant |
| US7039040(B1) | 2006-05-01 | Burg | Applicant |
| US7054939(B2) | 2006-05-01 | Koch et al. | Applicant |
| US7068762(B2) | 2006-06-01 | Skladman et al. | Applicant |
| US7080321(B2) | 2006-07-01 | Aleksander et al. | Applicant |
| US7092370(B2) | 2006-08-01 | Jiang et al. | Applicant |
| US7099867(B2) | 2006-08-01 | Okada et al. | Applicant |
| US7158630(B2) | 2007-01-01 | Fotta et al. | Applicant |
| US7192235(B2) | 2007-03-01 | Blight et al. | Applicant |
| US7215760(B2) | 2007-05-01 | Lenard | Applicant |
| US7246371(B2) | 2007-07-01 | Diacakis et al. | Applicant |
| US7248677(B2) | 2007-07-01 | Randall et al. | Applicant |
| US7269247(B2) | 2007-09-01 | Mashinsky | Applicant |
| US7283805(B2) | 2007-10-01 | Agrawal | Applicant |
| US7287056(B2) | 2007-10-01 | Loveland et al. | Applicant |
| US7299259(B2) | 2007-11-01 | Petroyikh | Applicant |
| US7398061(B2) | 2008-07-01 | Mousseau | Applicant |
| US2001/0006893(A1) | 2001-07-01 | Yoshioka | Applicant |
| US2002/0019829(A1) | 2002-02-01 | Shapiro | Applicant |
| US2002/0021307(A1) | 2002-02-01 | Glenn et al. | Applicant |
| US2002/0032040(A1) | 2002-03-01 | Tsukamoto | Applicant |
| US2002/0035605(A1) | 2002-03-01 | McDowell et al. | Applicant |
| US2002/0052225(A1) | 2002-05-01 | Davis et al. | Applicant |
| US2002/0055350(A1) | 2002-05-01 | Gupte et al. | Applicant |
| US2002/0065894(A1) | 2002-05-01 | Dalai et al. | Applicant |
| US2002/0069081(A1) | 2002-06-01 | Ingram et al. | Applicant |
| US2002/0076010(A1) | 2002-06-01 | Sahel | Applicant |
| US2002/0076025(A1) | 2002-06-01 | Liversidge et al. | Applicant |
| US2002/0085701(A1) | 2002-07-01 | Parsons et al. | Applicant |
| US2002/0087630(A1) | 2002-07-01 | Wu | Applicant |
| US2002/0098831(A1) | 2002-07-01 | Castell et al. | Applicant |
| US2002/0116336(A1) | 2002-08-01 | Diacakis et al. | Applicant |
| US2002/0116461(A1) | 2002-08-01 | Diacakis et al. | Applicant |
| US2002/0126701(A1) | 2002-09-01 | Requena | Applicant |
| US2002/0176558(A1) | 2002-11-01 | Tate et al. | Applicant |
| US2003/0014491(A1) | 2003-01-01 | Horvitz et al. | Applicant |
| US2003/0018720(A1) | 2003-01-01 | Chang et al. | Applicant |
| US2003/0028621(A1) | 2003-02-01 | Furlong et al. | Applicant |
| US2003/0073440(A1) | 2003-04-01 | Mukhegee et al. | Applicant |
| US2003/0110228(A1) | 2003-06-01 | Xu et al. | Applicant |
| US2003/0130864(A1) | 2003-07-01 | Ho et al. | Applicant |
| US2003/0154251(A1) | 2003-08-01 | Manabe | Applicant |
| US2003/0154293(A1) | 2003-08-01 | Zmolek | Applicant |
| US2003/0195811(A1) | 2003-10-01 | Hayes et al. | Applicant |
| US2004/0010431(A1) | 2004-01-01 | Thomas et al. | Applicant |
| US2004/0120498(A1) | 2004-06-01 | Sylvain | Applicant |
| US2004/0141594(A1) | 2004-07-01 | Brunson | Applicant |
| US2004/0189698(A1) | 2004-09-01 | Bokish | Applicant |
| US2005/0031107(A1) | 2005-02-01 | Fotta | Applicant |
| US2005/0163104(A1) | 2005-07-01 | Christensen et al. | Applicant |
| US2005/0187781(A1) | 2005-08-01 | Christensen et al. | Applicant |
| US2005/0216848(A1) | 2005-09-01 | Thompson et al. | Applicant |
| US2005/0276407(A1) | 2005-12-01 | Mohler | Applicant |
| US2007/0121808(A1) | 2007-05-01 | Brunson et al. | Applicant |
| US2007/0127699(A1) | 2007-06-01 | Lenard | Applicant |
| US2008/0089488(A1) | 2008-04-01 | Brunson et al. | Applicant |
| EP886416 | 1998-12-01 | Applicant | |
| EP930592 | 1999-07-01 | Applicant | |
| EP1259053 | 2002-11-01 | Applicant | |
| EP1261179 | 2002-11-01 | Applicant | |
| JP5-260188 | 1993-10-01 | Applicant | |
| JPH8-23577 | 1996-01-01 | Applicant | |
| JP9-200813 | 1997-07-01 | Applicant | |
| JPH11-046377 | 1999-02-01 | Applicant | |
| JP11-088495 | 1999-03-01 | Applicant | |
| JPH11-187454 | 1999-07-01 | Applicant | |
| JPH11-205837 | 1999-07-01 | Applicant | |
| JP2000-102059 | 2000-04-01 | Applicant | |
| JP2000-312258 | 2000-11-01 | Applicant | |
| JP2001-189774 | 2001-07-01 | Applicant | |
| JP2001-224075 | 2001-08-01 | Applicant | |
| JP2001-251395 | 2001-09-01 | Applicant | |
| JP2001-251682 | 2001-09-01 | Applicant | |
| JP2001-350782 | 2001-12-01 | Applicant | |
| JP2002-094614 | 2002-03-01 | Applicant | |
| JP2002-101155 | 2002-04-01 | Applicant | |
| JP2002-108794 | 2002-04-01 | Applicant | |
| JP2002-152335 | 2002-05-01 | Applicant | |
| JP2002-176449 | 2002-06-01 | Applicant | |
| JP2003-8655 | 2003-01-01 | Applicant | |
| JP2003-116175 | 2003-04-01 | Applicant | |
| JP2003-517781 | 2003-05-01 | Applicant | |
| JP2003-169147 | 2003-06-01 | Applicant | |
| JP2003-196469 | 2003-07-01 | Applicant | |
| JP2003-296556 | 2003-10-01 | Applicant | |
| JP2004-013303 | 2004-01-01 | Applicant | |
| JP2004-30371 | 2004-01-01 | Applicant | |
| WO97/24010 | 1997-07-01 | Applicant | |
| WO98/03923 | 1998-01-01 | Applicant | |
| WO98/12644 | 1998-03-01 | Applicant | |
| WO/39964 | 2000-07-01 | Applicant | |
| WO/69140 | 2000-11-01 | Applicant | |
| WO1/45368 | 2001-06-01 | Applicant | |
| WO1/55915 | 2001-08-01 | Applicant | |
| WO1/69387 | 2001-09-01 | Applicant | |
| WO2/30105 | 2002-04-01 | Applicant | |
| WO2/093959 | 2002-11-01 | Applicant | |
| WO3/025776 | 2003-03-01 | Applicant | |
| WO3/054717 | 2003-07-01 | Applicant | |
| WO3/096559 | 2003-11-01 | Applicant | |
| WO3/085539 | 2006-10-01 | Applicant |
Non-Patent Literature (62)
- U.S. Appl. No. 12/242,103, filed Sep. 30, 2008, Zmolek.Applicant
- U.S. Appl. No. 12/242,432, filed Sep. 30, 2008, Brunson et al.Applicant
- U.S. Appl. No. 12/242,458, filed Sep. 30, 2008, Brunson et al.Applicant
- U.S. Appl. No. 12/242,484, filed Sep. 30, 2008, Brunson et al.Applicant
- U.S. Appl. No. 12/242,504, filed Sep. 30, 2008, Brunson et al.Applicant
- U.S. Appl. No. 12/242,538, filed Sep. 30, 2008, Brunson et al.Applicant
- U.S. Appl. No. 12/243,009, filed Sep. 30, 2008, Brunson et al.Applicant
- U.S. Appl. No. 10/865,114, filed Jun. 9, 2004, Craft.Applicant
- U.S. Appl. No. 11/542,295, filed Oct. 3, 2006, Somani.Applicant
- U.S. Appl. No. 11/626,217, filed Jan. 23, 2007, Coughlan.Applicant
- Andy Zmolek; “SIMPLE and Presence: Enterprise Value Propositions,” Avaya presentation, 16 pages, presented Jan. 24, 2002.Applicant
- Atkins et al “Common Presence and Instant Messaging: Message Format,” Network Working Group (Jan. 9, 2003), available at http://www.ietf.internet-drafts/draft-ietf-impp-cpim-msgfmt-06.txt, 31 pages.Applicant
- Berners-Lee et al.; “Uniform Resource Identifiers (URI); Generic Syntax,” Network Working Group, Request for Comments 2396 (Aug. 1998), 38 pages.Applicant
- Bill Michael, “The Politics of Naming” www.cConvergence.com (Jul. 2001) pp. 31-35.Applicant
- CC News: Call Center Technology, “FaceTime gives voice, vision to instant messaging”, available at http://www.ccnews.com/may2000/depts/cct/cctstory2.htm, 2 pages; Copyright 2000, 1999.Applicant
- Chavez et al., “Interactive Applications of Personal Situation-Aware Assistants”, Computers and Graphics, Pergamon Press LTD., Oxford, GB, vol. 23, No. 6, Dec. 1999, pp. 903-915, XP 004187839, ISSN: 0097-8493.Applicant
- CommWeb.com “Enterprise Customer Interfaces: Application Messaging Via Instant Messaging” (Dec. 9, 2002) , available at http://www.commweb.com/article/COM20021209S0001/2, 3 pages.Applicant
- CosmoCall Universe™, “The Carrier-Grade, All-IP Contact Center Platform for Next Generation Network-Based Services” (2002) 3 pages.Applicant
- CosmoCall Universe™, “The Next Generation IP Contact Center Platform”, available at http://www.cosmocom.com/ProductInfo/Product.htm, 18 pages, 1997-2003.Applicant
- Crocker et al. “Common Presence and Instant Messaging (CPIM),” Network Working Group (Aug. 14, 2002), available at http://www.ietf.internet-drafts/draft-ietf-impp-cpim-03.txt, 33 pages.Applicant
- Dawson et al.; “Vcard MIME Directory Profile,” Network Working Group (Sep. 1998), available at http://www.ietf.org/rfc/rfc2426.txt?number=2426, 40 pages.Applicant
- Day et al. “A Model for Presence and Instant Messaging,” Network Working Group (Feb. 2000), available at http://www.ietf.org/rfc/rfc2277.txt?number=2778, 16 pages.Applicant
- Day et al.; “Instant Messaging/Presence Protocol Requirements,” Network Working Group (Feb. 2000), available at http://www.ietf.org/rfc/rfc2779.txt?number=2779, 25 pages.Applicant
- e-Vantage Solutions, “Customer Service Window”, available at http://www.evgl.com/dsw.html, 2 pages, 2003.Applicant
- FaceTime Communications Press Release, “Amica Insurance Selects FaceTime Communications to Provide Instant Messaging-Based Customer Service in Enterprise” (Jun. 25, 2001), available at http://www.factime.com/pr/pr010625.shtm, 2 pages.Applicant
- FaceTime Communications website, “Customer Services”, available at http://www.facetime.com/custsvcs.shtm, 4 pages, 2003.Applicant
- FaceTime Communications website, “Overview”, available at http://www.facetime.com/solutions.shtm, 4 pages, 2003.Applicant
- FaceTime Communications website, “Presence Management”, available at http://www.facetime.com/presence.shtm, 3 pages, 2003.Applicant
- Fielding et al.; “Hypertext Transfer Protocol—HTTP/1.1,” Network Working Group, Request for Comments 2068 (Jan. 1997), 152 pages.Applicant
- G. Klyne et al., “Instant Messaging using APEX”, Network Working Group, Jun. 1, 2001, 19 pages.Applicant
- G. Klyne; “A Syntax for Describing Media Feature Sets,” Network Working Group (Mar. 1999), available at http://wvvw.ietf.org/rfc/rfc2533.txt?number=2533, 35 pages.Applicant
- G. Klyne; “Protocol-independent Content Negotiation Framework,” Network Working Group (Sep. 1999), available at http://www.ietf.org/rfc/rfc2703.txt?number=2703, 19 pages.Applicant
- Grigonis, Computer Technology Encyclopedia (2000) pp. 342-345, 389-392.Applicant
- Gulbrandsen et al.; “A DNS RR for Specifying the Location of Services (DNS SRV),” Network Working Group (Feb. 2000), available at http://www.ietf.org/rfc/rfc2782.txt?number=2782, 12 pages.Applicant
- Holtman et al.; “HTTP Remote Variant Selection Algorithm—RVSA/1.0,” Network Working Group (Mar. 1998), available at http://www.ietf.org/rfc/rfc2296.txt?number=2296, 13 pages.Applicant
- Holtman et al.; “Transparent Content Negotiation in HTTP,” Network Working Group (Mar. 1998), available at http://www.ietf.org/rfc/rfc2295.txt?number=2295, 55 pages.Applicant
- J. Rosenberg et al., “SIP extensions for Instant Messaging”, Internet Engineering Task Force, Jul. 18, 2001, 22 pages.Applicant
- MIT Project Oxygen, “Oxygen: Pervasive, Human-Centered Computing” MIT Laboratory for Computer Science, MIT Artificial Intelligence Laboratory (May 2002).Applicant
- Ovisoft Technologies, “Ovisoft Messenger—Call Center Solutions”, available at http://www.ofisoft.com/solutioncallcenter.htm, 1 page, 2003.Applicant
- Richard Grigonis, Computer Telephony Encyclopedia (2000) pp. 367-375.Applicant
- Richard Grigonis,. Computer Telephony Encyclopedia (2000) pp. 413-430.Applicant
- Richard Shockey, ‘ENUM: Phone Numbers Meet the Net’ www.cConveroence.corn (Jul. 2001) pp. 21-30.Applicant
- Rose et al.. “The APEX Presence Service,” Network Working Group (Jan. 14, 2002), available at http://www.ieff.org/internet-drafs/draft-ielf-apex-presence-06.txt, 31 pages.Applicant
- Salvator, Dave, “Review: Skype Voice Chat”, Available at http://www.findarticles.com/p/articles/mi—zdext/is—200310/ai—ziff109903>, Extreme Tech, Oct. 2003, 2 pages.Applicant
- Schulzrinne, H., et al., “The Session Initiation Protocol: Internet-Centric Signaling”, IEEE Communications Magazine (Oct. 2000), vol. 38, No. 10, pp. 134-141.Applicant
- Stephanie Losi, “Instant Messaging for Call Centers Leaves 'Em Smiling” www.CRMDaily.com (Jun. 4, 2001), available at http://www.newsfactor.com/perl/story/10246.html, 3 pages.Applicant
- Steve Taylor et al., “SIP in the call center” Network World Convergence Newsletter (Aug. 27, 2003), available at http://www.nwfusion.com/newsletters/converg/2003/0825converge2.html, 4 pages.Applicant
- Sugano et al, “Common Presence and Instant Messaging (CPIM) Presence Information Data Format,” Network Working Group (Dec. 2002), available at http://www.lettorofintemet-drafts/draft-letf-impo-cnim-oidf-07.bct, 26 pages.Applicant
- The MIT Oxygen Project, Cambridge, MA, Apr. 25-26, 2000.Applicant
- Trudy Walsh, “Instant messaging boosts service at Texas call center” GCN (Nov. 2001), available at http://www.gcn.com/cgi-bin/udt/im.display.printable?client.id=state2&story.id=16765, 2 pages.Applicant
- Venus Valley, “Live chat for your website”, Available at http://www.pppindia.com/vvchat/shots.htm>, Venus Valley Live Support, 2003, 2 pages.Applicant
- WiredRed News Release, “WiredRed to Provide Secure Instant Messaging for Eight New Call Center Customers”, available at http://www.wiredred.com/news—release—callctr.html, 2 pages, Sep. 28, 2002.Applicant
- XML-NS Tim Bray et al., “Namespaces in XML”, W3C recommendation: xml-names, Jan. 14, 1999, 12 pages.Applicant
- “Phone Mail Override for Incoming Calls”, IBM Technical Disclosure Bullitin, vol. 37, No. 11, Nov. 1994.Applicant
- “CallWave Launches Mobile Call Screening and Mobile Call Transfer for Cell Phones; First Network-Independent VoIP Application to Deliver wireless/Wireline Convergence”; Callwave, Inc.; Internet Article printed from http://investor.callwave.com/phoenix.zhtml?c=180005&p=irol-newsArticle—print&ID=651; Dec. 7, 2004; 2 pages.Applicant
- Official Action for U.S. Appl. No. 10/865,114, mailed Oct. 18, 2005, pp. 1-18.Applicant
- Official Action for U.S. Appl. No. 10/865,114, mailed Mar. 9, 2006, pp. 1-16.Applicant
- Advisiory Action for U.S. Appl. No. 10/865,114, mailed May 17, 2006, pp. 1-4.Applicant
- Notice of Panel Decision from Pre-Appeal Brief Review for U.S. Appl. No. 10/865,114, mailed Aug. 17, 2006, pp. 1-2.Applicant
- Examiner's Answer to Appeal Brief for U.S. Appl. No. 10/865,114, mailed Dec. 27, 2006, pp. 1-18.Applicant
- Notice of Allowance for U.S. Appl. No. 10/865,114, mailed Jul. 10, 2008, pp. 1-7.Applicant
- Okuyama et al., “Instant Message Technique for Supporting New Mobile Service”, Fuzitsu, Fuzitsu Inc., Jul. 13, 2001, vol. 52, the fourth number, pp. 262-267 (translated abstract).Applicant