US20090131034A1 - Automatic user availability status determination for a handheld communication device - Google Patents

Automatic user availability status determination for a handheld communication device Download PDF

Info

Publication number
US20090131034A1
US20090131034A1 US12/354,184 US35418409A US2009131034A1 US 20090131034 A1 US20090131034 A1 US 20090131034A1 US 35418409 A US35418409 A US 35418409A US 2009131034 A1 US2009131034 A1 US 2009131034A1
Authority
US
United States
Prior art keywords
availability status
user
unavailable
communication device
handheld communication
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US12/354,184
Inventor
Gerhard D. Klassen
Shaul S. Wisebourt
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
BlackBerry Ltd
Malikie Innovations Ltd
Original Assignee
Research in Motion Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Research in Motion Ltd filed Critical Research in Motion Ltd
Priority to US12/354,184 priority Critical patent/US20090131034A1/en
Assigned to RESEARCH IN MOTION LIMITED reassignment RESEARCH IN MOTION LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KLASSEN, GERHARD D., MR., WISEBOURT, SHAUL S., MR.
Publication of US20090131034A1 publication Critical patent/US20090131034A1/en
Assigned to MALIKIE INNOVATIONS LIMITED reassignment MALIKIE INNOVATIONS LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BLACKBERRY LIMITED
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58—Message adaptation for wireless communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72448—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
    • H04M1/72451—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions according to schedules, e.g. using calendar applications

Definitions

  • This application relates to handheld communication devices, and in particular to a method for automatically determining the availability status of a user of a handheld communication device.
  • a method for automatically determining user availability status.
  • Various selected conditions of the device may be checked, which imply whether or not the user is likely Available, or else Unavailable.
  • the selected conditions are checked only if the user has not explicitly or semi-explicitly set his or her status to Unavailable. In such a case, checking would be clearly redundant, since the user has clearly indicated a desire to override any automatic determination.
  • the conditions to be checked can vary widely, but generally include anything from which it might be inferred or implied that the user is likely either Available or Unavailable. Such conditions can include, for example, whether or not a specified timeout for use of a keypad, trackwheel or other mechanical feature of the device has elapsed yet; whether or not a real-time application is in use (a phone or games application, for example); and preferably any one or more of a variety of other conditions, one further example being whether or not there are any unattended-to notifications such as an unanswered phone call, or a missed e-mail, SMS or other message.
  • FIG. 1 is a block diagram showing an example flow of a method for checking user availability status
  • FIG. 2 is a block diagram showing an alternative example of the method.
  • FIG. 3 is a block diagram showing a more specific example of the method.
  • FIG. 1 shows a block diagram illustrating the principle of embodiments herein. From an entry point 1 , the method checks at box 2 for any one or more of a number of possible conditions which might reasonably imply that the user is Unavailable. If one of those conditions applies, then the user availability status is set to Unavailable at box 3 and there is a Check Later at box 4 to see if that is still the case. Otherwise, the user availability status is set to Available at box 5 , and there is a check again later at box 4 , or instead via box 4 ′ if a different time interval was desired than the time interval of box 4 .
  • the method is invoked only if the user has not explicitly set his or her status to Unavailable (via a Do Not Disturb option or setting or button, for example). Similarly, if the user has “semi-explicitly” set his or her status to Unavailable, for example by selecting a “Quiet” or other profile which implies Unavailable or which has Unavailable associated with it by default or by user selection, then the method is not invoked, i.e. there is no path to entry point 1 . The check for this explicit or semi-explicit setting takes place outside the example.
  • FIG. 2 an alternative is shown, in which checking for an explicit or semi-explicit Unavailable setting takes place within the example. From the entry point 1 , that is the first condition which is checked, at box 6 . If there is an explicit or semi-explicit Unavailable setting, then there is just a Check Later at box 4 or box 4 ′′, to see if that is still the case. Otherwise, the rest of the method proceeds as in FIG. 1 .
  • FIG. 3 shows a particular example of the method. This example follows the model of FIG. 2 , but could also follow the model of FIG. 1 , i.e. with respect to whether or not the check for explicit or semi-explicit Unavailable status takes place within the method or elsewhere.
  • boxes 21 , 22 and 23 correspond to box 2 in FIGS. 1 and 2 , and provide specific examples of conditions which could be checked in making an automatic user status determination.
  • the method first checks at box 21 to see if the elapsed time from last use of a keyboard or trackwheel or possibly some other mechanical feature of the device is greater than some defined timeout, 15 to 30 minutes for example. If not, then the user availability status is set to or left at Available, i.e. he or she is considered to be Available in view of current or recent use of the device.
  • the method next checks at box 22 to see if a real-time application such as a phone or game is in use. If so, the user availability status is set to or left at Available, i.e. he or she is considered to be likely Available, just temporarily occupied.
  • the method next checks at box 23 for any one of a number of possible additional conditions which might indicate or imply that the user is Unavailable. For example, the method could check for any of the following:
  • the user availability status is set to Unavailable at box 3 . Otherwise, it is set to Available at box 5 . In either event, the method then routes to the Check Later box 4 .
  • the consequences of the device being deemed Available or Unavailable depend on specific applications and specific implementations, and can vary. That is outside the scope of the application itself.
  • the consequences can be established by either the user's device, or a peer device, or both of them. For example, the user might not be able to send a message to someone who is Unavailable, or, as another example, the user may still be able to send the message, but the peer device will not notify the user if the peer device is Unavailable.
  • the behavior may be fixed, or preferably can be defined through user options.

