The present disclosure is generally related to personal communications and, more particularly, is related to presence and availability status.
Presence and availability are terms used to describe a present ability of an individual to communicate. Presence is an ability of an individual to communicate in real time, and availability is an individual's willingness to communicate in real time. In communications, it is advantageous to know whether a potential recipient of a communication message is present and available, i.e., available to receive and respond to the message before initiating the transmission of the message. By making the presence and availability of individual users known before any communication is attempted, a realtime communications environment is facilitated that is more effective and less obtrusive than conventional communication mediums. Clearly, the communication message that is sent to an addressee that is known to be present and available is more likely to be received promptly than a conventional message. For example, often times, conventional telephone calls are forwarded to a person's voicemail and are never returned.
Instant messaging (IM) is one communication medium that employs presence and availability technology. An instant messaging network recognizes when a user is “present” on the network. Accordingly, the network sends notification to other users (usually members of a “buddy list”) that are also logged on the network that the user is “present.” Further, instant messaging lets a user display custom status messages to his “buddies” online about the user's “availability.” For example, a user can specify his availability status as being “busy, not taking messages.” Therefore another user on the “buddy list” that is connected to the instant messaging network will be notified that although the user is present on the network, he is not available for receiving messages.
Presence and availability information is most useful when an individual shares his or her online status with a trusted group of users. A communication message sent to someone who is readily present and available is less obtrusive, when the addressee has made himself or herself available to the communication. However, today's services mostly focus on a “pull” model for users to retrieve others' presence and availability status. Typically, a user has to log on a communication network before the user is notified about the presence and availability of other users on the network. Thus, a heretofore unaddressed need exists in the industry to address the aforementioned deficiencies and inadequacies.
Preferred embodiments of the present invention provide a system and method for providing presence and availability status information of a first user (User1) to a second user (User2). The system includes a presence availability server for storing presence and availability status information of User 1. The presence availability server is configured to detect a change in the presence and availability status of User1. The presence availability server also informs a notification server of a change in the presence and availability status of User1. The notification server generates a notification message for a communication device of User2. The notification message contains current presence and availability status information of User1.
The preferred embodiment of the present invention can also be viewed as providing a method for supplying presence and availability status information of User1 to User2. In this regard, one embodiment of such a method, among others, can be broadly summarized by the following steps: storing presence and availability status of User 1; detecting a change in the presence and availability status of User1; generating a notification message for User2, wherein the notification message contains the current presence and availability status of User1.
Other systems, methods, features, and advantages of the present invention will be or become apparent to one with skill in the art upon examination of the following drawings and detailed description. It is intended that all such additional systems, methods, features, and advantages be included within this description and the scope of the present invention.
Many aspects of the present disclosure can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present invention. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.
The presence availability server 110 maintains current presence and availability data of User1 as the presence availability server receives updates from the communication device 120. The presence availability server 110 stores presence and availability data for User1 in a presence availability database 115. The presence availability database 115 is located on the presence availability server 110. Alternatively, in other embodiments, the presence availability database 115 could be in communication with and located separately from the presence availability server 110. The communication device of User1120 notifies the presence availability server 110 of a change in the presence and availability status of User1. The communication device of User1 communicates with the presence availability server 110 via a communication network 130. The communication network 130 could be a PSTN telephone network, the Internet, or any other network supporting communication technologies.
The presence availability notification system 100 also includes a notification server 140 that receives update messages from the presence availability server 110 concerning a change in the presence and availability status of User1. The notification server 140 then sends a notification message to the communication device 150 of User2 to notify User2 of a change in the online status of User1. The User2 communication device 150 includes any device that User2 can receive a notification message with, such as a PSTN phone, an email client, an instant messaging client, etc.
The notification server 140 contains a profile database 145. The profile database 145 contains profiles of users of the notification server 140, such as User1 and User2. Alternatively, the profile database 145 could be stored separately from the notification server 140 on another server that is in communication with the notification server 140. The notification server 140 preferably generates and transmits notification messages for receipt by the communication device 150 of User2 by using the Internet 160. In other embodiments, however, any type of communication network, besides the Internet 160, could be used.
Particularly, in one implementation, the notification server 140 sends a notification message to a messaging server 170 that is connected to the Internet 160. The messaging server 170 then forwards the notification message to the communication device 150 of User2 via a communication network 180. The messaging server 170 supports a communication technology, such as email, instant messaging, voiceXML, WAP, etc. The communication network 180 could be a PSTN telephone network, the Internet, or any other network supporting the communication technology of the messaging server 170. For example, if the messaging server 170 is an instant messaging server 170, then the communication network 180 could be the Internet, for example. Correspondingly, if the messaging server is a voiceXML server, then the communication network 180 could be a PSTN network.
The overall operation of the presence availability notification system 100 (or method 200) will be described with reference to
In block 230, User2 specifies notification preferences. Again, the entering of information for User2 may be facilitated by the use of web pages. Notification preferences are the necessary contact information for delivering a notification message to User2. The notification preferences may include the email address of User2, phone number, WAP address, instant messaging address, etc. User2 may have more than one contact address specified, so that User2 can receive more than one notification message for a presence and availability status change. Typically, the notification preferences are included in a profile for User2 that is created and stored in the profile database 145. Additionally in the profile, User2 specifies a userID and password. The userID and password are needed by User2 to access his profile and to update his profile information.
In block 240, User2 registers to monitor the presence and availability status of User1. To do so, User2 specifies the userID of User1 in the profile of User2. The profile of User2 is stored in the profile database 145. Additionally, the presence availability server 110 registers that the online status of User1 is being monitored. To initiate the sending of a notification message, a change occurs in the presence and availability status of User1. For instance, if User1 terminated an instant messaging session, his or her online status changes from being “present” for instant messaging communications to being “not present.” Therefore, a notification message will be sent to notify User2 of this change in the online status of User1. The current presence and availability data of User1 are maintained in a presence availability database 115 located in a presence availability server 110.
The presence availability server 110 detects the change in the presence and availability status of User1, as depicted in block 250. For instance, the communication device 120 of User1 may inform the presence availability server 110 of a change in the online status of User1. Alternatively, the presence availability server 110 could poll the communication device 120 to determine the online status of User1. In step 255, the presence availability server 110 determines from the presence availability database 115 that User1 is being monitored by at least one other user, so the presence availability server 110 informs the notification server 140 of the change in the presence and availability status of User1. Otherwise, the presence availability server 110 would not notify the notification server 140 of status changes for User1. After a change, the notification server 140 retrieves from the profile database 145 the notification preferences from the profiles of users who have the userID of User1 in their profile.
Therefore, the profile of User2 is retrieved by the notification server 140, since User2 is monitoring the online status of User1 and has the userID of User1 in his or her profile. From the profile of User2, the notification server obtains the notification preferences of User2, as depicted in block 260. The notification preferences specify the manner for delivering a notification message to User2. For example, the notification preferences may specify that a notification message is to be delivered at the email address of User2. Accordingly in block 270, a notification message detailing the presence and availability status change of User1 is sent to User2 in conformity with the notification preferences of User2. In the notification message, the presence and availability status of User2 is provided by the presence availability server.
In an alternative representative implementation of the present invention, User1 designates in his profile the users that he or she wants notified about the changes in his or her online status. Then after the notification server 140 is informed about a change in the online status of User1, the notification server 140 sends notification messages to the users designated in the profile of User1. The notification messages are delivered according to the notification preferences in the various profiles designated in the profile of User1.
In another embodiment, User1 designates in the presence availability database 115 the users that User1 wants notified about changes in the online status of User1. Accordingly, the presence availability server 110 notifies the notification server of a change in the presence and availability status of User1. The presence availability server 110 also instructs the notification server 140 on which individuals to send notifications to, since this information is stored in the presence availability database 115. The notification messages are delivered according to the notification preferences in the individual's profile in the profile database 145.
It should also be noted that the functions provided by the presence availability server & presence availability database and the notification server & profile database do not have to be provided by separate network devices. The respective functions could be performed by a single server & database.
With the instant messaging address of User2, the notification server 140 requests that an instant message be sent from a messaging server 170 to the instant messaging address of User2. In this particular embodiment, the messaging server 170 is an instant messaging server. In the request to the instant messaging server 170, the notification server 140 specifies the content of the instant message, which is to include the updated online status of User1. Lastly in
In another representative implementation of one preferred embodiment of the invention,
In
In
In an alternative implementation,
In
The notification message includes the new presence and availability status of User1. The voiceXML gateway 170 receives the notification message and initiates a telephone call to the telephone number of User2. Upon an answer by the communication device 150 of User2, the voiceXML gateway 170 converts the notification message in voiceXML to a voice notification message that is delivered to the communication device 150 of User2 over a PSTN telephone network.
Note, as long as the presence availability server 110 has a network interface and the number of users it has to support are small, a small workstation could operate as a presence availability server 110. More often, though, the presence availability server 110 will be a higher end platform, e.g. a Sun Microsystems Netra. The presence availability server 110 has interfaces to all of the types of devices it supports. Over these interfaces, the presence and availability status information of User1 is communicated to the presence availability server. For most devices a TCP/IP interface is sufficient. For some device types, a wireless modem may be required. Along with the device interfaces, the presence availability server may contain a database package to store the presence and availability status information in (e.g. Oracle, Access, etc.), and another interface to allow the querying of a user's presence and availability status. This second interface may be available over TCP/IP and preferably is in the form of a simple application program interface (API) or a servlet.
It should be emphasized that the above-described embodiments of the present invention, particularly, any “preferred” embodiments, are merely possible examples of implementations, merely set forth for a clear understanding of the principles of the invention. Many variations and modifications may be made to the above-described embodiment(s) of the invention without departing substantially from the spirit and principles of the invention. For example, other messaging technologies such as short message service (SMS) or fax messaging could be used to support the delivery of the notification messages. All such modifications and variations are intended to be included herein within the scope of this disclosure and the present invention and protected by the following claims.
This application is a continuation of copending U.S. utility application entitled, “Real-Time Notification of Presence Availability Changes,” having Ser. No. 12/133,590, filed Jun. 5, 2008, which is a continuation of U.S. utility application entitled, “Real-Time Notification of Presence Availability Changes,” having Ser. No. 10/144,425, filed May 13, 2002, U.S. Pat. No. 7,395,329, issued on Jul. 1, 2008, which is entirely incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5675733 | Williams | Oct 1997 | A |
5720771 | Snell | Feb 1998 | A |
5793365 | Tang et al. | Aug 1998 | A |
5796393 | MacNaughton et al. | Aug 1998 | A |
5812639 | Bartholomew et al. | Sep 1998 | A |
5926179 | Matsuda et al. | Jul 1999 | A |
6047327 | Tso et al. | Apr 2000 | A |
6058420 | Davies | May 2000 | A |
6108709 | Shinomura et al. | Aug 2000 | A |
6151507 | Laiho et al. | Nov 2000 | A |
6219045 | Leahy et al. | Apr 2001 | B1 |
6286033 | Kishinsky et al. | Sep 2001 | B1 |
6301609 | Aravamudan et al. | Oct 2001 | B1 |
6425006 | Chari et al. | Jul 2002 | B1 |
6429893 | Xin | Aug 2002 | B1 |
6466261 | Nakamura | Oct 2002 | B1 |
6546005 | Berkley et al. | Apr 2003 | B1 |
6553416 | Chari et al. | Apr 2003 | B1 |
6584494 | Manabe et al. | Jun 2003 | B1 |
6591094 | Bentley | Jul 2003 | B1 |
6654790 | Ogle et al. | Nov 2003 | B2 |
6658095 | Yoakum et al. | Dec 2003 | B1 |
6665375 | Forlenza et al. | Dec 2003 | B1 |
6668169 | Burgan et al. | Dec 2003 | B2 |
6671693 | Marpe et al. | Dec 2003 | B1 |
6727811 | Fendis | Apr 2004 | B1 |
6731308 | Tang et al. | May 2004 | B1 |
6757365 | Bogard | Jun 2004 | B1 |
6757722 | Lonnfors et al. | Jun 2004 | B2 |
6771173 | Clayton et al. | Aug 2004 | B1 |
6816578 | Kredo et al. | Nov 2004 | B1 |
6879677 | Trandal et al. | Apr 2005 | B2 |
6944555 | Blackett et al. | Sep 2005 | B2 |
6954136 | Sauer | Oct 2005 | B2 |
6965935 | Diong | Nov 2005 | B2 |
6968052 | Wullert, II | Nov 2005 | B2 |
6968179 | De Vries | Nov 2005 | B1 |
6976092 | Daniell et al. | Dec 2005 | B1 |
6980558 | Aramoto | Dec 2005 | B2 |
6987840 | Bosik et al. | Jan 2006 | B1 |
6993327 | Mathis | Jan 2006 | B2 |
7015806 | Naidoo et al. | Mar 2006 | B2 |
7020696 | Perry et al. | Mar 2006 | B1 |
7043530 | Isaacs et al. | May 2006 | B2 |
7058036 | Yu et al. | Jun 2006 | B1 |
7072941 | Griffin et al. | Jul 2006 | B2 |
7111044 | Lee | Sep 2006 | B2 |
7262690 | Heaton et al. | Aug 2007 | B2 |
7302270 | Day | Nov 2007 | B1 |
7313617 | Malik et al. | Dec 2007 | B2 |
7321921 | Malik | Jan 2008 | B2 |
7324826 | Carey et al. | Jan 2008 | B2 |
7353455 | Malik | Apr 2008 | B2 |
7370278 | Malik et al. | May 2008 | B2 |
7392306 | Donner et al. | Jun 2008 | B1 |
7395329 | Holt et al. | Jul 2008 | B1 |
7401158 | Beauchamp et al. | Jul 2008 | B2 |
7406501 | Szeto et al. | Jul 2008 | B2 |
7472187 | Malik | Dec 2008 | B2 |
7483969 | Chavda et al. | Jan 2009 | B2 |
7561041 | Nguyen et al. | Jul 2009 | B2 |
7624172 | Austin-Lane | Nov 2009 | B1 |
7676550 | Jachner | Mar 2010 | B1 |
7701925 | Mason et al. | Apr 2010 | B1 |
7836126 | Thommes et al. | Nov 2010 | B2 |
7956739 | Hong et al. | Jun 2011 | B2 |
8090821 | Holt et al. | Jan 2012 | B2 |
20020026483 | Isaacs et al. | Feb 2002 | A1 |
20020032740 | Stern et al. | Mar 2002 | A1 |
20020035605 | McDowell et al. | Mar 2002 | A1 |
20020046299 | Lefeber et al. | Apr 2002 | A1 |
20020083127 | Agrawal | Jun 2002 | A1 |
20020103008 | Rahn et al. | Aug 2002 | A1 |
20020160757 | Shavit et al. | Oct 2002 | A1 |
20030018903 | Greca et al. | Jan 2003 | A1 |
20030050986 | Matthews et al. | Mar 2003 | A1 |
20030097485 | Horvitz et al. | May 2003 | A1 |
20030182428 | Li et al. | Sep 2003 | A1 |
20030208544 | Wilson | Nov 2003 | A1 |
20030217098 | Bobde et al. | Nov 2003 | A1 |
20030217142 | Bobde et al. | Nov 2003 | A1 |
20030218631 | Malik | Nov 2003 | A1 |
20040003046 | Grabelsky et al. | Jan 2004 | A1 |
20040015547 | Griffin et al. | Jan 2004 | A1 |
20040015548 | Lee | Jan 2004 | A1 |
20040044738 | Ohno et al. | Mar 2004 | A1 |
20040085205 | Yeh | May 2004 | A1 |
20040086093 | Schranz | May 2004 | A1 |
20040153506 | Ito et al. | Aug 2004 | A1 |
20040171396 | Carey et al. | Sep 2004 | A1 |
20040177118 | Mason et al. | Sep 2004 | A1 |
20040177134 | Lonnfors et al. | Sep 2004 | A1 |
20040179038 | Blattner et al. | Sep 2004 | A1 |
20040179039 | Blattner et al. | Sep 2004 | A1 |
20040205175 | Kammerer | Oct 2004 | A1 |
20040221224 | Blattner et al. | Nov 2004 | A1 |
20040267887 | Berger et al. | Dec 2004 | A1 |
20050010644 | Brown et al. | Jan 2005 | A1 |
20050068167 | Boyer et al. | Mar 2005 | A1 |
20050166154 | Wilson et al. | Jul 2005 | A1 |
20050210104 | Torvinen | Sep 2005 | A1 |
20050216565 | Ito et al. | Sep 2005 | A1 |
20050218206 | Ohno et al. | Oct 2005 | A1 |
20050228895 | Karunamurthy et al. | Oct 2005 | A1 |
20060004924 | Trossen | Jan 2006 | A1 |
20060030264 | Morris | Feb 2006 | A1 |
20060031293 | Thommes et al. | Feb 2006 | A1 |
20060031772 | Valeski | Feb 2006 | A1 |
20060167998 | Yoshiuchi et al. | Jul 2006 | A1 |
20060242239 | Morishima et al. | Oct 2006 | A1 |
20060248184 | Wu et al. | Nov 2006 | A1 |
20060252444 | Ozugur | Nov 2006 | A1 |
20060253593 | Jachner | Nov 2006 | A1 |
20060277296 | Matsubara et al. | Dec 2006 | A1 |
20070016649 | Nishiki | Jan 2007 | A1 |
20070027930 | Alvarado et al. | Feb 2007 | A1 |
20070083627 | Mohammed et al. | Apr 2007 | A1 |
20070121867 | Ozugur et al. | May 2007 | A1 |
20070124469 | Mohammed et al. | May 2007 | A1 |
20070136475 | Leppisaari et al. | Jun 2007 | A1 |
20070150825 | Jachner | Jun 2007 | A1 |
20070182541 | Harris et al. | Aug 2007 | A1 |
20070198725 | Morris | Aug 2007 | A1 |
20070208702 | Morris | Sep 2007 | A1 |
20070220143 | Lund et al. | Sep 2007 | A1 |
20070233854 | Bukovec et al. | Oct 2007 | A1 |
20070265859 | Jachner | Nov 2007 | A1 |
20080052384 | Marl et al. | Feb 2008 | A1 |
20080077685 | Nguyen et al. | Mar 2008 | A1 |
20080133708 | Alvarado et al. | Jun 2008 | A1 |
20080184136 | Malik | Jul 2008 | A1 |
20080209347 | Malik et al. | Aug 2008 | A1 |
20080244026 | Holt et al. | Oct 2008 | A1 |
20100114579 | Ostermann et al. | May 2010 | A1 |
20100219971 | Appelman et al. | Sep 2010 | A1 |
20100227594 | De Vries | Sep 2010 | A1 |
20100299615 | Miluzzo et al. | Nov 2010 | A1 |
20110029629 | Burtner et al. | Feb 2011 | A1 |
Number | Date | Country |
---|---|---|
03098449 | Nov 2003 | WO |
03100637 | Dec 2003 | WO |
Entry |
---|
Malik; Final Office Action mailed Feb. 14, 2012 for U.S. Appl. No. 12/115,004, filed May 5, 2008. |
Malik; Non-Final Rejection mailed Nov. 4, 2005 for U.S. Appl. No. 10/889,859, filed Jul. 13, 2004. |
Malik; Notice of Allowance and Fees Due mailed Sep. 27, 2007 for U.S. Appl. No. 10/889,859, filed Jul. 13, 2004. |
Malik; U.S. Appl. No. 10/889,859, filed Jul. 13, 2004. |
Malik; Non-Final Rejection mailed Oct. 1, 2008 for U.S. Appl. No. 12/017,999, filed Jan. 22, 2008. |
Malik; U.S. Appl. No. 12/017,999, filed Jan. 22, 2008. |
Nguyen; Final Office Action mailed Jun. 8, 2010 for U.S. Appl. No. 11/524,668 mailed Sep. 21, 2006. |
Nguyen; Final Office Action mailed Jun. 29, 2011 for U.S. Appl. No. 11/524,668, filed Sep. 21, 2006. |
Nguyen; Final Office Action mailed Sep. 3, 2009 for U.S. Appl. No. 11/524,668, filed Sep. 24, 2006. |
Nguyen; Non-Final Office Action mailed Jan. 20, 2011 for U.S. Appl. No. 11/524,668, filed Sep. 21, 2006. |
Nguyen; Non-Final Rejection mailed Mar. 9, 2009 for U.S. Appl. No. 11/524,668, filed Sep. 21, 2006. |
Nguyen; Non-Final Rejection mailed Dec. 31, 2009 for U.S. Appl. No. 11/524,668, filed Sep. 21, 2006. |
Nguyen; Non-Final Rejection mailed Oct. 20, 2008 for U.S. Appl. No. 11/520,262, filed Sep. 13, 2006. |
Nguyen; Notice of Allowance mailed Feb. 6, 2009 for U.S. Appl. No. 11/520,262, filed Sep. 13, 2006. |
Nguyen; Notice of Allowance mailed Apr. 6, 2009 for U.S. Appl. No. 11/520,262, filed Sep. 13, 2006. |
Nguyen; Non-Final Office Action mailed Sep. 24, 2010 for U.S. Appl. No. 12/483,306, filed Jun. 12, 2009. |
Nguyen; Notice of Allowance mailed Mar. 17, 2011 for U.S. Appl. No. 12/483,306, filed Jun. 12, 2009. |
Nguyen; Final Office Action mailed Jul. 6, 2011 for U.S. Appl. No. 11/525,008, filed Sep. 21, 2006. |
Nguyen; Final Office Action mailed Jul. 16, 2010 for U.S. Appl. No. 11/525,008, filed Sep. 21, 2006. |
Nguyen; Final Office Action mailed Sep. 15, 2009 for U.S. Appl. No. 11/525,008, filed Sep. 21, 2006. |
Nguyen; Non-Final Office Action mailed Feb. 2, 2011 for U.S. Appl. No. 11/525,008, filed Sep. 21, 2006. |
Nguyen; Non-Final Rejection mailed Jan. 22, 2010 for U.S. Appl. No. 11/525,008, filed Sep. 21, 2006. |
Nguyen; Non-Final Rejection mailed Mar. 12, 2009 for U.S. Appl. No. 11/525,008, filed Sep. 21, 2006. |
Daigle; Final Office Action mailed Apr. 10, 2009 for U.S. Appl. No. 11/304,319, filed Dec. 15, 2005. |
Daigle; Interview Summary mailed Jun. 15, 2009 for U.S. Appl. No. 11/304,319, filed Dec. 15, 2005. |
Daigle; Non-Final Rejection mailed Nov. 20, 2008 for U.S. Appl. No. 11/304,319, filed Dec. 15, 2005. |
Daigle; U.S. Appl. No. 11/304,319, filed Dec. 15, 2005. |
Daigle; Non-Final Rejection mailed Jul. 29, 2009 for U.S. Appl. No. 11/304,341, filed Dec. 15, 2005. |
Jensen; U.S. Appl. No. 12/535,062, filed Aug. 4, 2009. |
Boyer, et al., “Presence Awareness Tools for Virtual Enterprise”, 1998, 6 pages—Virtual Enterprise Workshop, Citeseer. |
Newton; Telecom Dictionary; Definition of “Ack”; CMP books, 20th edition, p. 42. |
Jensen; Non-Final Office Action mailed Jan. 3, 2012 for U.S. Appl. No. 12/535,062, filed Aug. 4, 2009. |
Non-Final Office Action mailed Nov. 28, 2011 for U.S. Appl. No. 12/059,320, filed Mar. 31, 2008. |
Malik; Final Office Action mailed Jun. 25, 2012 for U.S. Appl. No. 12/059,320, filed Mar. 31, 2008. |
Nguyen; Notice of Allowance mailed Jun. 20, 2012 for U.S. Appl. No. 11/524,668, filed Sep. 21, 2006. |
Holt; Final Rejection mailed Feb. 27, 2006 for U.S. Appl. No. 10/144,425, filed May 13, 2002. |
Holt; Final Rejection mailed Jun. 19, 2007 for U.S. Appl. No. 10/144,425, filed May 13, 2002. |
Holt: Non-Final Rejection mailed Jan. 3, 2007 for U.S. Appl. No. 10/144,425, filed May 13, 2002. |
Holt: Non-Final Rejection mailed Jul. 14, 2006 for U.S. Appl. No. 10/144,425, filed May 13, 2002. |
Holt; Non-Final Rejection mailed Aug. 25, 2005 for U.S. Appl. No. 10/144,425, filed May 13, 2002. |
Holt; Notice of allowance and Fees Due mailed Jan. 28, 2008 for U.S. Appl. No. 10/144,425, filed May 13, 2002. |
Holt; U.S. Appl. No. 10/144,425, filed May 13, 2002. |
Holt; Non-Final Office Action mailed Mar. 8, 2011 for U.S. Appl. No. 12/133,590, filed Jun. 5, 2008. |
Holt; Non-Final Office Action mailed Sep. 15, 2010 for U.S. Appl. No. 12/133,590, filed Jun. 5, 2008. |
Holt; Notice of Allowance mailed Sep. 1, 2011 for U.S. Appl. No. 12/133,590, filed Jun. 5, 2008. |
Malik; Advisory Action mailed Jun. 11, 2004 for U.S. Appl. No. 10/223,859, filed Aug. 19, 2002. |
Malik; Examiner Interview Summary mailed Apr. 21, 2004 for U.S. Appl. No. 10/223,859, filed Aug. 19, 2002. |
Malik; Examiner Interview Summary mailed Nov. 14, 2003 for U.S. Appl. No. 10/223,859, filed Aug. 19, 2002. |
Malik; Final Rejection mailed Feb. 24, 2004 for U.S. Appl. No. 10/223,859, filed Aug. 19, 2002. |
Malik; Final Rejection mailed Sep. 7, 2006 for U.S. Appl. No. 10/223,859, filed Aug. 19, 2002. |
Malik; Final Rejection mailed Nov. 21, 2005 for U.S. Appl. No. 10/223,859, filed Aug. 19, 2002. |
Malik; Non-Final Rejection mailed Mar. 13, 2006 for U.S. Appl. No. 10/223,859, filed Aug. 19, 2002. |
Malik; Non-Final Rejection mailed May 18, 2005 for U.S. Appl. No. 10/223,859, filed Aug. 19, 2002. |
Malik; Non-Final Rejection mailed Jun. 6, 2007 for U.S. Appl. No. 10/223,859, filed Aug. 19, 2002. |
Malik; Non-Final Rejection mailed Sep. 2, 2003 for U.S. Appl. No. 10/223,859, filed Aug. 19, 2002. |
Malik; Non-Final Rejection mailed Oct. 20, 2004 for U.S. Appl. No. 10/223,859, filed Aug. 19, 2002. |
Malik; Notice of Allowance and Fees Due mailed Dec. 5, 2007 for U.S. Appl. No. 10/223,859, filed Aug. 19, 2002. |
Malik; Pre-Brief Appeal Conference Decision mailed Mar. 15, 2007 for U.S. Appl. No. 10/223,859, filed Aug. 19, 2002. |
Malik; U.S. Appl. No. 10/223,859, filed Aug. 19, 2002. |
Malik; Final Office Action mailed Nov. 9, 2010 for U.S. Appl. No. 12/059,320, filed Mar. 31, 2008. |
Malik; Non-Final Office Action mailed Apr. 8, 2010 for U.S. Appl. No. 12/059,320, filed Mar. 31, 2008. |
Malik; U.S. Appl. No. 12/059,320, filed Mar. 31, 2008. |
Mailk; Final Rejection mailed Dec. 5, 2006 for U.S. Appl. No. 10/985,361, filed Nov. 10, 2004. |
Malik; Advisory Action mailed Feb. 28, 2007 for U.S. Appl. No. 10/985,361, filed Nov. 10, 2004. |
Malik; Non-Final Rejection mailed Jun. 5, 2006 for U.S. Appl. No. 10/985,361, filed Nov. 10, 2004. |
Malik; Non-Final Rejection mailed Jun. 19, 2007 for U.S. Appl. No. 10/985,361, filed Nov. 10, 2004. |
Malik; Notice of Allowance and Fees Due mailed Jan. 11, 2008 for U.S. Appl. No. 10/985,361, filed Nov. 10, 2004. |
Malik; U.S. Appl. No. 10/985,361, filed Nov. 10, 2004. |
Malik; Non-Final Office Action mailed May 17, 2011 for U.S. Appl. No. 12/115,004, filed May 5, 2008. |
Malik; U.S. Appl. No. 12/115,004, filed May 5, 2008. |
Adamczyk; Advisory Action mailed Dec. 31, 2008 for U.S. Appl. No. 10/745,199, filed Dec. 23, 2003. |
Adamczyk; Final Office Action mailed Dec. 8, 2009 for U.S. Appl. No. 10/745,199, filed Dec. 23, 2003. |
Adamczyk; Final Rejection mailed Oct. 14, 2008 for U.S. Appl. No. 10/745,199, filed Dec. 23, 2003. |
Adamczyk; Non-Final Rejection mailed Mar. 26, 2008 for U.S. Appl. No. 10/745,199, filed Dec. 23, 2003. |
Adamczyk; Non-Final Rejection mailed Jun. 11, 2009 for U.S. Appl. No. 10/745,199, filed Dec. 23, 2003. |
Adamczyk; U.S. Appl. No. 10/745,199, filed Dec. 23, 2003. |
Malik; Examiner Interview Summary mailed Jan. 4, 2006 for U.S. Appl. No. 10/889,859, filed Jul. 13, 2004. |
Malik; Examiner Interview Summary mailed Jun. 5, 2006 for U.S. Appl. No. 10/889,859, filed Jul. 13, 2004. |
Malik; Examiner Interview Summary mailed Jun. 19, 2007 for U.S. Appl. No. 10/889,859, filed Jul. 13, 2004. |
Malik; Examiner Interview Summary mailed Aug. 2, 2006 for U.S. Appl. No. 10/889,859, filed Jul. 13, 2004. |
Malik; Examiner Interview Summary mailed Sep. 27, 2007 for U.S. Appl. No. 10/889,859, filed Jul. 13, 2004. |
Malik; Final Rejection mailed Mar. 28, 2006 for U.S. Appl. No. 10/889,859, filed Jul. 13, 2004. |
Malik; Final Rejection mailed Dec. 12, 2006 for U.S. Appl. No. 10/889,859, filed Jul. 13, 2004. |
Malik; Non-Final Rejection mailed Apr. 9, 2007 for U.S. Appl. No. 10/889,859, filed Jul. 13, 2004. |
Malik; Non-Final Rejection mailed Jun. 27, 2006 for U.S. Appl. No. 10/889,859, filed Jul. 13, 2004. |
Number | Date | Country | |
---|---|---|---|
20120072590 A1 | Mar 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12133590 | Jun 2008 | US |
Child | 13306189 | US | |
Parent | 10144425 | May 2002 | US |
Child | 12133590 | US |