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.
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.
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.
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.
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.
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.
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.
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.
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.
With reference now to
The perceived presence subsystem 104 may include a communications manager 124 and one or more communications devices or applications 128. As illustrated in
As depicted in
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.
With reference now to
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.
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.
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.
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.
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.
With reference now to
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.
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.
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.
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.
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.
With reference now to
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.
With reference now to
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.
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.
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.
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.
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.
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.
Number | Name | Date | Kind |
---|---|---|---|
4817130 | Frimmel, Jr. | Mar 1989 | A |
4941168 | Kelly, Jr. | Jul 1990 | A |
5003577 | Ertz et al. | Mar 1991 | A |
5185782 | Srinivasan | Feb 1993 | A |
5206903 | Kohler et al. | Apr 1993 | A |
5329578 | Brennan et al. | Jul 1994 | A |
5341414 | Popke | Aug 1994 | A |
5371534 | Dagdeviren et al. | Dec 1994 | A |
5410343 | Coddington et al. | Apr 1995 | A |
5430792 | Jesurum et al. | Jul 1995 | A |
5434908 | Klein | Jul 1995 | A |
5511112 | Szlam | Apr 1996 | A |
5555376 | Theimer et al. | Sep 1996 | A |
5712902 | Florence et al. | Jan 1998 | A |
5742763 | Jones | Apr 1998 | A |
5802510 | Jones | Sep 1998 | A |
5819084 | Shapiro et al. | Oct 1998 | A |
5826039 | Jones | Oct 1998 | A |
5828747 | Fisher et al. | Oct 1998 | A |
5864874 | Shapiro | Jan 1999 | A |
5905793 | Flockhart et al. | May 1999 | A |
5982873 | Flockhart et al. | Nov 1999 | A |
5999611 | Tatchell et al. | Dec 1999 | A |
6018655 | Bartle et al. | Jan 2000 | A |
6031896 | Gardell et al. | Feb 2000 | A |
6038296 | Brunson et al. | Mar 2000 | A |
6046762 | Sonesh et al. | Apr 2000 | A |
6068188 | Knowles | May 2000 | A |
6088441 | Flockhart et al. | Jul 2000 | A |
6094681 | Shaffer et al. | Jul 2000 | A |
6128304 | Gardell et al. | Oct 2000 | A |
6130937 | Fotta | Oct 2000 | A |
6144644 | Bajzath et al. | Nov 2000 | A |
6154738 | Call | Nov 2000 | A |
6163607 | Bogart et al. | Dec 2000 | A |
6167266 | Havinis et al. | Dec 2000 | A |
6169795 | Dunn et al. | Jan 2001 | B1 |
6173053 | Bogart et al. | Jan 2001 | B1 |
6185603 | Henderson et al. | Feb 2001 | B1 |
6188756 | Mashinsky | Feb 2001 | B1 |
6192122 | Flockhart et al. | Feb 2001 | B1 |
6199048 | Hudetz et al. | Mar 2001 | B1 |
6226360 | Goldberg et al. | May 2001 | B1 |
6272319 | Narusawa | Aug 2001 | B1 |
6298062 | Gardell et al. | Oct 2001 | B1 |
6307931 | Vaudreuil | Oct 2001 | B1 |
6310947 | Polcyn | Oct 2001 | B1 |
6311231 | Bateman et al. | Oct 2001 | B1 |
6317593 | Vossler | Nov 2001 | B1 |
6330243 | Strandberg | Dec 2001 | B1 |
6330317 | Garfinkel | Dec 2001 | B1 |
6332081 | Do | Dec 2001 | B1 |
6360222 | Quinn | Mar 2002 | B1 |
6408177 | Parikh et al. | Jun 2002 | B1 |
6411682 | Fuller et al. | Jun 2002 | B1 |
6430271 | DeJesus et al. | Aug 2002 | B1 |
6430602 | Kay et al. | Aug 2002 | B1 |
6449260 | Sassin et al. | Sep 2002 | B1 |
6456711 | Cheung et al. | Sep 2002 | B1 |
6463299 | Macor | Oct 2002 | B1 |
6463471 | Dreke et al. | Oct 2002 | B1 |
6477105 | Wu | Nov 2002 | B2 |
6477373 | Rappaport et al. | Nov 2002 | B1 |
6477374 | Shaffer et al. | Nov 2002 | B1 |
6480484 | Morton | Nov 2002 | B2 |
6535600 | Fisher et al. | Mar 2003 | B1 |
6546097 | Peltz | Apr 2003 | B1 |
6549612 | Gifford et al. | Apr 2003 | B2 |
6561805 | Kumar | May 2003 | B2 |
6614783 | Sonesh et al. | Sep 2003 | B1 |
6636587 | Nagai et al. | Oct 2003 | B1 |
6665534 | Conklin et al. | Dec 2003 | B1 |
6668167 | McDowell et al. | Dec 2003 | B2 |
6675168 | Shapiro et al. | Jan 2004 | B2 |
6700967 | Kleinoder et al. | Mar 2004 | B2 |
6738462 | Brunson | May 2004 | B1 |
6741586 | Schuster et al. | May 2004 | B1 |
6750897 | Moshrefi et al. | Jun 2004 | B1 |
6788773 | Fotta | Sep 2004 | B1 |
6789120 | Lee et al. | Sep 2004 | B1 |
6839735 | Wong et al. | Jan 2005 | B2 |
6868395 | Szlam et al. | Mar 2005 | B1 |
6871062 | Trop et al. | Mar 2005 | B2 |
6879677 | Trandal et al. | Apr 2005 | B2 |
6879828 | Virtanen et al. | Apr 2005 | B2 |
6891933 | Kumamoto | May 2005 | B2 |
6925166 | Chan | Aug 2005 | B1 |
6968052 | Wullert, II | Nov 2005 | B2 |
6968179 | De Vries | Nov 2005 | B1 |
6988126 | Wilcock et al. | Jan 2006 | B2 |
6999731 | Cronin | Feb 2006 | B2 |
7023971 | Huart et al. | Apr 2006 | B1 |
7023980 | Lenard | Apr 2006 | B2 |
7027586 | Bushey et al. | Apr 2006 | B2 |
7039040 | Burg | May 2006 | B1 |
7054939 | Koch et al. | May 2006 | B2 |
7068762 | Skladman et al. | Jun 2006 | B2 |
7080321 | Aleksander et al. | Jul 2006 | B2 |
7092370 | Jiang et al. | Aug 2006 | B2 |
7099867 | Okada et al. | Aug 2006 | B2 |
7158630 | Fotta et al. | Jan 2007 | B2 |
7192235 | Blight et al. | Mar 2007 | B2 |
7215760 | Lenard | May 2007 | B2 |
7246371 | Diacakis et al. | Jul 2007 | B2 |
7248677 | Randall et al. | Jul 2007 | B2 |
7269247 | Mashinsky | Sep 2007 | B2 |
7283805 | Agrawal | Oct 2007 | B2 |
7287056 | Loveland et al. | Oct 2007 | B2 |
7299259 | Petroyikh | Nov 2007 | B2 |
7398061 | Mousseau | Jul 2008 | B2 |
20010006893 | Yoshioka | Jul 2001 | A1 |
20020019829 | Shapiro | Feb 2002 | A1 |
20020021307 | Glenn et al. | Feb 2002 | A1 |
20020032040 | Tsukamoto | Mar 2002 | A1 |
20020035605 | McDowell et al. | Mar 2002 | A1 |
20020052225 | Davis et al. | May 2002 | A1 |
20020055350 | Gupte et al. | May 2002 | A1 |
20020065894 | Dalai et al. | May 2002 | A1 |
20020069081 | Ingram et al. | Jun 2002 | A1 |
20020076010 | Sahel | Jun 2002 | A1 |
20020076025 | Liversidge et al. | Jun 2002 | A1 |
20020085701 | Parsons et al. | Jul 2002 | A1 |
20020087630 | Wu | Jul 2002 | A1 |
20020098831 | Castell et al. | Jul 2002 | A1 |
20020116336 | Diacakis et al. | Aug 2002 | A1 |
20020116461 | Diacakis et al. | Aug 2002 | A1 |
20020126701 | Requena | Sep 2002 | A1 |
20020176558 | Tate et al. | Nov 2002 | A1 |
20030014491 | Horvitz et al. | Jan 2003 | A1 |
20030018720 | Chang et al. | Jan 2003 | A1 |
20030028621 | Furlong et al. | Feb 2003 | A1 |
20030073440 | Mukhegee et al. | Apr 2003 | A1 |
20030110228 | Xu et al. | Jun 2003 | A1 |
20030130864 | Ho et al. | Jul 2003 | A1 |
20030154251 | Manabe | Aug 2003 | A1 |
20030154293 | Zmolek | Aug 2003 | A1 |
20030195811 | Hayes et al. | Oct 2003 | A1 |
20040010431 | Thomas et al. | Jan 2004 | A1 |
20040120498 | Sylvain | Jun 2004 | A1 |
20040141594 | Brunson | Jul 2004 | A1 |
20040189698 | Bokish | Sep 2004 | A1 |
20050031107 | Fotta | Feb 2005 | A1 |
20050163104 | Christensen et al. | Jul 2005 | A1 |
20050187781 | Christensen et al. | Aug 2005 | A1 |
20050216848 | Thompson et al. | Sep 2005 | A1 |
20050276407 | Mohler | Dec 2005 | A1 |
20070121808 | Brunson et al. | May 2007 | A1 |
20070127699 | Lenard | Jun 2007 | A1 |
20080089488 | Brunson et al. | Apr 2008 | A1 |
Number | Date | Country |
---|---|---|
0886416 | Dec 1998 | EP |
0930592 | Jul 1999 | EP |
1259053 | Nov 2002 | EP |
1261179 | Nov 2002 | EP |
05-260188 | Oct 1993 | JP |
H8-23577 | Jan 1996 | JP |
9-200813 | Jul 1997 | JP |
H11-046377 | Feb 1999 | JP |
11-088495 | Mar 1999 | JP |
H11-187454 | Jul 1999 | JP |
H11-205837 | Jul 1999 | JP |
2000-102059 | Apr 2000 | JP |
2000-312258 | Nov 2000 | JP |
2001-189774 | Jul 2001 | JP |
2001-224075 | Aug 2001 | JP |
2001-251395 | Sep 2001 | JP |
2001-251682 | Sep 2001 | JP |
2001-350782 | Dec 2001 | JP |
2002-094614 | Mar 2002 | JP |
2002-101155 | Apr 2002 | JP |
2002-108794 | Apr 2002 | JP |
2002-152335 | May 2002 | JP |
2002-176449 | Jun 2002 | JP |
2003-8655 | Jan 2003 | JP |
2003-116175 | Apr 2003 | JP |
2003-517781 | May 2003 | JP |
2003-169147 | Jun 2003 | JP |
2003-196469 | Jul 2003 | JP |
2003-296556 | Oct 2003 | JP |
2004-013303 | Jan 2004 | JP |
2004-30371 | Jan 2004 | JP |
WO 9724010 | Jul 1997 | WO |
WO 9803923 | Jan 1998 | WO |
WO 9812644 | Mar 1998 | WO |
WO 0039964 | Jul 2000 | WO |
WO 0069140 | Nov 2000 | WO |
WO 0145368 | Jun 2001 | WO |
WO 0155915 | Aug 2001 | WO |
WO 0169387 | Sep 2001 | WO |
WO 0230105 | Apr 2002 | WO |
WO 02093959 | Nov 2002 | WO |
WO 03025776 | Mar 2003 | WO |
WO 03054717 | Jul 2003 | WO |
WO 03096559 | Nov 2003 | WO |
WO 03085539 | Oct 2006 | WO |
Number | Date | Country | |
---|---|---|---|
Parent | 10865114 | Jun 2004 | US |
Child | 12147355 | US |