Abstract

To automatically determine the availability status of the user of a handheld communication device, various selected conditions of the device may be checked, which imply whether or not the user is likely Available, or Unavailable or the equivalent. Normally, the selected conditions are checked only if the user has not explicitly or semi-explicitly set his or her status to Unavailable. The conditions to be checked can vary widely, but generally include anything from which it might be inferred or implied that the user is likely either Available or Unavailable or the equivalent. Such conditions can include, for example, whether or not a specified timeout for use of a keypad, trackwheel or other mechanical feature of the device has elapsed yet; whether or not a real-time application is in use; and preferably any one or more of a variety of other conditions, one further example being whether or not there are any unattended-to notifications such as an unanswered phone call, or a missed e-mail, SMS or other message.

Description

    REFERENCE TO RELATED APPLICATIONS
  • This is a divisional of U.S. patent application Ser. No. 11/048,716, filed Feb. 3, 2005, which claims the benefit of Provisional Application No. 60/607,758, filed Sep. 8, 2004, the contents of all of which are expressly incorporated herein by reference.
    • FIELD
  • This application relates to handheld communication devices, and in particular to a method for automatically determining the availability status of a user of a handheld communication device.
    • BACKGROUND
  • There are handheld communication device applications in which updated user availability status information is important. Instant messaging is a good example of such an application. A user expects answers mostly in real time (unlike SMS, for example), so it is critical to know other party's availability status at the time when the user sends his or her instant message. Most instant messaging allow the user to explicitly set his or her availability status. Most such applications also provide an implicit way for the client application to say whether the user is available or not. Usually the user availability status is changed by a desktop application based on whether the keyboard has remained idle for a certain period of time. However, this approach is not relevant for some handheld communication devices, such as when the device is in its holster, for example. The user may be actually available for responses, and just in a waiting mode, with the device idle. The implicit or automatic approach that is used by a desktop client is therefore not applicable to such devices.
    • SUMMARY
  • In view of the above, it is an object of embodiments herein to provide an improved method for determining the availability status of a user of a handheld communication device.
  • Thus according to an aspect herein, a method is provided for automatically determining user availability status. Various selected conditions of the device may be checked, which imply whether or not the user is likely Available, or else Unavailable.
  • According to a further aspect, preferably the selected conditions are checked only if the user has not explicitly or semi-explicitly set his or her status to Unavailable. In such a case, checking would be clearly redundant, since the user has clearly indicated a desire to override any automatic determination.
  • The conditions to be checked can vary widely, but generally include anything from which it might be inferred or implied that the user is likely either Available or Unavailable. Such conditions can include, for example, whether or not a specified timeout for use of a keypad, trackwheel or other mechanical feature of the device has elapsed yet; whether or not a real-time application is in use (a phone or games application, for example); and preferably any one or more of a variety of other conditions, one further example being whether or not there are any unattended-to notifications such as an unanswered phone call, or a missed e-mail, SMS or other message.
  • Further aspects will be described or will become apparent in the course of the following detailed description.
  • Throughout this specification, the terms Available and Unavailable are used for convenience. Of course it should be clearly understood that the terms used may vary among devices and from company to company within the industry, and the embodiments herein apply regardless of what actual terms are used to describe the states herein designated as Available and Unavailable. Without limiting the generality of the foregoing, alternative expressions such as “busy” or “unreachable” or “inaccessible” could be used, for example.
    • BRIEF DESCRIPTION OF THE DRAWINGS
  • Aspects and embodiments will now be described with reference to the accompanying drawings, in which:
  • FIG. 1 is a block diagram showing an example flow of a method for checking user availability status;
  • FIG. 2 is a block diagram showing an alternative example of the method; and
  • FIG. 3 is a block diagram showing a more specific example of the method.
    •  DETAILED DESCRIPTION
  • FIG. 1 shows a block diagram illustrating the principle of embodiments herein. From an entry point 1, the method checks at box 2 for any one or more of a number of possible conditions which might reasonably imply that the user is Unavailable. If one of those conditions applies, then the user availability status is set to Unavailable at box 3 and there is a Check Later at box 4 to see if that is still the case. Otherwise, the user availability status is set to Available at box 5, and there is a check again later at box 4, or instead via box 4′ if a different time interval was desired than the time interval of box 4.
  • In the FIG. 1 example, the method is invoked only if the user has not explicitly set his or her status to Unavailable (via a Do Not Disturb option or setting or button, for example). Similarly, if the user has “semi-explicitly” set his or her status to Unavailable, for example by selecting a “Quiet” or other profile which implies Unavailable or which has Unavailable associated with it by default or by user selection, then the method is not invoked, i.e. there is no path to entry point 1. The check for this explicit or semi-explicit setting takes place outside the example.
  • In FIG. 2, an alternative is shown, in which checking for an explicit or semi-explicit Unavailable setting takes place within the example. From the entry point 1, that is the first condition which is checked, at box 6. If there is an explicit or semi-explicit Unavailable setting, then there is just a Check Later at box 4 or box 4″, to see if that is still the case. Otherwise, the rest of the method proceeds as in FIG. 1.
  • FIG. 3 shows a particular example of the method. This example follows the model of FIG. 2, but could also follow the model of FIG. 1, i.e. with respect to whether or not the check for explicit or semi-explicit Unavailable status takes place within the method or elsewhere. In FIG. 3, boxes 21, 22 and 23 correspond to box 2 in FIGS. 1 and 2, and provide specific examples of conditions which could be checked in making an automatic user status determination.
  • Preferably the method first checks at box 21 to see if the elapsed time from last use of a keyboard or trackwheel or possibly some other mechanical feature of the device is greater than some defined timeout, 15 to 30 minutes for example. If not, then the user availability status is set to or left at Available, i.e. he or she is considered to be Available in view of current or recent use of the device.
  • If the timeout has elapsed, then preferably the method next checks at box 22 to see if a real-time application such as a phone or game is in use. If so, the user availability status is set to or left at Available, i.e. he or she is considered to be likely Available, just temporarily occupied.
  • If there is no real-time application in use, then preferably the method next checks at box 23 for any one of a number of possible additional conditions which might indicate or imply that the user is Unavailable. For example, the method could check for any of the following:
      • a. Unattended-to notifications: if there are notifications, for example an unanswered phone call, or a missed e-mail, SMS or other message, which the user has not responded to;
      • b. A Calendar event, indicating a contemporaneous appointment;
      • c. An event which the device recognizes as the user indicating temporary unavailability. For example, in some devices, the action of removing the device from a holster and immediately replacing it (“click-click”) may be deemed to be a signal that the user doesn't want to accept any notifications;
      • d. The device being locked;
      • e. The time being within the user's indicated normal sleep or off-duty hours;
      • f. The battery being low, in which case the user may wish to be considered Unavailable, to preserve the battery for other uses;
      • g. The user being out of the coverage area; and
      • h. Anything else relevant to the particular device, that might logically indicate Unavailable.
  • It should be clearly understood that the above is a list of examples only, and the manner in which the method is applied may vary considerably. For some devices, some of the above options may not be applicable, or there may be some options available which are not listed. And for some devices, even if the options are available, a decision may be made that only one or a few options will be checked. For example, it may be decided just to check whether the timeout has elapsed, if so check whether a real-time application is in use, and if not check for any unattended-to notifications.
  • If one of the conditions checked for does indeed apply, then the user availability status is set to Unavailable at box 3. Otherwise, it is set to Available at box 5. In either event, the method then routes to the Check Later box 4.
  • Especially if it is decided that the system will be set up to check a number of conditions, it makes sense to first check if a real-time application is in use, as in the preceding. However, that is not strictly a requirement herein. It is merely preferable, before using resources to check for other conditions. In general, it makes sense, where there are multiple conditions to be checked, to check them in the order of highest probability, though not mandatory.
  • The consequences of the device being deemed Available or Unavailable depend on specific applications and specific implementations, and can vary. That is outside the scope of the application itself. The consequences can be established by either the user's device, or a peer device, or both of them. For example, the user might not be able to send a message to someone who is Unavailable, or, as another example, the user may still be able to send the message, but the peer device will not notify the user if the peer device is Unavailable. The behavior may be fixed, or preferably can be defined through user options.
  • Those who are knowledgeable in the field will appreciate that there may be obvious variations to the preceding. Accordingly, the invention is defined not by the above specific examples, but by the claims which follow.

