The following description relates generally to providing a user interface and more particularly to providing an informational tool tip for an instant messaging user interface.
Online service providers facilitate access to information and services by providing interactive UIs (User Interfaces) that help users navigate to desired resources. Generally, a UI allows a user to execute particular commands or to link to certain locations by simply selecting screen objects such as icons, windows, and drop-down menus. The design of a UI has a significant impact on a user's online experience. In particular, the icons, the windows, and the menus of a UI may be arranged to enable a user to locate preferred information and services quickly and easily.
In one general aspect, an interface enables perception of information regarding a communications session that leverages an instant messaging platform. The user interface includes an instant messaging application user interface that enables perception and selection of instant messaging communications sessions for an instant messaging user, a mechanism to determine the content from within a desired instant messaging session that is not actively displayed, and an informational tool tip that provides a perceivable indication to the user of at least a portion of the determined content of the desired instant messaging session.
Implementations may include one or more of the following features. For example, the tool tip may be activated in response to user selection of the desired instant messaging session. In one implementation, the user selection may be inferred based upon the position of a user input device relative to the instant messaging communications session. For instance, the selection may be inferred based upon maintaining the user input device in a position relative to the instant messaging communications session for a predetermined threshold period of time. In another implementation, the user selection may be an overt selection activity. For instance, the overt selection may be carried out by manipulating a user input device.
In one implementation, the informational tool tip may be rendered in a pop up window, and may be rendered as an overlay. The tool tip may provide a perceivable indication of less than all of the determined content of the desired instant messaging session. The tool tip may be closed automatically.
In another implementation, the interface includes one or more instant messaging sub-interfaces that represent distinct and concurrent instant messaging communications sessions. The interface may also include interface tabs associated with one or more of the sub-interfaces. The interface tabs enable user selection among the sub-interfaces, and each interface tab persists beyond active display of the associated sub-interface. The tool tip may be activated in response to user selection of the interface tab associated with the desired instant messaging session. For instance, the tool tip may be activated based on the position of a user input device that is proximate to one of the interface tabs associated with the desired instant messaging session.
In one implementation, the user interface is a visual interface. For example, the desired instant messaging session may include an exchange of one or more text messages, or one or more audio-video messages such as a video message. In another implementation, the user interface may be an audible interface. For example, the desired instant messaging session may include an exchange of one or more audio messages, or one or more audio-visual messages such as a video message.
Aspects of the informational tool tip may be implemented by an apparatus and/or by a computer program stored on a computer readable medium. The computer readable medium may comprise a disc, a client device, a host device, and/or a propagated signal. In addition, aspects of the informational tool tip may be implemented in a client/host context or in a standalone or offline client device. The informational tool tip may be rendered in a client/host context and may be accessed or updated through a remote device in a client/host environment. The informational tool tip also may be rendered by the standalone/offline device and may be accessed or updated through a remote device in a non-client/host environment such as, for example, a LAN server serving an end user or a mainframe serving a terminal device.
Other features will be apparent from the following description, including the drawings, and from the claims.
Like reference symbols in the various drawings indicate like elements.
In general, an informational tool tip may be provided for an instant messaging (IM) user interface (UI), such as a tabbed IM UI having one or more interface tabs, where each interface tab is assigned to a pending IM session, and the tabs may appear adjacent to one another to, among other things, enable selection of and switching between IM sessions. When several interface tabs are displayed, the active tab corresponds to the IM session currently being viewed or manipulated by the user, and inactive tabs are rendered for the IM sessions which are not currently being viewed or manipulated by the user.
An informational tool tip for the IM UI may be capable of presenting to the user a perceivable indication of at least a portion of an IM communications session that is not being actively displayed. As such, the informational tool tip is able to accommodate a user who seeks to perceive information about one of the inactive IM sessions that is not actively displayed to the user, while maintaining active display of the currently active IM session.
In order to activate the informational tool tip, the user may select a desired IM session that is not being actively displayed. For example, to activate and render the informational tool tip, the user may position a mouse or other viewer input device proximate to or over the interface tab corresponding to the desired IM session. The informational tool tip may be rendered in any location on the display.
The informational tool tip may be used to present all or a portion of the desired IM communications session. In one implementation, a pre-determined number of lines or characters of the desired IM session are presented. In another implementation, a pre-determined number of messages communicated between the buddy and the user are presented. In yet another implementation, only recent messages communicated within a predetermined threshold time period are displayed. For example, the informational tool tip may show all messages communicated within the last thirty (30) minutes. In still another implementation, the tool tip may show the entire IM session. The contents of the desired IM session may be made available to the tool tip by, for example, a client system or a host system, or a combination thereof.
Typically, IM communications involve an instantaneous or nearly instantaneous communication between two users, where each user is able to perceive online presence information regarding other selected users (“buddies”). The IM communications are typically peer-to-peer after authentication has been performed. Examples of IM communications exist over AIM, AOL Instant Messaging, Yahoo Messenger, MSN, and ICQ, among others.
For illustrative purposes,
The client device 120 typically includes a general-purpose computer 170 having an internal or external memory 172 for storing data and programs such as an operating system 174 (e.g., DOS, Windows™, Windows 95™, Windows 98, Windows 2000™, Windows Me™, Windows XP™, Windows NT™, OS/2, or Linux) and one or more application programs. Examples of application programs include authoring applications 176 (e.g., word processing, database programs, spreadsheet programs, or graphics programs) capable of generating documents or other electronic content; client applications 178 (e.g., America Online (AOL) client, CompuServe client, AOL Instant Messenger (AIM) client, interactive television (ITV) client, Internet Service Provider (ISP) client, or instant messaging (IM) client) capable of communicating with other computer users, accessing various computer resources, and viewing, creating, or otherwise manipulating electronic content; and browser applications 180 (e.g., Netscape's Navigator or Microsoft's Internet Explorer) capable of rendering standard Internet content and other content formatted according to standard protocols such as the Hypertext Transfer Protocol (HTTP).
One or more of the application programs may be installed on the internal or external storage 172 of the general-purpose computer 170. Alternatively, in another implementation, the client controller 125 may access application programs externally stored in and/or performed by one or more device(s) external to the general-purpose computer 170.
The general-purpose computer 170 also includes a central processing unit 182 (CPU) for executing instructions in response to commands from the client controller 125. The general-purpose computer 170 may include a communication device 184 for sending and receiving data. One example of the communication device 184 is a modem. Other examples include a transceiver, a set-top box, a communication card, a satellite dish, an antenna, a network adapter, or some other mechanism capable of transmitting and receiving data over the communications link 115 through a wired or wireless data pathway 150. The general-purpose computer 170 also may include a television (“TV”) tuner 186 for receiving television programming in the form of broadcast, satellite, and/or cable TV signals. As a result, the client device 120 can selectively and/or simultaneously display network content received by communications device 184 and TV programming content received by the TV tuner 186.
The general-purpose computer 170 may include an input/output interface 188 that enables wired or wireless connection to various peripheral devices 190. Examples of peripheral devices 190 include, but are not limited to, a mouse 191, a mobile phone 192, a personal digital assistant 193 (PDA), an MP3 player (not shown), a keyboard 194, a display monitor 195 with or without a touch screen input, a TV remote control 196 for receiving information from and rendering information to users, and an audiovisual input device 198.
Although
Referring to
The client device 120 and the host device 135 are generally capable of executing instructions under the command of, respectively, a client controller 125 and a host controller 140. The client device 120 and the host device 135 are connected to, respectively, the client controller 125 and the host controller 140 by, respectively wired or wireless data pathways 130 and 145, which are capable of delivering data.
The client device 120, the client controller 125, the host device 135, and the host controller 140 typically each include one or more hardware components and/or software components. An example of a client device 120 or a host device 135 is a general-purpose computer (e.g., a personal computer) or software on such a computer capable of responding to and executing instructions in a defined manner. Other examples include a special-purpose computer, a workstation, a server, a device, a component, other physical or virtual equipment or some combination of these capable of responding to and executing instructions. The client device 120 and the host device 135 may include devices that are capable of establishing peer-to-peer communications.
An example of client controller 125 or host controller 140 is a software application loaded on the client device 120 or the host device 135 for commanding and directing communications enabled by the client device 120 or the host device 135. Other examples include a program, a piece of code, an instruction, a device, a computer, a computer system, or a combination of these for independently or collectively instructing the client device 120 or the host device 135 to interact and operate as described. The client controller 125 and the host controller 140 may be embodied permanently or temporarily in any type of machine, component, physical or virtual equipment, storage medium, or propagated signal capable of providing instructions to the client device 120 and the host device 135.
The communications link 115 typically includes a delivery network 160 making a direct or indirect communication between the client system 105 and the host system 110, irrespective of physical separation. Examples of a delivery network 160 include the Internet, the World Wide Web, WANs, LANs, analog or digital wired and wireless telephone networks (e.g. Public Switched Telephone Network (PSTN), Integrated Services Digital Network (ISDN), and Digital Subscriber Line (xDSL)), radio, television, cable, or satellite systems, and other delivery mechanisms for carrying data. The communications link 115 may include communication pathways 150, 155 that enable communications through the one or more delivery networks 160 described above. Each of the communication pathways 150, 155 may include, for example, a wired, wireless, cable or satellite communication pathway.
In one implementation, the IM host system 310 may have characteristics similar to those described above with respect to host system 110, and the client system 105 and the buddy client system 305 may include communication software to enable access by users to the IM host system 310.
The IM host system 310 may support IM services irrespective of a user's network or Internet access. Thus, the IM host system 310 may allow users to send and receive IMs, regardless of whether they have access to any particular ISP. The IM host system 310 also may support associated services, such as administrative matters, advertising, directory services, chat, and interest groups related to the IM. The IM host system 310 has an architecture that enables the devices (e.g., servers) within the IM host system 310 to communicate with each other. To transfer data, the IM host system 310 employs one or more standard or exclusive IM protocols.
To access the IM host system 310 to begin an IM session in the implementation of
Once connectivity is established, a user who is using client system 105 may view whether a buddy using buddy client system 305 is online, and typically may view whether the buddy is able to receive IMs. If the buddy is online, the user may exchange IMs with that buddy.
In one implementation, the IMs sent between client system 105 and buddy client system 305 are routed through IM host system 310. In another implementation, the IMs sent between client system 105 and buddy client system 305 are routed through a third party server (not shown), and also may optionally be routed through IM host system 310. In yet another implementation, the IMs are sent directly between client system 105 and buddy client system 305.
In procedure 400, the overt or inferred selection of an interface tab or other interface item corresponding to an IM session is detected (step 405). For example, a selection may be inferred by the positioning of a mouse or other input device position over or proximate to the interface tab or other interface item. In one implementation, if the position of the mouse pointer is, or remains for a predetermined threshold period of time, proximate to or positioned over the interface tab, a selection of the interface tab or other interface item is inferred. An overt selection of an interface tab or other interface item may also be made. For example, a button or other control on a mouse or other input device may be manipulated to make the overt selection. Next, content from within the IM session corresponding to the interface tab or other interface item is retrieved (step 410). In one implementation, all of the content of the IM session is retrieved. In another implementation, only a portion of the content of the IM session is retrieved. The tool tip is then opened and populated (step 415) with the content retrieved in step 410. For example, the tool tip may be opened and may appear as a rectangular pop-up window proximate to the interface tab over which the mouse is positioned. In other implementations, the tool tip may be opened in other locations on the display.
In the implementation shown by
The UI 600 includes an IM display area 605 to display the IM conversation messages 605a of an active IM session, for example, the IM conversation messages in the IM session corresponding to sub-interface 647j and interface tab 640j are displayed in display area 605 of
An area 625 may be provided to display various icons and controls. For example, the area 625 may include a buddy icon 625a corresponding to the IM buddy from which the conversation message 605a was received, and a buddy icon 625e corresponding to the user who has received and is viewing the IM conversation message 605a. Controls provided in area 625 may include a control 625b to retrieve information about the IM buddy, a control 625c to notify the service provider of inappropriate behavior by the IM buddy, a control 625d to indicate to the user whether the IM buddy is using a mobile device, a control 625f to setup various features of the service, and a control 625g to invite a new buddy to join in the IM session, among others. Also, a control button 630 may be provided to initiate a new IM session with a different IM buddy.
The UI 600 contains one or more interface tabs 640, each of which is assigned to a pending IM session and is potentially associated with a sub-interface 647 such as sub-interface 647j. The IM session may use a combination of text, graphics, audio, and video data to communicate with an IM buddy. The IM buddy may be identified by a screen name as shown by, for example, an identifier. The IM buddy typically is another user or an automated system, such as an artificial intelligence system or other automated system or agent having a screen name that responds to IM queries from a user. An active tab 640j corresponds to the IM session that the user views or with which the user interacts currently through, for example, sub-interface 647j. Inactive tabs 640a, 640b, 640c, 640d, 640e, 640f, 640g, 640h, and 640i correspond to other concurrent IM sessions with which the user does not currently view or interact, or sessions that the user is otherwise unable to view.
The UI 600 includes a conversation counter 650 that may provide information relating to the concurrent IM sessions, such as the total number of concurrent IM sessions, the number of new IM sessions, and the number of ongoing IM sessions having a new IM message waiting to be viewed. In general, the conversation counter 650 provides a perceivable indication to the user of statistics regarding the concurrent IM session. In the example of
Scroll bars 643 and 645 are provided for scrolling to perceive tabs corresponding to open IM sessions when the total number of concurrent IM sessions exceeds the maximum number of concurrent conversations that may be displayed simultaneously. The scroll bars 643 and 645 allow the user to scroll up and down among the concurrent IM sessions, and provide an indication that one or more of the IM sessions “hidden” by the scroll bar has a new IM message waiting to be viewed. For example, as shown in
Status indicators 644 and 646 may be provided on the scroll bars 643 and 645 to indicate whether one or more of the IM sessions accessible by the scroll bar has a new IM message. In the example of
The interface tabs 640 may include a status indicator 640j1 to indicate whether a new IM message within the IM session corresponding to an interface tab remains pending for review. In general, the indicator 640j1 provides a perceivable status indication to the user that a new message is pending in at least one concurrent IM session. Once the new message is viewed or acknowledged, the indicator 640j1 changes and the conversation counter 650 is updated to reflect one fewer message waiting to be viewed. The interface tabs 640 also may include an identifier, such as the screen name of the IM buddy, to identify the particular IM session to which it is assigned. Although not shown in
An informational tool tip 710 may be provided for the tabbed IM user interface to provide the user with a perceivable indication of at least a portion of an IM communications session that is not being actively displayed. For example, the informational tool tip may show all or a portion of the desired IM conversation 710a with buddy “ChattingChuck,” without the user needing to cause active display of the user interface corresponding to the desired IM conversation. The informational tool tip 710 may be provided to enable a user to perceive information relating to the conversations accessible by the scroll bars 643, 645. Also, the informational tool tip may be rendered in various locations on the display. For example, the tool tip may be rendered proximate or close to the interface tab to which the tool tip corresponds.
In order to activate the informational tool tip, the user may select a desired IM session that is not being actively displayed. For example, to activate and render the informational tool tip 710, the user may position a mouse 715 or other user input device proximate to or over the interface tab 640j corresponding to the desired IM session. In one implementation, the informational tool tip 710 is activated as soon as the mouse 715 or other user input device is positioned proximate to or over the interface tab 640j. In another implementation, the informational tool tip 710 is activated and rendered after the mouse 715 or other user input device remains proximate to or positioned over the interface tab 640j for a predetermined threshold period of time, or after some overt selection activity using the mouse or input device. The informational tool tip may be rendered in other locations on the display, or it may be non-visual.
The user may also close or deactivate the informational tool tip 710. For example, the informational tool tip may be automatically closed or deactivated if the user moves the mouse or input device, or if the mouse or input device is moved from a position over or proximate to the interface tab 640j. In another implementation, the tool tip may remain open until the user affirmatively takes an action to close the window.
The informational tool tip 710 may display all or a portion of the desired IM communications session 710a. In one implementation, a pre-determined or limited number of lines or characters of the desired IM session are displayed. In another implementation, a pre-determined number of messages communicated between the buddy and the user are displayed. For instance, as shown with respect to tool tip 810 of
The UI 900 includes a task bar 902. The task bar 902 includes one or more interface buttons 905. Interface buttons 905a, 905b, 905c, and 905d, each correspond to a concurrent, inactive IM session. If the user were to select an interface button, a corresponding IM sub-interface containing the IM conversation may be rendered. The sub-interface may be similar to sub-interface 647 described above with respect to
Referring to
Procedure 1100 generally involves rendering an informational tool tip for an IM UI. As described, it is particularly relevant to an IM UI having one or more tabs, each interface tab being associated with a sub-interface and assigned to a pending IM session and appearing adjacent to one another while persisting beyond active display of the associated sub-interface. However, procedure 1100 or its concepts may be applied to other applications and interfaces.
In procedure 1100, the client system 105 and the IM host system 310 are physically and/or logically connected (step 1105). For instance, client system 105 may connect to the IM host system 310 across a network (e.g., network 160) by supplying a user identification and password to a server (e.g., a login server) in order to obtain access to the IM host system 310.
Next, the IM host system 310 establishes communications between a first IM buddy (step 1110) and the client system 105. The IM host system 310 deliver an IM message across a network 160, and the IM message may include a text message portion, a time of delivery, and a screen name of the first IM buddy.
The client system 105 renders a first IM user interface for the first IM session with the first buddy, examples of which were described with respect to
As previously discussed, the IM UI includes a first interface tab corresponding to the first IM session with the first buddy, and also may include other tabs corresponding to other IM sessions with other buddies. For example,
Rendering the IM UI may include initializing or updating one or more of the interface tab, the sub-interface, the status indicator, the identifier, the conversation counter, the display area status indicator, the information indicator, and the display area. For example, as shown in
Using the client system 105, the user may choose to send an IM message back to the first buddy (step 1120). The client system 105 may send the message to the IM host system 310 by providing the IM message across a network 160. The IM message may include a message portion, a time of delivery, and a screen name of the user. The message portion may be a text message, a graphics message, an audio message, or a video message. Referring to
The IM Host system 310 provides the IM message from the user to the first IM buddy (step 1125). The IM host system 310 may provide the IM message across a network 160 to the client system associated with the first buddy (not shown).
Next, the client system 105 renders an updated IM UI for the first IM session (step 1130). The updated UI may be rendered simultaneously with step 1120, or may be rendered at a later time. Rendering an updated IM UI may include updating the interface tab, the sub-interface, the status indicator, the conversation counter, the information indicator, and the display area. For example, referring to
The IM host system 310 then provides an IM message from a second IM buddy (step 1135) to the client system 105. As discussed above with respect to step 1110, the IM host system 310 may provide the IM message across a network 160, and the IM message may include a text message portion, a time of delivery, and a screen name of the second IM buddy.
Next, the client system 105 renders a second interface tab for a second IM user interface corresponding to the second IM session with the second buddy, examples of which were described with respect to
Rendering the IM UI may include initializing or updating one or more of the interface tab, the sub-interface, the status indicator, the identifier, the conversation counter, the display area status indicator, the information indicator, and the display area. The IM message 705a from the second buddy appears in IM display area 605. Also, if the maximum number of concurrent IM sessions available for display is exceeded when the IM message is provided, then rendering the IM UI may include rendering a scroll arrow, examples of which were described with respect to
Using the client system 105, the user may choose to send an IM message to the second buddy (step 1145) in a similar fashion to that discussed above with respect to step 1120. Also, similar to the discussion above with respect to step 1125, the IM Host system 310 provides the IM message to the first IM buddy (step 1150).
Next, the client system 105 renders an updated IM UI (step 1155). The updated UI may be rendered simultaneously with step 1145, or may be rendered at a later time. Rendering the updated IM UI may include initializing or updating the interface tab, the sub-interface, status indicator, the identifier, the conversation counter, the display area status indicator, the information indicator, and the display area. The user's IM message to the second buddy also may be rendered in the IM display area 605.
The user may desire to activate an informational tool tip to perceive information about the First IM session which is not being actively displayed, while maintaining active display of the Second IM session. The user selects the First IM session (step 1160). For example, as discussed above with respect to
Next, the informational tool tip is rendered for the selected IM session, which in this case is the First IM session (step 1165). As discussed above with respect to
The relative placement of steps 1110-1165 with respect to other steps in
While some functions of procedure 1100 may be performed entirely by the client system 105, as described, other functions may be performed by the collective operation of the client system 105 and the IM host system 310. For example, an informational tool tip may be rendered entirely by the client. However, the informational tool tip may be rendered based upon information and/or IMs provided to the client by the IM host system.
Other implementations are within the scope of the following claims. For example, although the examples above are given in an IM context, other communications systems with similar attributes may be used. Also, the user interface may be a viewable interface, an audible interface, a tactile interface, or any combination thereof.
This application claims priority from U.S. Provisional Application No. 60/376,181, filed Apr. 30, 2002, which is incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
5283560 | Bartlett | Feb 1994 | A |
5287514 | Gram | Feb 1994 | A |
5307086 | Griffin et al. | Apr 1994 | A |
5416895 | Anderson et al. | May 1995 | A |
5544352 | Egger | Aug 1996 | A |
5546528 | Johnston | Aug 1996 | A |
5581670 | Bier et al. | Dec 1996 | A |
5588107 | Bowden et al. | Dec 1996 | A |
5617114 | Bier et al. | Apr 1997 | A |
5617526 | Oran et al. | Apr 1997 | A |
5627960 | Clifford et al. | May 1997 | A |
5644737 | Tuniman et al. | Jul 1997 | A |
5664133 | Malamud et al. | Sep 1997 | A |
5692142 | Craycroft et al. | Nov 1997 | A |
5712995 | Cohn | Jan 1998 | A |
5721852 | Porter | Feb 1998 | A |
5742813 | Kavanagh et al. | Apr 1998 | A |
5754176 | Crawford | May 1998 | A |
5760768 | Gram | Jun 1998 | A |
5798752 | Buxton et al. | Aug 1998 | A |
5801703 | Bowden et al. | Sep 1998 | A |
5832494 | Egger et al. | Nov 1998 | A |
5838315 | Craycroft et al. | Nov 1998 | A |
5877758 | Seybold | Mar 1999 | A |
5877765 | Dickman et al. | Mar 1999 | A |
5884306 | Bliss et al. | Mar 1999 | A |
5929851 | Donnelly | Jul 1999 | A |
5936625 | Kahl et al. | Aug 1999 | A |
5937417 | Nielsen | Aug 1999 | A |
5959621 | Nawaz et al. | Sep 1999 | A |
5974413 | Beauregard et al. | Oct 1999 | A |
5990905 | Chew et al. | Nov 1999 | A |
5995101 | Clark et al. | Nov 1999 | A |
6002398 | Wilson | Dec 1999 | A |
6002400 | Loring et al. | Dec 1999 | A |
6018571 | Langlois et al. | Jan 2000 | A |
6057844 | Strauss | May 2000 | A |
6078935 | Nielsen | Jun 2000 | A |
6081830 | Schindle | Jun 2000 | A |
6091409 | Dickman et al. | Jul 2000 | A |
6092068 | Dinkelacker | Jul 2000 | A |
6097389 | Morris et al. | Aug 2000 | A |
6118427 | Buxton et al. | Sep 2000 | A |
6144375 | Jain et al. | Nov 2000 | A |
6147685 | Bliss et al. | Nov 2000 | A |
6173316 | De Boor et al. | Jan 2001 | B1 |
6188403 | Sacerdoti et al. | Feb 2001 | B1 |
6212548 | DeSimone et al. | Apr 2001 | B1 |
6229539 | Morcos et al. | May 2001 | B1 |
6233571 | Egger et al. | May 2001 | B1 |
6233726 | Bowman et al. | May 2001 | B1 |
6237135 | Timbol | May 2001 | B1 |
6246411 | Strauss | Jun 2001 | B1 |
6248946 | Dwek | Jun 2001 | B1 |
6252594 | Xia et al. | Jun 2001 | B1 |
6260148 | Aggarwal et al. | Jul 2001 | B1 |
6275790 | Yamamoto et al. | Aug 2001 | B1 |
6281879 | Graham | Aug 2001 | B1 |
6301609 | Aravamudan et al. | Oct 2001 | B1 |
6304879 | Sobeski et al. | Oct 2001 | B1 |
6317128 | Harrison et al. | Nov 2001 | B1 |
6346952 | Shtivelman | Feb 2002 | B1 |
6362842 | Tahara et al. | Mar 2002 | B1 |
6369837 | Schirmer | Apr 2002 | B1 |
6377944 | Busey et al. | Apr 2002 | B1 |
6381735 | Hunt | Apr 2002 | B1 |
6384849 | Morcos et al. | May 2002 | B1 |
6407757 | Ho | Jun 2002 | B1 |
6434599 | Porter | Aug 2002 | B1 |
6519629 | Harvey et al. | Feb 2003 | B2 |
6539421 | Appleman et al. | Mar 2003 | B1 |
6665395 | Busey et al. | Dec 2003 | B1 |
6691159 | Grewal et al. | Feb 2004 | B1 |
6731308 | Tang et al. | May 2004 | B1 |
6784901 | Harvey et al. | Aug 2004 | B1 |
6907447 | Cooperman et al. | Jun 2005 | B1 |
6981223 | Becker et al. | Dec 2005 | B2 |
7017119 | Johnston et al. | Mar 2006 | B1 |
20020073207 | Widger et al. | Jun 2002 | A1 |
20020097277 | Pitroda | Jul 2002 | A1 |
20020101446 | Tang et al. | Aug 2002 | A1 |
20020130904 | Becker et al. | Sep 2002 | A1 |
20020160819 | Daurensan | Oct 2002 | A1 |
20020163545 | Hii | Nov 2002 | A1 |
20030030670 | Duarte et al. | Feb 2003 | A1 |
20030052915 | Brown et al. | Mar 2003 | A1 |
20030142141 | Brown et al. | Jul 2003 | A1 |
20030164862 | Cadiz et al. | Sep 2003 | A1 |
20030210265 | Haimberg | Nov 2003 | A1 |
Number | Date | Country | |
---|---|---|---|
60376181 | Apr 2002 | US |