The present invention is related to the following copending U.S. patent applications filed concurrently herewith, assigned to the assignee of the present invention, and hereby incorporated by reference in their entireties:
The invention relates generally to computer systems and communications.
People communicate in many ways over many types of devices and channels, including by voice, by audio/video, and by text or the like. Voice communications include audio over landline telephones such as connected to POTS (plain old telephone service) lines or PBX (private branch exchange) lines, and cellular and satellite telephones, as well as voice over Internet Protocol (VoIP). Audiovisual communications include video tele-conference (VTC), which also may be Internet Protocol-based communication. Text communications include electronic mail, instant messaging, pagers with text messaging, and so forth.
Some contemporary devices provide multiple ways to communicate, e.g., pocket sized personal computers may have a cellular telephone connection to place audio calls, and a wireless internet connection for sending and receiving electronic mail messages and instant messaging communications. Some mobile devices (e.g., a Smartphone) are considered to be more like telephones, but likewise provide Internet access, and may handle text messaging generally.
One problem with any communications device is that users do not necessarily want to receive communications all the time. For example, in the past when telephone was the main (or only practical) way to reach someone remotely, a telephone user in an important client meeting would tell a receptionist to “hold my calls” in order to avoid being interrupted. Some contemporary telephone systems provide a “do not disturb” feature that essentially does the same thing, such as to route any incoming calls to a voicemail system.
While this is beneficial for telephone calls, such an automatic do not disturb feature does not help with other types of communications that can be similarly distracting. For example, a visible notification may appear on a user's main display screen when an email message is received. Further, the conventional do not disturb feature on a telephone is little more than a switching mechanism that does not discriminate based on the source of the call, take action based on the type of call, or perform other operations that are more intelligent with respect to how an incoming communication is handled, that is, in a way that resembles how a human receptionist might act given the same communication.
What is needed is an automated do not disturb system and related methods for handling contemporary communications in a computer system. The system and method should operate in what is perceived to be an intelligent manner, and be fairly comprehensive in handling communications, as well as flexible and extensible to handle many user scenarios and usage patterns. At the same time, the do not disturb system and method should be straightforward for users to implement and activate.
Briefly, the present invention provides a do not disturb system and method in a computer system at which communications are received. Communications may include virtually any kind of notifications over which a computer system may have some control, including audio over landline telephones such as connected to POTS (plain old telephone service) lines or PBX (private branch exchange) lines, and cellular and satellite telephones, as well as voice over Internet Protocol (VoIP). Audiovisual communications include video tele-conference (VTC), which also may be Internet Protocol-based communication. Text (whether actual text, handwriting or some other human-perceptible format) communications include electronic mail, instant messaging, pagers with text messaging, subscription-based messages such as stock quotes and so forth.
A user may set a computer system into a do not disturb mode by pressing a button such as on a keyboard or on the machine, by setting other physical state such as closing an office door, or by clicking on a user interface of an appropriate software program. The mode may also be entered by an automated process, such as at a scheduled certain time. While in this do not disturb mode, any communication routed through the machine will be evaluated against a set of rules to determine how that communication is to be handled, based on criteria such as the source of the communication (e.g., the caller or sender's identity), the type of communication (e.g., voice or text, and possibly accompanying priority data), and possibly other criteria, such as a level of do not disturb, time-of-day and so forth. Based on the rules versus such criteria, an action comprising a notification and outgoing action is selected, such as via a database lookup and/or applying rules to the criteria.
The action may range from no notification whatsoever for anyone, to limited notifications for certain users and/or types of messages, to full notifications when certain rules are met. Notifications may include any audible, visual or tactile feedback. The rules may be set to include or exclude any particular communicant or group of communicants, and/or any communications types. For example, a rule and action may be set up to block all incoming phone calls based on received caller ID information, except calls from a family member or the user's supervisor, and then only provide a visual notification by flashing an LED and showing the caller ID data. The visual notification need not be on the user's main display screen.
The resultant action taken in response to a communication may include sending a return communication back to the caller or sender. The return communication need not be of the same type as the incoming call or message. For example, an email message, instant message or some other visual notification may be returned to a voice caller indicating that the do not disturb mode is in effect at the recipient's computer, which acts as the center for communications. In the event that the caller ID and/or other information from that call is known, possibly including preset knowledge such as that the incoming telephone number belongs to a mobile device, the output can be adjusted as appropriate, e.g., although a text message should be sent, the text message may be converted to speech to leave a voice message when the call was known to be from a source with indeterminate technological capabilities, such as from a mobile phone that may not handle text, or when the caller is known to be traveling.
In addition to providing an indication to the user, such as lighting an LED proximate the do not disturb button, to remind the user that this mode is active, a publicly visible indicator such as a light atop a user's cubicle wall or by an office door may also communicate this information to others in advance. Colors and/or flash patterns may be varied to enhance visibility and/or indicate a do not disturb level, e.g., do not disturb at all, do not disturb unless very important, do not disturb unless specific clearance was previously given, and so forth. A broadcast message may be sent to selective others, such as to proactively notify other members of a work team of a user's do not disturb status before such disturbance is attempted.
Other advantages will become apparent from the following detailed description when taken in conjunction with the drawings, in which:
a is a representation of a control panel positioned beneath a computer monitor and having a “do not disturb” button incorporated into the control panel, in accordance with an aspect of the present invention;
b is a representation of a “do not disturb” button incorporated into the monitor, in accordance with an aspect of the present invention;
c is a representation of a “do not disturb” activation device, in accordance with an aspect of the present invention;
Exemplary Operating Environment
The invention is operational with numerous other general purpose, or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with the invention include, but are not limited to: personal computers, server computers, hand-held or laptop devices, tablet devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, and so forth, which perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in local and/or remote computer storage media including memory storage devices.
With reference to
The computer 110 typically includes a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by the computer 110 and includes both volatile and nonvolatile media, and removable and non-removable media. By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by the computer 110. Communication media typically embodies computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer-readable media.
The system memory 130 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 131 and random access memory (RAM) 132. A basic input/output system 133 (BIOS), containing the basic routines that help to transfer information between elements within computer 110, such as during start-up, is typically stored in ROM 131. RAM 132 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 120. By way of example, and not limitation,
The computer 110 may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only,
The drives and their associated computer storage media, discussed above and illustrated in
The computer 110 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 180. The remote computer 180 may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 110, although only a memory storage device 181 has been illustrated in
When used in a LAN networking environment, the computer 110 is connected to the LAN 171 through a network interface or adapter 170. When used in a WAN networking environment, the computer 110 typically includes a modem 172 or other means for establishing communications over the WAN 173, such as the Internet. The modem 172, which may be internal or external, may be connected to the system bus 121 via the user input interface 160 or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer 110, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,
Do Not Disturb Computing
The present invention is generally directed towards operating a computer system in a mode which intelligently routes, provides notifications for and otherwise appropriately handles communications and other notifications received at the computer. As such, the computer is generally arranged as a central communications point for multiple communications-related devices, such as generally described in the related copending U.S. patent application Ser. No. entitled “Real-Time Communications Architecture and Methods for use with a Personal Computer System.” As will be understood, the various communication channels, devices and scenarios described herein are only examples, and there are many others to which the present invention will apply.
Turning to
Also represented in
As generally represented in
To handle a user's various communications needs, the real-time communications controller 300 allows a user to connect to various communication channels (e.g., a telephone company switching network, a mobile phone network, the internet or an intranet, and virtually any other local area or wide area network over which communication is possible) using the various communications-related data input/output devices. In general, the user is able to input data via any input mechanism, e.g., any microphone on any device, via any text or pointing-based user data entry mechanism 302 such as the keyboard and/or mouse, and/or the camera 202, and have that data configured as appropriate (e.g., converted from speech to text) and sent to an appropriate (one or possibly more) of the available communication channels. Similarly, the real-time communications controller 300 is able to receive data and output appropriate data to the user on any one or more of the output mechanisms, such as the speaker of a speakerphone 304 when the user has selected that device, the handset telephone 204 when lifted, a headset 306 if activated, the mobile phone or similar computing device 308 if selected, a PBX phone 310 connected to a PBX mechanism 312 and/or a network card 314. When video, graphical and/or text information is available, data can also be displayed on the main display 191 (if active), and/or the auxiliary display 220. Note that some of the devices are represented in
In accordance with an aspect of the present invention, the real-time communications controller 300 controls various communication modes for the user, including the do not disturb mode. To enter this mode, the user can interact with the computer via software, e.g., by pointing and clicking on an a user interface component of an application or operating system program. Alternatively, a more straightforward way for a user to enter a do not disturb mode is by actuation of a hardware button (term button used loosely to indicate one of a variety of available switch types), such as represented in
For example, in one alternative implementation generally represented in
a and 5b show alternative arrangements, with the do not disturb button 522 again provided among routing controls 502 in
Turning to an explanation of the use of a do not disturb button 722, as generally represented in
A user interface 736 also may be used to select the do not disturb mode, as well as to configure the do not disturb rules and resultant actions. As described below, the RTC controller 300 includes logic for controlling what actions occur when communications are received with respect to a do not disturb operating state.
An automated process 738 also may be used to select the do not disturb mode. For example, a user may set up a schedule to select the do not disturb mode at the same hour every day, or whenever some other event occurs or is occurring, e.g., when on a video call the user may not want anything to disturb that call.
The operating system 134 may control the display of the indicator 724. For example, the do not disturb indicator 602 may be lit as steady amber when the do not disturb mode is active, although this may be configurable, e.g., by color-blind individuals. Other colors and/or patterns may indicate additional information to users, such as a level of a do not disturb mode, as described below.
By way of example, consider a “complete” do not disturb mode having no notifications whatsoever (as if the user shut off each telephone ringer and disconnected a network connection), versus a “standard” do not disturb mode in which visual indicators continue to function along with an auxiliary display to allow call screening, however no audible or modal alerts occur that distract the user's attention away from the main task at hand. An amber flashing pattern on the indicator 724 may indicate the “complete” do not disturb mode, while a steady amber light may indicate the “standard” mode. If audible notifications are allowed, ring patterns, tones and/or volume levels may vary based on the state of the do not disturb mode.
As generally represented in
User actions can occur and be detected in any number of ways, including hardware button and software activation and deactivation of the do not disturb mode as described above. The present invention contemplates essentially any way of activating or changing the mode, such as by program, remote control, dial-up, audio commands and so on. User action information may also be communicated by wireless radio 834, and/or from a network connection or other communication channel. Motion and/or proximity sensing can likewise serve as a user action sensor, e.g., related to a user's presence.
Where appropriate, a graphical user interface component 840 shown as part of the DND control logic 800 (but possibly anywhere in the computer system, such as in another application program) may facilitate entry of the user action and do not disturb information. For example, the user may interact with a software program such as related to user contacts to set the variables for how communications received from that contact are handled in each mode. The user may also use the graphical user interface 840 to configure various do not disturb settings.
The present invention similarly outputs information to the user in any feasible manner, including via the user interface when appropriate. Essentially, anything capable of outputting something that can be sensed by a user can serve as an output mechanism, including the displays 191 and/or 220, lights and other indicators 224, the speaker 206 or other audio generating device such as a ringer on a cell phone, and other mechanisms such as one that provides tactile feedback (e.g., a vibrating cell phone). Thus, as used herein, the term “display” is only an example, and is not limited to visible information, but can include any sensed output including non-visual representations. For example, a tone and pattern can “display” communications-related information audibly.
In general, the DND logic 800 receives remotely communicated data (such as an incoming call), and based on various real-time do not disturb rules 802 and user configurable settings 804, responds in a proper manner. For example, for an incoming telephone or cellular call, the DND control logic 400 may display the caller ID information on the auxiliary display 220, or possibly the main display 191 if so configured by the user, flash an indicator but not sound a ring or call waiting tone on the speaker 206, and wait for a user action. If the user presses a phone control button such as a speakerphone button, the call will be connected to the appropriate device, e.g., routed to the speaker 206 and microphone 208. Any other audio, such as music that the user was listening to, may be automatically muted until the call is complete, e.g., until the user again presses the speakerphone button to disconnect. Otherwise the call may be responded to with an automatic action, such as providing a voice mail message and/or sending a text message.
Note that the return action may be specific to the do not disturb mode, (as opposed to a not answering or busy message), and need not be of the same type as the call. For example, a text message may respond to a voice call to indicate that the called party is present, but has requested privacy. In the event that the caller ID and/or other information from that call is known, possibly including preset knowledge such as that the incoming telephone number belongs to a mobile device, the output can be adjusted as appropriate, e.g., although a text message should be sent, the text message may be converted to speech (e.g., by a text to speech converter 832 of
The present invention thus automatically and transparently responds in an appropriate and seemingly intelligent manner to a user's do not disturb needs. By way of example, consider the example above of a user who is working at the computer when a call comes in. Instead of simply sending the call to a recording, the DND control logic 800 analyzes the call data to figure out what type of call it is and who it is from, determines how (if at all) the user should be notified, and provides the notification. Further, the logic 800 determines whether to take an action, and if so, takes the action. With telephone and cellular calls, caller ID may be evaluated to determine the caller's identity, while instant messaging and email provide an identity for network-received messages. Unknown callers and unsolicited text messages may be filtered. However, the present invention is more than a conventional message filter, as it instead takes action to notify, preserve and/or discard incoming communications, and also to possibly automatically respond with an outgoing communication.
The DND logic 800 accesses local notification rules 906 to determine how the user should be notified, (if at all), while outgoing action rules 908 determine what information (if any) will be returned to the other communicating party. A lookup (or lookups) in a database 910, using the caller/sender and the type of call/message as keys, may be one way to obtain the appropriate rules. Note that within types of messages such as email messages, subtypes such as high priority, regular priority and low priority may be used as search keys and/or criteria so as to be assigned their own rules and actions. Other factors such as a DND level 904 (which may vary by time of day, a time out operation and so forth) may be used as part of a search key.
Note that not all type rules and source rules may be contained in the database 910. For example, the user may set special exceptions that may be used before searching the database (or to override or supplement a database result). In this manner, for example, the normal database 910 does not have to be modified for a one-time change that may expire. Type rules 912 and source rules 914 based on user preferences and/or defaults may provide or factor into the final results. An address book may be used in part, e.g., a user may flag a particular contact so as to always let a notification come through for that contact as if DND was off, regardless of the actual DND level.
Once the appropriate type or types of notification is known, a local notification 920 (or more than one) is given to the user based on the notification rules 906. Note that no notification may be given. If a notification is provided, some configurable amount of time may be given, if appropriate, to allow the user to accept the communication before an outgoing communication 922 based on the outgoing action rules 908 is issued. An outgoing communication may be provided, such as a voice mail recording requesting that a voicemail message may be recorded, and/or an instant message or email sent. The message may be “do not disturb” specific, e.g., to indicate that the user is present but currently in a privacy mode, and suggest an alternative course of action for very important calls/messages.
In addition to a set of rules, notification thresholds and presence may also be adjusted when the “Do Not Disturb” state is in already in effect. A software slider bar, or actuation pattern of the DND button may change the current level, or individual settings. For example, when increasing the level, by default, thresholds may be adjusted up one level and presence is set to indicate “Busy”, however this can be customized according to user preferences. A user interface allows the “Do Not Disturb” button to enter a privacy mode that is customizable by user for appropriate visibility, notification and filtering capabilities. For example, a slider bar may set the do not disturb level and bring in various per source and per type settings, with appropriate default levels that may be changed and preserved (e.g., in the database) for each combination, such as by manipulating checkboxes, radio buttons or the like.
As can be readily appreciated, there are any number of user interfaces, types of communications, sources, rules, local notifications and outgoing communications that may be arranged in a given implementation. For example, in one do not disturb state, a user may want the system set such that no calls sound an audible alert except a call from the user's direct boss. Calls that have previously recognized caller ID information may provide a pop-up message and the caller ID information on all calls in which a known caller ID is provided. All other calls are immediately routed to voice mail, and instant messages should be redirected to the auxiliary display instead of popping up on the main display. With the present invention, the user may make selections that alter general rules and/or defaults to provide the desired exceptions, and thereby obtain the appropriate results. A user who is still suffering too many disturbances can dynamically adjust the DND level on demand, or provide additional exceptions.
Further, any number of switches and/or mechanisms such as sensors may control the do not disturb state. For example, in
In addition to the notifying the user and the caller/sender upon a communication, like the DND reminder light for a user, a publicly visible indicator such as a light atop a user's cubicle wall or by an office door may also communicate this do not disturb state to others in advance. Colors and/or flash patterns may be varied to enhance visibility and/or indicate a do not disturb level, e.g., do not disturb at all, do not disturb unless very important, do not disturb unless specific clearance was previously given, and so forth. A broadcast message may be automatically sent to selective others users, such as to notify other members of a work team of a change in a user's do not disturb status (e.g., to or from on or off). Further, do not disturb status may be displayed on another person's workstation (e.g. “busy” in their instant message contact list).
It should be noted that other types of lighting are feasible and may be alternatively implemented. By way of example, as represented in
This same alternative light source (or sources) can be used (as an alternative or in addition to an LED indicator) to communicate alternative states of computer system use or activity including the do not disturb mode. In this condition, the light emanating from the base may works together with a do not disturb control button to indicate a shift in the way the computer is being used. When so configured, selecting the do not disturb mode causes the light emanating from the base to indicate to the user and other people around the user that the computer is now in a different use state.
Further, other aspects of a user's computing environment may change while in the do not disturb mode relative to other modes. For example a desktop theme or appearance may change, including the computers background, fonts, colors and so forth. Sounds may be different, background music may play, and other noticeable difference may occur as generally selected by the user to remind the user and/or notify others of the do not disturb state of operation.
As can be seen from the foregoing detailed description, there is provided a do not disturb communications method and system in a computer system for intelligently handling the incoming notifications with appropriate outputs in the form of local notifications and/or two-way communications. Users may customize the system and method to adjust for their particular needs. At the same time, a simple actuation of a button or software enters or exits the do not disturb mode, or varies a level of the do not disturb mode. The method and system thus provide significant advantages and benefits needed in contemporary computing and communications.
While the invention is susceptible to various modifications and alternative constructions, certain illustrated embodiments thereof are shown in the drawings and have been described above in detail. It should be understood, however, that there is no intention to limit the invention to the specific forms disclosed, but on the contrary, the intention is to cover all modifications, alternative constructions, and equivalents falling within the spirit and scope of the invention.
Number | Name | Date | Kind |
---|---|---|---|
4860342 | Danner | Aug 1989 | A |
5159445 | Gitlin | Oct 1992 | A |
5412417 | Tozuka | May 1995 | A |
5487181 | Dailey | Jan 1996 | A |
5519722 | Akman | May 1996 | A |
5533115 | Hollenbach | Jul 1996 | A |
5546538 | Cobbley | Aug 1996 | A |
5568540 | Grecko | Oct 1996 | A |
5657414 | Lett | Aug 1997 | A |
5675374 | Kohda | Oct 1997 | A |
5675810 | Sellers | Oct 1997 | A |
5768164 | Hollon | Jun 1998 | A |
5802305 | McKaughan | Sep 1998 | A |
5959622 | Greer | Sep 1999 | A |
5999613 | Nabkel et al. | Dec 1999 | A |
6006285 | Jacobs | Dec 1999 | A |
6052442 | Cooper et al. | Apr 2000 | A |
6101610 | Beebe | Aug 2000 | A |
6144363 | Alloul | Nov 2000 | A |
6144644 | Bajzath et al. | Nov 2000 | A |
6172703 | Lee | Jan 2001 | B1 |
6208373 | Fong et al. | Mar 2001 | B1 |
6215420 | Harrison et al. | Apr 2001 | B1 |
6237846 | Lowell | May 2001 | B1 |
6240168 | Stanford et al. | May 2001 | B1 |
6266714 | Jacobs | Jul 2001 | B1 |
6279056 | Jacobs | Aug 2001 | B1 |
6282435 | Wagner et al. | Aug 2001 | B1 |
6346934 | Wugofski | Feb 2002 | B1 |
6362440 | Karidis | Mar 2002 | B1 |
6380968 | Alexander | Apr 2002 | B1 |
6417849 | Lefebvre | Jul 2002 | B2 |
6438585 | Mousseau | Aug 2002 | B2 |
6453027 | Kang | Sep 2002 | B1 |
6483905 | Kikinis | Nov 2002 | B1 |
6507356 | Jackel et al. | Jan 2003 | B1 |
6513128 | Wang | Jan 2003 | B1 |
6518957 | Lehtinen et al. | Feb 2003 | B1 |
6519335 | Bushnell | Feb 2003 | B1 |
6546262 | Freadman | Apr 2003 | B1 |
6603855 | Cannon et al. | Aug 2003 | B1 |
6628194 | Hellebust | Sep 2003 | B1 |
6628267 | Karidis | Sep 2003 | B2 |
6658095 | Yoakum et al. | Dec 2003 | B1 |
6671356 | Lewis | Dec 2003 | B2 |
6671743 | Verity | Dec 2003 | B1 |
6680845 | Agata | Jan 2004 | B2 |
6691233 | Gannage | Feb 2004 | B1 |
6718183 | Blust | Apr 2004 | B1 |
6731316 | Herigstad et al. | May 2004 | B2 |
6741232 | Siedlikowski | May 2004 | B1 |
6757372 | Dunlap et al. | Jun 2004 | B1 |
6806867 | Arruda | Oct 2004 | B1 |
6819961 | Jacobs | Nov 2004 | B2 |
6831657 | Tsutsumi et al. | Dec 2004 | B2 |
6882326 | Hirayama | Apr 2005 | B2 |
6888562 | Rambo et al. | May 2005 | B2 |
6892074 | Tarkiainen | May 2005 | B2 |
6897851 | Carini | May 2005 | B2 |
6902332 | McLoone | Jun 2005 | B2 |
6912283 | Meyerson et al. | Jun 2005 | B2 |
6937950 | Cragun | Aug 2005 | B2 |
6938174 | LeKuch | Aug 2005 | B2 |
6970556 | Wall et al. | Nov 2005 | B2 |
6973167 | Kikinis | Dec 2005 | B2 |
6976216 | Peskin et al. | Dec 2005 | B1 |
6980641 | Stanford et al. | Dec 2005 | B1 |
6996445 | Kamijo | Feb 2006 | B1 |
7036110 | Jeyaraman | Apr 2006 | B2 |
7096391 | Johnson | Aug 2006 | B2 |
7123370 | Watanabe | Oct 2006 | B2 |
7221331 | Bear | May 2007 | B2 |
7231229 | Hawkins | Jun 2007 | B1 |
7243130 | Horvitz | Jul 2007 | B2 |
7272660 | Powers | Sep 2007 | B1 |
7302637 | Maguire | Nov 2007 | B1 |
20010040551 | Yates et al. | Nov 2001 | A1 |
20020015020 | Mobin | Feb 2002 | A1 |
20020080967 | Abdo | Jun 2002 | A1 |
20020087225 | Howard | Jul 2002 | A1 |
20020131072 | Jackson | Sep 2002 | A1 |
20020167458 | Baudisch | Nov 2002 | A1 |
20020167460 | Baudisch | Nov 2002 | A1 |
20030021290 | Jones | Jan 2003 | A1 |
20030025674 | Watanabe | Feb 2003 | A1 |
20030037180 | Madineni et al. | Feb 2003 | A1 |
20030069689 | Ibara | Apr 2003 | A1 |
20030074590 | Fogle | Apr 2003 | A1 |
20030112325 | Boyden et al. | Jun 2003 | A1 |
20030122874 | Dieberger | Jul 2003 | A1 |
20030131148 | Kelley et al. | Jul 2003 | A1 |
20030146903 | Yi | Aug 2003 | A1 |
20030188041 | Fillmore | Oct 2003 | A1 |
20030197685 | Yi | Oct 2003 | A1 |
20030227471 | Eglit | Dec 2003 | A1 |
20040114032 | Kakii | Jun 2004 | A1 |
20040135819 | Maa | Jul 2004 | A1 |
20040141012 | Tootill | Jul 2004 | A1 |
20040155956 | Libbey | Aug 2004 | A1 |
20040177361 | Bernhard et al. | Sep 2004 | A1 |
20040222977 | Bear | Nov 2004 | A1 |
20040222978 | Bear | Nov 2004 | A1 |
20040223058 | Richter | Nov 2004 | A1 |
20040223061 | Bear | Nov 2004 | A1 |
20040223599 | Bear | Nov 2004 | A1 |
20040225502 | Bear | Nov 2004 | A1 |
20040225892 | Bear | Nov 2004 | A1 |
20040225901 | Bear | Nov 2004 | A1 |
20040240167 | Ledbetter et al. | Dec 2004 | A1 |
20040240650 | Bear | Dec 2004 | A1 |
20050068423 | Bear | Mar 2005 | A1 |
20050069101 | Bear | Mar 2005 | A1 |
20050071437 | Bear | Mar 2005 | A1 |
20050071626 | Bear | Mar 2005 | A1 |
20050182822 | Daniel | Aug 2005 | A1 |
20050186942 | Griffin | Aug 2005 | A1 |
20050193396 | Stafford-Fraser | Sep 2005 | A1 |
20060007051 | Bear | Jan 2006 | A1 |
20060048062 | Adamson | Mar 2006 | A1 |
20060061516 | Campbell | Mar 2006 | A1 |
20060095525 | Mousaeau | May 2006 | A1 |
20060130075 | Rhoten | Jun 2006 | A1 |
20060164324 | Polivy | Jul 2006 | A1 |
20060284787 | Bear | Dec 2006 | A1 |
Number | Date | Country |
---|---|---|
0772327 | May 1997 | EP |
0777394 | Jun 1997 | EP |
000816990 | Jan 1998 | EP |
0838934 | Apr 1998 | EP |
0772327 | Feb 1999 | EP |
WO9602049 | Jan 1996 | WO |
Number | Date | Country | |
---|---|---|---|
20040223599 A1 | Nov 2004 | US |