Claims (9)

1. A method for determining the availability status of a user of a handheld communication device, the method comprising:
checking if an interval between when the handheld device is removed from a holster and returned to the holster is less than a predetermined threshold; and
if the interval is less than the threshold, determining the availability status as Unavailable.
2. A method as in claim 1, further comprising checking whether or not the availability status has been explicitly or semi-explicitly set to Unavailable, and if so, bypassing the checking if the interval is less than the predetermined threshold.
3. A method as in claim 2, wherein, after bypassing, there is no further checking until when and if the availability status is set to Available.
4. A method as in claim 2, wherein, after bypassing, there is no further checking until a second predetermined time interval has passed.
5. A handheld communication device provided with a computer-readable medium containing instructions, which, when executed by the handheld communication device, cause the handheld communication device to perform a method for determining the availability status of a user of the device, the method comprising:
checking if an interval between when the handheld device is removed from a holster and returned to the holster is less than a predetermined threshold; and
if the interval is less than the threshold, determining the availability status as Unavailable.
6. A handheld communication device as in claim 5, wherein the method further comprises checking whether or not the availability status has been explicitly or semi-explicitly set to Unavailable, and if so, bypassing the checking if the interval is less than the predetermined threshold.
7. A handheld communication device as in claim 6, wherein. after bypassing, there is no further checking of availability status until when and if the availability status is set to Available.
8. A handheld communication device as in claim 6, wherein after bypassing, there is no further checking of availability status until a second predetermined time interval has passed.
9. A method for determining the availability status of a user of a handheld communication device, the method comprising:
checking if an interval between when the handheld device is removed from a holster and returned to the holster is less than a predetermined threshold;
if the interval is less than the threshold, determining the availability status as Unavailable; and
communicating the availability status via a network with which the handheld communication device is in communication.
US12/354,184 2004-09-08 2009-01-15 Automatic user availability status determination for a handheld communication device Abandoned US20090131034A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/354,184 US20090131034A1 (en) 2004-09-08 2009-01-15 Automatic user availability status determination for a handheld communication device

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US60775804P 2004-09-08 2004-09-08
US11/048,716 US8064355B2 (en) 2004-09-08 2005-02-03 Automatic user availability status determination for a handheld communication device
US12/354,184 US20090131034A1 (en) 2004-09-08 2009-01-15 Automatic user availability status determination for a handheld communication device

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/048,716 Division US8064355B2 (en) 2004-09-08 2005-02-03 Automatic user availability status determination for a handheld communication device

Publications (1)

Publication Number Publication Date
US20090131034A1 true US20090131034A1 (en) 2009-05-21

Family

ID=36036038

Family Applications (3)

Application Number Title Priority Date Filing Date
US11/048,716 Active 2027-02-07 US8064355B2 (en) 2004-09-08 2005-02-03 Automatic user availability status determination for a handheld communication device
US12/354,184 Abandoned US20090131034A1 (en) 2004-09-08 2009-01-15 Automatic user availability status determination for a handheld communication device
US13/280,504 Active US8688081B2 (en) 2004-09-08 2011-10-25 Automatic user availability status determination for a handheld communication device

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US11/048,716 Active 2027-02-07 US8064355B2 (en) 2004-09-08 2005-02-03 Automatic user availability status determination for a handheld communication device

Family Applications After (1)

Application Number Title Priority Date Filing Date
US13/280,504 Active US8688081B2 (en) 2004-09-08 2011-10-25 Automatic user availability status determination for a handheld communication device

Country Status (6)

Country Link
US (3) US8064355B2 (en)
EP (2) EP1805643B1 (en)
AT (1) ATE473606T1 (en)
CA (1) CA2580711C (en)
DE (1) DE602005022210D1 (en)
WO (1) WO2006026846A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10616409B2 (en) * 2014-06-17 2020-04-07 Lenovo (Singapore) Pte Ltd Sharing device availability
US11218377B2 (en) 2019-09-20 2022-01-04 Lenovo (Singapore) Pte. Ltd. Prediction of loss of network connection and caching of content

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE602008001785D1 (en) 2008-05-09 2010-08-26 Research In Motion Ltd System and method for updating presence information in instant messaging applications on a mobile device
US20100057857A1 (en) * 2008-08-27 2010-03-04 Szeto Christopher T Chat matching
US8930829B2 (en) * 2008-09-30 2015-01-06 Shoretel, Inc. Presence change alert
US20110208813A1 (en) * 2009-06-30 2011-08-25 Nortel Networks Limited Personal status communications manager
EP2328324A1 (en) 2009-11-27 2011-06-01 France Telecom Selective routing method, network and home agent
US9065786B2 (en) * 2010-09-24 2015-06-23 Yagi Corp. Context-sensitive auto-responder
WO2012040661A1 (en) * 2010-09-24 2012-03-29 Robert Plotkin Profile-based message control
WO2012064788A1 (en) 2010-11-08 2012-05-18 Robert Plotkin Enforced unitasking in multitasking systems
US9992021B1 (en) 2013-03-14 2018-06-05 GoTenna, Inc. System and method for private and point-to-point communication between computing devices
US20150135096A1 (en) * 2013-11-14 2015-05-14 Avaya Inc. System and method for displaying context-aware contact details

Citations (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020054117A1 (en) * 2000-03-16 2002-05-09 Van Dantzich Maarten R. Scope user interface for displaying the priorities and properties of multiple informational items
US20020083127A1 (en) * 2000-11-20 2002-06-27 At&T Wireless Services, Inc. Methods and systems for providing application level presence information in wireless communication
US20020087649A1 (en) * 2000-03-16 2002-07-04 Horvitz Eric J. Bounded-deferral policies for reducing the disruptiveness of notifications
US20020143916A1 (en) * 2000-05-11 2002-10-03 Dennis Mendiola Method and system for tracking the online status of active users of an internet-based instant messaging system
US20020162112A1 (en) * 2001-02-21 2002-10-31 Vesta Broadband Services, Inc. PC-based virtual set-top box for internet-based distribution of video and other data
US6493759B1 (en) * 2000-07-24 2002-12-10 Bbnt Solutions Llc Cluster head resignation to improve routing in mobile communication systems
US20030018726A1 (en) * 2001-04-27 2003-01-23 Low Sydney Gordon Instant messaging
US6519639B1 (en) * 1999-07-21 2003-02-11 Microsoft Corporation System and method for activity monitoring and reporting in a computer network
US20030104819A1 (en) * 2001-12-05 2003-06-05 Intel Corporation Automatically updating presence information
US20030135624A1 (en) * 2001-12-27 2003-07-17 Mckinnon Steve J. Dynamic presence management
US6658095B1 (en) * 2002-03-19 2003-12-02 Nortel Networks Limited Customized presence information delivery
US6674358B1 (en) * 2001-01-04 2004-01-06 Motorola, Inc. Holster with detection for an inserted electronic device
US20040039630A1 (en) * 2002-08-12 2004-02-26 Begole James M.A. Method and system for inferring and applying coordination patterns from individual work and communication activity
US6714519B2 (en) * 2000-11-03 2004-03-30 Vocaltec Communications Limited Communications availability
US20040162882A1 (en) * 2003-02-14 2004-08-19 Siemens Information And Communication Networks, Inc. Messenger assistant for personal information management
US20040199663A1 (en) * 2000-03-16 2004-10-07 Horvitz Eric J. Harnessing information about the timing of a user's client-server interactions to enhance messaging and collaboration services
US20050058094A1 (en) * 2003-09-16 2005-03-17 Mihal Lazaridis Method for creating a peer-to-peer immediate messaging solution without using an instant messaging server
US20050108348A1 (en) * 2003-10-29 2005-05-19 Eng-Keong Lee Endpoint status notification system
US20050273827A1 (en) * 1999-09-13 2005-12-08 Javed Shoeb M Set-top box for internet-based distribution of video and other data
US20060031368A1 (en) * 2004-06-16 2006-02-09 Decone Ian D Presence management in a push to talk system
US7062026B1 (en) * 1999-09-27 2006-06-13 Nec Corporation Telephone apparatus and start control method
US20060135182A1 (en) * 2004-12-21 2006-06-22 Unmehopa Musa R Method and apparatus for reporting implicit events
US7076267B2 (en) * 2001-12-07 2006-07-11 Research In Motion Limited System and method for event-dependent state activation for a dual-mode mobile communication device
US20060187847A1 (en) * 2005-02-05 2006-08-24 Cisco Technology, Inc Techniques for determining communication state using accelerometer data
US7120239B2 (en) * 2001-05-02 2006-10-10 Bellsouth Intellectual Property Corp. System and method for providing no answer detail service for telephone calls that are not completed
US7139797B1 (en) * 2002-04-10 2006-11-21 Nortel Networks Limited Presence information based on media activity
US7139806B2 (en) * 2002-10-10 2006-11-21 Motorola, Inc. Communication system for providing dynamic management of contacts and method therefor
US7227937B1 (en) * 2002-03-19 2007-06-05 Nortel Networks Limited Monitoring natural interaction for presence detection
US20080089488A1 (en) * 2003-01-20 2008-04-17 Avaya Technology Corp. Messaging advise in presence-aware networks

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3098488B2 (en) * 1998-04-20 2000-10-16 埼玉日本電気株式会社 Missed call notification device and method for foldable mobile phone
US7395329B1 (en) * 2002-05-13 2008-07-01 At&T Delaware Intellectual Property., Inc. Real-time notification of presence availability changes
US20050148331A1 (en) * 2004-01-07 2005-07-07 Ixi Mobile (R&D) Ltd. Presence status update system and method in a mobile communication network

Patent Citations (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6519639B1 (en) * 1999-07-21 2003-02-11 Microsoft Corporation System and method for activity monitoring and reporting in a computer network
US20050108392A1 (en) * 1999-07-21 2005-05-19 Microsoft Corporation System and method for activity monitoring and reporting in a computer network
US20050273827A1 (en) * 1999-09-13 2005-12-08 Javed Shoeb M Set-top box for internet-based distribution of video and other data
US7062026B1 (en) * 1999-09-27 2006-06-13 Nec Corporation Telephone apparatus and start control method
US20020054117A1 (en) * 2000-03-16 2002-05-09 Van Dantzich Maarten R. Scope user interface for displaying the priorities and properties of multiple informational items
US20020087649A1 (en) * 2000-03-16 2002-07-04 Horvitz Eric J. Bounded-deferral policies for reducing the disruptiveness of notifications
US20040199663A1 (en) * 2000-03-16 2004-10-07 Horvitz Eric J. Harnessing information about the timing of a user's client-server interactions to enhance messaging and collaboration services
US20020143916A1 (en) * 2000-05-11 2002-10-03 Dennis Mendiola Method and system for tracking the online status of active users of an internet-based instant messaging system
US6493759B1 (en) * 2000-07-24 2002-12-10 Bbnt Solutions Llc Cluster head resignation to improve routing in mobile communication systems
US6714519B2 (en) * 2000-11-03 2004-03-30 Vocaltec Communications Limited Communications availability
US7283805B2 (en) * 2000-11-20 2007-10-16 Cingular Wireless Ii, Llc Methods and systems for providing application level presence information in wireless communication
US20020083127A1 (en) * 2000-11-20 2002-06-27 At&T Wireless Services, Inc. Methods and systems for providing application level presence information in wireless communication
US6674358B1 (en) * 2001-01-04 2004-01-06 Motorola, Inc. Holster with detection for an inserted electronic device
US20020162112A1 (en) * 2001-02-21 2002-10-31 Vesta Broadband Services, Inc. PC-based virtual set-top box for internet-based distribution of video and other data
US20030018726A1 (en) * 2001-04-27 2003-01-23 Low Sydney Gordon Instant messaging
US7120239B2 (en) * 2001-05-02 2006-10-10 Bellsouth Intellectual Property Corp. System and method for providing no answer detail service for telephone calls that are not completed
US20030104819A1 (en) * 2001-12-05 2003-06-05 Intel Corporation Automatically updating presence information
US7076267B2 (en) * 2001-12-07 2006-07-11 Research In Motion Limited System and method for event-dependent state activation for a dual-mode mobile communication device
US20030135624A1 (en) * 2001-12-27 2003-07-17 Mckinnon Steve J. Dynamic presence management
US6658095B1 (en) * 2002-03-19 2003-12-02 Nortel Networks Limited Customized presence information delivery
US7227937B1 (en) * 2002-03-19 2007-06-05 Nortel Networks Limited Monitoring natural interaction for presence detection
US7139797B1 (en) * 2002-04-10 2006-11-21 Nortel Networks Limited Presence information based on media activity
US20040039630A1 (en) * 2002-08-12 2004-02-26 Begole James M.A. Method and system for inferring and applying coordination patterns from individual work and communication activity
US7139806B2 (en) * 2002-10-10 2006-11-21 Motorola, Inc. Communication system for providing dynamic management of contacts and method therefor
US20080089488A1 (en) * 2003-01-20 2008-04-17 Avaya Technology Corp. Messaging advise in presence-aware networks
US20040162882A1 (en) * 2003-02-14 2004-08-19 Siemens Information And Communication Networks, Inc. Messenger assistant for personal information management
US20050058094A1 (en) * 2003-09-16 2005-03-17 Mihal Lazaridis Method for creating a peer-to-peer immediate messaging solution without using an instant messaging server
US20050124363A1 (en) * 2003-09-16 2005-06-09 Klassen Gerhard D. Handheld electronic device and associated method providing availability data in a messaging environment
US20050108348A1 (en) * 2003-10-29 2005-05-19 Eng-Keong Lee Endpoint status notification system
US20060031368A1 (en) * 2004-06-16 2006-02-09 Decone Ian D Presence management in a push to talk system
US20060135182A1 (en) * 2004-12-21 2006-06-22 Unmehopa Musa R Method and apparatus for reporting implicit events
US20060187847A1 (en) * 2005-02-05 2006-08-24 Cisco Technology, Inc Techniques for determining communication state using accelerometer data

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10616409B2 (en) * 2014-06-17 2020-04-07 Lenovo (Singapore) Pte Ltd Sharing device availability
US11218377B2 (en) 2019-09-20 2022-01-04 Lenovo (Singapore) Pte. Ltd. Prediction of loss of network connection and caching of content

Also Published As

Publication number Publication date
US20060052061A1 (en) 2006-03-09
WO2006026846A1 (en) 2006-03-16
CA2580711C (en) 2012-09-18
EP1805643A1 (en) 2007-07-11
US20120094640A1 (en) 2012-04-19
EP2159712A3 (en) 2010-05-05
ATE473606T1 (en) 2010-07-15
EP1805643B1 (en) 2010-07-07
EP1805643A4 (en) 2007-10-17
US8064355B2 (en) 2011-11-22
EP2159712A2 (en) 2010-03-03
CA2580711A1 (en) 2006-03-16
US8688081B2 (en) 2014-04-01
DE602005022210D1 (en) 2010-08-19

Similar Documents

Publication Publication Date Title
US8688081B2 (en) Automatic user availability status determination for a handheld communication device
US6501834B1 (en) Message sender status monitor
US8103725B2 (en) Communication using delegates
US8874670B2 (en) Communication using delegates, such as delegates specified in an email or scheduling application
US7987236B2 (en) Recipient control of source audio identifiers for digital communications
US8140633B2 (en) Forwarding to automatically prioritized IM accounts based upon priority and presence
US8060121B1 (en) Mobile network presence service with load-based notification throttling
US20040158610A1 (en) Client proxying for instant messaging
US8189755B2 (en) Call urgency screening
US20040215732A1 (en) Extensible user context system for delivery of notifications
US20060193448A1 (en) Method and apparatus for augmenting voice data on a mobile device call
US20050265318A1 (en) Apparatus, system, and method for rejecting a session establishment request
US7827561B2 (en) System and method for public consumption of communication events between arbitrary processes
RU2005120368A (en) WHEN-FREE MESSAGE EXCHANGE
WO2007067075A2 (en) Context aware phonebook
EP1855431A2 (en) Mobile communication system, mobile terminal, mail server, and electronic mail reception-limiting method
CN1822542B (en) Presence management server and system
US6745225B2 (en) Method and a device for enabling intercommunication among user processes in a communication management system regardless of the availability of the user processes
JP2008035020A (en) Response validity/invalidity circumstance notification system
US20060271632A1 (en) System and method of voicemail and videomail storage for instant messaging users
US20070022160A1 (en) Method of managing privileged conversations in an instant conversation system
JP2005328488A (en) Battery saving method in wireless portable terminal and wireless portable terminal using the method
US9014675B1 (en) Mobile network presence service
JP2003173311A (en) Information terminal device
JPH08251224A (en) Electronic mail system

Legal Events

Date Code Title Description
AS Assignment

Owner name: RESEARCH IN MOTION LIMITED, CANADA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KLASSEN, GERHARD D., MR.;WISEBOURT, SHAUL S., MR.;REEL/FRAME:022113/0759

Effective date: 20050131

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

AS Assignment

Owner name: MALIKIE INNOVATIONS LIMITED, IRELAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BLACKBERRY LIMITED;REEL/FRAME:064104/0103

Effective date: 20230511